[ngw] Bcc question
jeffrey.i.ghitelman at state.or.us
Tue Dec 4 22:45:24 UTC 2012
Here you go...
Return-path: <user at domain.com>
Received: from mailhub.state.or.us ([xxx.xxx.xxx.xxx])
by V-GPW02.A4590.PERS.STATE.OR.US with ESMTP; Tue, 04 Dec 2012 13:03:44 -0800
Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [188.8.131.52])
by mail5.state.or.us with ESMTP id qB4L3i51012303-qB4L3i52012303
for <jeffrey.i.ghitelman at state.or.us>; Tue, 4 Dec 2012 13:03:44 -0800
Received: from omta17.emeryville.ca.mail.comcast.net ([184.108.40.206])
by qmta03.emeryville.ca.mail.comcast.net with comcast
id XTev1k0011afHeLA3Z3kBk; Tue, 04 Dec 2012 21:03:44 +0000
Received: from sz0065.ev.mail.comcast.net ([220.127.116.11])
by omta17.emeryville.ca.mail.comcast.net with comcast
id XZ3k1k00X2yr1eL8dZ3kat; Tue, 04 Dec 2012 21:03:44 +0000
Date: Tue, 4 Dec 2012 21:03:44 +0000 (UTC)
From: Jeff Ghitelman <user at domain.com>
To: jeffrey.i.ghitelman at state.or.us
Message-ID: <1587293679.901898.1354655024369.JavaMail.root at sz0065a.emeryville.ca.mail.comcast.net>
Subject: testing external email
Content-Type: text/plain; charset=utf-8
X-Mailer: Zimbra 6.0.13_GA_2944 (zclient/6.0.13_GA_2944)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
X-FEAS-SPF: PASS / PASS ( ip="18.104.22.168", helo="qmta03.emeryville.ca.mail.comcast.net", mailFrom="user at domain.com" ) ( headerFrom="user at domain.com" )
>>> On 12/4/2012 at 2:30 PM, "James Taylor" <James.Taylor at eastcobbgroup.com> wrote:
can you you post a sanitized example?
>>> "Jeffrey GHITELMAN" <jeffrey.i.ghitelman at state.or.us> 12/4/2012 04:06 PM >>>
Thanks for the reply James...
I don't see any bcc: info in the message source; is there somewhere else I can look for it?
>>> On 12/4/2012 at 12:04 PM, "James Taylor" <James.Taylor at eastcobbgroup.com> wrote:
The bcc: field is populated based on the header info in the incoming email.
I have never heard of this happening.
If you have a relay host for incoming mail, I would suspect it is doing something bad to the smtp header of the incoming email.
The East Cobb Group, Inc.
james.taylor at eastcobbgroup.com
>>> "Jeffrey GHITELMAN" <jeffrey.i.ghitelman at state.or.us> 12/4/2012 11:21 AM >>>
I need a little help with an issue I can't figure out. I hope I can explain this clearly.
We are a single domain, single po shop. Ever since the 5.x days our system was configured with two domains in the Internet Addressing portion of our system config. .
Our internal domain is PERS.STATE.OR.US which was (is) the preferred domain and STATE.OR.US was the second domain listed. I never really understood why STATE.OR.US was specified, but as long as everything worked properly, I left it alone.
All our external email is relayed to a statewide mailhub which does a lookup and replaces @state.or.us with the proper agency domain in our case PERS.STATE.OR.US.
However, when internal apps with built-in SMTP mailers would try to send to STATE.OR.US addresses, the GWIA would return a addressee unknown error, because that entity did not exist locally.
So to correct this, I removed the STATE.OR.US definition on our system. Well that fixed the relay problem.... but introduced another issue.
Now, all inbound email shows the users full external address (e.g. FN.LN at PERS.STATE.OR.US) in the To: field and their display name in the Bc: field. Is there anyway to prevent the Bc field from being populated like this?
If this is an unsolicited spam message, please click this link to report it: http://control.eastcobbgroup.com:49285/contents/spamreport.shtml?rptid=18442&srvid=16vl15t
ngw mailing list
ngw at ngwlist.com
If this is an unsolicited spam message, please click this link to report it: http://control.eastcobbgroup.com:49285/contents/spamreport.shtml?rptid=18460&srvid=16vl15t
ngw mailing list
ngw at ngwlist.com
More information about the ngw