Sam Varshavchik wrote:
Gordon Messmer writes:
Maybe a better scenario to illustrate my concern would be this:
A user send an email to an alias that points off-site. Courier can't
contact the primary MX immediately, so it tries a backup MX. The
backup MX doesn't have a list of users, so it accepts the message in
order to relay it later. When the primary MX comes back up, the
backup MX tries to send the email, but the user no longer exists
(perhaps he's left that company). The backup MX has been instructed
not to give DSNs, so the original sender never knows that the intended
recipient doesn't receive the mail.
I've yet to see a forwarding alias being involved in this scenario in
any way.
I can conceive of scenarios more likely to occur if you like. Perhaps
your Courier server is on a private network, and it relays mail out
through a host dedicated to that task (maybe that one provides
additional filtering). Your aliases to off-site hosts, then, get
delivered to your "smart host" with instructions not to notify users
when there are delivery failures.
I just think the idea of asking for no DSNs on aliases is ill conceived.
Situations will arise where you want a DSN and won't get one.
If you think I'm wrong, at least help me out by pointing me at the
general location where I should modify courier to suit my needs, please.
PS:
I apologise for taking this off-list... That was accidental.
7 messages in net.sourceforge.lists.courier-users[courier-users] Re: another question ...
