D G Teed wrote: > On Thu, Nov 13, 2008 at 2:14 PM, mouss <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > If someone emailed > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>, it > will reject, > saying that user doesn't exist. Our users expect this feature. > If we told them bad addresses will cause email to be lost without > notification, they would not be happy. > > > if address is typoeduser, then reject it during the smtp > transaction while the "untrusted" client is still connected. once > you accept mail, you should no more send bounces, except in few > controlled situations. > > sure, losing mail is bad. but you should reject mail during the > smtp transaction. if your postfix is a lreay server and you can't > get the relay_recipient_maps, then you can use > reject_unverified_recipient (only for selected domains). > > > In this thread I've posted my postconf -n output. > > We user virtual_alias_maps and > smtpd_client_restrictions = reject_unlisted_recipient > is at the beginning of our list of restrictions.
client restrictions are checked on connect. reject_unlisted_recipient is not known until the recipient restrictions. > > This causes email to be rejected for non-delivery. We do not > relay to our Exchange or Cyrus server only to find out > at that stage the email address does not exist. Our mapping > file (virtual_alias_maps) is the complete list of all addresses and > what final server they go to. > > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > Does this not achieve the same result as using relay_recipient_maps ? > > virtual_alias_maps is a map that can rewrite an address across any address class. relay_recipient_maps is a verification map for relay_domains class. You basically will allow a catch all on the MX if a spammer knew the back end domain(s) with no relay_recipient_maps present. This may cause Backscatter. Your experience may vary of course. Brian
