On Tue, 19 Mar 2013, Ed wrote:
Hi All.
I am experiencing an issue with the following:
The scenario:
From: [email protected]
To: [email protected]
CC: [email protected]
After receiving the email CC at site 3, site 3 is sending out emails to
everyone on the original,
basically a duplicate email arrives to the sender and everyone in the
headers.
You then include logs but it's hard to figure out what corresponds to
site1, site2, and site3.
The logs appear to indicate that there are one or more content filters at
play. Noel pointed out what can happen if they're poorly designed.
Postfix
Site 3 logs and postconf follows
Logs
----------------------
Mar 14 10:27:41 mail postfix/cleanup[5265]:
10E7BE1C0A:message-id=<[email protected]
al>
Mar 14 10:27:41 mail postfix/smtpd[5269]: disconnect from
localhost[127.0.0.1]
Mar 14 10:27:41 mail postfix/smtp[5266]: 44D90E014D:
to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=6.5,
delays=1.7/0.02/0/4.7, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=03066-15,
from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 10E7BE1C0A)
What's this. We see the queue ID reported by the recieving SMTP server in
our own logs. Is this just being handed off to our same Postfix instance
on another port?
Mar 14 10:27:41 mail postfix/qmgr[2179]: 44D90E014D: removed
Mar 14 10:27:41 mail postfix/smtp[5270]: 10E7BE1C0A:
to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10026, delay=0.05,
delays=0.03/0.02/0/0, dsn=2.0.0, status=sent (250 Ok)
Handed off to a content filter at port 10026.
Mar 14 10:27:41 mail postfix/qmgr[2179]: 10E7BE1C0A: removed
Mar 14 10:27:41 mail postfix/smtpd[5272]: connect from localhost[127.0.0.1]
Mar 14 10:27:41 mail postfix/smtpd[5272]: 4B9A3E1C0A:
client=localhost[127.0.0.1]
Mar 14 10:27:41 mail postfix/cleanup[5265]:
4B9A3E1C0A:message-id=<[email protected]
al>
Mar 14 10:27:41 mail postfix/qmgr[2179]: 4B9A3E1C0A:
from=<[email protected]>, size=7049, nrcpt=3 (queue active)
And comes back from a content filter with 3 recipients.
Seeing your master.cf might help too. But it's most likely the content
filter listening to port 10026.
-- Larry Stone
[email protected]
