On 22 May 2013, at 07:07 , "Bill Cole" <[email protected]> wrote: > On 22 May 2013, at 7:36, LuKreme wrote: >> May 21 14:29:35 mail postfix/cleanup[81455]: 27FC0118B7AF: >> message-id=<[email protected]> >> May 21 14:29:35 mail postfix/bounce[81551]: 3F635118B777: sender >> non-delivery notification: 27FC0118B7AF > > 27FC0118B7AF has a null envelope sender because it is a bounce of > 3F635118B777. See the 2nd line?
Yes, I see that *now*. Thanks. I think I was tunnel-visioned on the end of the line. > Seems like a backscatter problem. The log should have lines about why > 27FC0118B7AF was asynchronously bounced which will expose the root cause. After looking up the original email I see this is a account that forwards mail to a gmail account, and gmail rejected the forwarded mail because it was spam. /var/log/maillog.1.bz2:May 21 14:29:31 mail postfix/smtp[81526]: 3F635118B777: to=<*munged*@gmail.com>, orig_to=<*munged*>, relay=gmail-smtp-in.l.google.com[74.125.142.26]:25, delay=1.1, delays=0.26/0.05/0.39/0.45, dsn=5.7.1, status=bounced (host gmail-smtp-in.l.google.com[74.125.142.26] said: 550-5.7.1 [75.148.117.91 12] Our system has detected that this message is 550-5.7.1 likely unsolicited mail. To reduce the amount of spam sent to Gmail, 550-5.7.1 this message has been blocked. Please visit 550-5.7.1 http://support.google.com/mail/bin/answer.py?hl=en&answer=188131 for 550 5.7.1 more information. cl1si4050394igc.54 - gsmtp (in reply to end of DATA command)) Short of not forwarding to gmail, anything I can do so that this results in dropping the mail (the 'wrong' thing) instead of trying to generate the appropriate bounce (the 'right' thing)? -- Away with him! away with him! he speaks Latin.
