On Tue, Jul 06, 2010 at 10:11:27AM -0400, Matt Hayes wrote: > I've been watching this for a while and still not sure what could be > causing it it or if its a known issue, but thought I'd pass it along > here on the mailing list to see whatever one else thought. > > I use recipient_bcc_maps to bcc email to my personal account to Gmail.
> Relevant logs to the issue: > --------------------------- > > http://pastebin.slackadelic.com/p/VUgFOC21.html Look at lines > 25,26,27,28 as they are where the duplicate log entries are at. Please be kind to the people helping you and do not use pastebins, they are a pain in the butt to use. Post the logs, and obfuscate the local parts of any addresses you want to keep private: Jul 6 09:59:36 cyberslack postfix/smtpd[20468]: 366C57A17A: client=russian-caravan.cloud9.net[168.100.1.4] Jul 6 09:59:36 cyberslack postfix/cleanup[20474]: 366C57A17A: message-id=<20100706135843.gj5...@np305c2n2.ms.com> Jul 6 09:59:36 cyberslack postfix/qmgr[16355]: 366C57A17A: from=<owner-postfix-us...@postfix.org>, size=5201, nrcpt=2 (queue active) Jul 6 09:59:37 cyberslack postfix-reinject/smtpd[20481]: 2EDEE7A22F: client=localhost[127.0.0.1] Jul 6 09:59:37 cyberslack postfix/cleanup[20474]: 2EDEE7A22F: message-id=<20100706135843.gj5...@np305c2n2.ms.com> Jul 6 09:59:37 cyberslack postfix/qmgr[16355]: 2EDEE7A22F: from=<owner-postfix-us...@postfix.org>, size=5585, nrcpt=3 (queue active) Jul 6 09:59:37 cyberslack amavis[19206]: (19206-08) Passed CLEAN, [168.100.1.4] [170.74.93.68] <owner-postfix-us...@postfix.org> -> <gmailu...@gmail.com>,<slacku...@slackadelic.com>, Message-ID: <20100706135843.gj5...@np305c2n2.ms.com>, Hits: -0.064, 934 ms Jul 6 09:59:37 cyberslack amavisfeed/smtp[20476]: 366C57A17A: to=<gmailu...@gmail.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=2.5, delays=1.6/0.01/0.01/0.94, dsn=2.6.0, status=sent (250 2.6.0 Ok, id=19206-08, from MTA: 250 2.0.0 Ok: queued as 2EDEE7A22F) Jul 6 09:59:37 cyberslack amavisfeed/smtp[20476]: 366C57A17A: to=<slacku...@slackadelic.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=2.5, delays=1.6/0.01/0.01/0.94, dsn=2.6.0, status=sent (250 2.6.0 Ok, id=19206-08, from MTA: 250 2.0.0 Ok: queued as 2EDEE7A22F) Jul 6 09:59:37 cyberslack postfix/qmgr[16355]: 366C57A17A: removed Jul 6 09:59:37 cyberslack postfix/virtual[20482]: 2EDEE7A22F: to=<slacku...@slackadelic.com>, relay=virtual, delay=0.12, delays=0.07/0.02/0/0.02, dsn=2.0.0, status=sent (delivered to maildir) Jul 6 09:59:37 cyberslack postfix/smtp[20483]: 2EDEE7A22F: to=<gmailu...@gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.95.27]:25, delay=0.76, delays=0.07/0.05/0.29/0.34, dsn=2.0.0, status=sent (250 2.0.0 OK 1278424777 16si8703246ibr.79) Jul 6 09:59:37 cyberslack postfix/smtp[20483]: 2EDEE7A22F: to=<gmailu...@gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.95.27]:25, delay=0.76, delays=0.07/0.05/0.29/0.34, dsn=2.0.0, status=sent (250 2.0.0 OK 1278424777 16si8703246ibr.79) Jul 6 09:59:37 cyberslack postfix/qmgr[16355]: 2EDEE7A22F: removed > Definitely could be something with my setup, but this is the only time I > see the duplicate is when the bcc map sends the email off-site. Nothing wrong at all, there are no duplicate logs, delivery into amavis is logged, and delivery to the destination post-amavis is logged. -- Viktor.
