From: Gordon Messmer [mailto:[EMAIL PROTECTED]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.
This is precisely the way that my network operates. Outgoing mail is sent through a gateway server for AntiVirus filtering. Courier is currently only used for our hosted email accounts, but if we did switch our main server from Exchange to Courier (which I would like to do), this issue would probably come up at some point.
I'm still waiting for an address alias to enter the picture.
This also has nothing to do with address aliasing.
Unless you actually add every mailbox involved into $sysconfdir/aliases, none of this is relevant.
pgp00000.pgp
Description: PGP signature
