On 6/8/2011 12:11 PM, Rich Wales wrote:
Given the smtpd_reject_unlisted_recipient parameter (which is "yes" by default), is there any reason to include reject_unlisted_recipient in my smtpd_recipient_restrictions? It would seem that doing this would be redundant -- or am I missing some subtle point?
The smtpd_reject_unlisted_recipient is performed after all the specified smtpd_recipient_restrictions entry.
Some people want to perform the check sooner in the process, so reject_unlisted_recipient can be specified where you want the test performed.
If you specify reject_unlisted_recipient, the later smtpd_reject_unlisted_recipient test is skipped (or rather, not repeated).
I also note there is an smtpd_reject_unlisted_sender parameter (which is "no" by default). What issues would I want to consider before deciding to enable this parameter in my configuration?
Some people intentionally send mail from users that can't receive mail. This is off by default to prevent surprises.
I would recommend using this restriction if it doesn't break anything.
-- Noel Jones
