Stack Exchange Network
Stack Exchange network consists of 181 Q&A communities including
Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
The best answers are voted up and rise to the top
9 years, 3 months ago
I would like Postfix to generate and contact via Mailer-Daemon the sender recipient when the following case occurs
Bad recipient address syntax.
I've been reading through Postfix docs but haven't found the right directive, any advice please?
Transcript of session follows.
Out: 220 mail.mydomain.es ESMTP Postfix
In: EHLO mail.mydomain.es
Out: 250-SIZE 10240000
Out: 250-AUTH PLAIN LOGIN CRAM-MD5 DIGEST-MD5
Out: 250 DSN
In: AUTH LOGIN
Out: 334 VXNlcm5hbWU6
Out: 334 UGFzc3dvcmQ6
Out: 235 2.7.0 Authentication successful
In: MAIL FROM:<email@example.com>
Out: 250 2.1.0 Ok
In: RCPT TO:<firstname.lastname@example.org>
Out: 250 2.1.5 Ok
In: RCPT TO:<"Foo - Bar <email@example.com>FooBar FB">
Out: 501 5.1.3 Bad recipient address syntax
Out: 250 2.0.0 Ok
Out: 221 2.0.0 Bye
Feb 24, 2014 at 19:13
508 2 2 gold badges 9 9 silver badges 27 27 bronze badges
The sending client should handle this case. Postfix should not accept the message for the invalid recipient. From the dialog you have included it is behaving correctly. It is the responsibility of the sending software to provide the appropriate notifications.
If it has accepted the message, the sender may be fake so you do not want to send a bounce message. If you do send a bounce message after the message has been accepted. Sending such backscatter spam is bad practice, and may reduce the reputation of your server. Servers that receive backscatter spam may refuse your mail or assign it to the spam box.
Feb 25, 2014 at 0:55
27.7k 3 3 gold badges 37 37 silver badges 69 69 bronze badges
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our
Accept all cookies
Necessary cookies only