Alexandre Ellert: > > Wietse : > > You can push the problem back to the webservers, by using the the > > Postfix SMTP server's "reject_unverified_recipient" feature. > > > > With this, Postfix will make one connection for the recipient > > address, and then the Postfix SMTP server answers with 5XX to the > > web application when that recipient does not exist. > > > > There are no repeated connections, because Postfix stores the results > > in a cache (both positive and negative). > > Very nice, that way the customer website would get a bounce the > second time it sends to an invalid address.
No, it gets a bounce the first time. > > Wietse : > > For details: http://www.postfix.org/ADDRESS_VERIFICATION_README.html > > > > You'll have to adjust some settings so that Postfix replies with > > 5xx (by default it replies with 4xx to be on the safe side). > > I read carefully "Limitations of address verification" and I would > limit scope to those particular accounts which doesn't care about > email verification. In that case use: /etc/postfix/main.cf: smtpd_recipient_restrictions = ... check_sender_access hash:/etc/postfix/sender_access ... /etc/postfix/sender_access: x...@example.com reject_unverified_recipient example.net reject_unverified_recipient example.org reject_unverified_recipient Note that address verification requires that this Postfix MTA can talk directly to the remote MX host. Wietse
