Running ISPCFG3 on Debian Wheezy according to Perfect Server with nginx tutorial I was just checking my mail logs and found this occurrance where an incoming email triggers a vacation response which is sent with a blank sender and thus bounces: Code: May 20 18:21:17 h2118175 dovecot: lda(franziska@incoming): sieve: msgid=<[email protected]>: stored mail into mailbox 'INBOX' May 20 18:21:17 h2118175 postfix/pickup[256358]: 746DB4240D5: uid=5000 from=<> May 20 18:21:17 h2118175 dovecot: lda(franziska@incoming): sieve: msgid=<[email protected]>: sent vacation response to <SRS0+VpXz=2S=acw-bizdev.com= [email protected]> May 20 18:21:17 h2118175 postfix/cleanup[260112]: 746DB4240D5: message-id=<[email protected]> May 20 18:21:17 h2118175 postfix/pipe[260133]: 0284D4240CF: to=<franziska@incoming>, relay=dovecot, delay=0.47, delays=0.15/0.01/0/0.31, dsn=2.0.0, status=sent (delivered via do vecot service) May 20 18:21:17 h2118175 postfix/qmgr[168127]: 0284D4240CF: removed May 20 18:21:17 h2118175 postfix/qmgr[168127]: 746DB4240D5: from=<>, size=953, nrcpt=1 (queue active) May 20 18:21:18 h2118175 postfix/smtpd[260129]: connect from localhost[127.0.0.1] May 20 18:21:18 h2118175 postfix/smtpd[260129]: 0F989424081: client=localhost[127.0.0.1] May 20 18:21:18 h2118175 postsrsd[260131]: srs_forward: <""> not rewritten: No at sign in sender address May 20 18:21:18 h2118175 postsrsd[260132]: srs_reverse: <[email protected]> rewritten as <[email protected]> May 20 18:21:18 h2118175 postfix/cleanup[260112]: 0F989424081: message-id=<[email protected]> May 20 18:21:18 h2118175 postfix/qmgr[168127]: 0F989424081: from=<>, size=1532, nrcpt=1 (queue active) May 20 18:21:18 h2118175 postfix/smtpd[260129]: disconnect from localhost[127.0.0.1] May 20 18:21:18 h2118175 amavis[248807]: (248807-08) Passed CLEAN {RelayedInbound}, <> -> <[email protected]>, Message-ID: <dovecot-s [email protected]>, mail_id: zR_ZkiCsDA2K, Hits: -1.9, size: 953, queued_as: 0F989424081, 620 ms May 20 18:21:18 h2118175 postfix/smtp[260114]: 746DB4240D5: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.79, del ays=0.17/0/0/0.62, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 0F989424081) May 20 18:21:18 h2118175 postfix/qmgr[168127]: 746DB4240D5: removed May 20 18:21:46 h2118175 postfix/smtp[260138]: 0F989424081: to=<[email protected]>, orig_to=<[email protected]>, relay=smtp. secureserver.net[68.178.213.203]:25, delay=28, delays=0.11/0.01/16/12, dsn=5.1.0, status=bounced (host smtp.secureserver.net[68.178.213.203] said: 550 5.1.0 <> Blank From: addresses are not allowed. Please provide a valid From: IB501 <http://x.co/srbounce> (in reply to MAIL FROM command)) May 20 18:21:46 h2118175 postfix/qmgr[168127]: 0F989424081: removed May 20 18:22:16 h2118175 postfix/smtpd[257668]: disconnect from p3plsmtpa09-04.prod.phx3.secureserver.net[173.201.193.233]
The field is set to <> on purpose: See the following links: http://tools.ietf.org/html/rfc3834#section-3.3 http://tools.ietf.org/html/rfc5230#section-5.1 This setting prevents responders from replying to this message (when correctly configured), e.g. a delivery report should not be sent and prevent looping back and forth mail. So you should not change this.
Ok, I get what you are saying and read those links. So this is the safe solution. I guess the other party refusing to accept an email without sender is in the minority then and can be safely ignored?
