I believe your proposed method is wise as it preserves the most options for the
admin with the least bother AFAICT.
Please comment quick so they can do a fix :) and I can tell my customers when
it might be working :)
- April
----------------------------------------------------------------------
aaron - 14-Jan-05 01:59 CET
----------------------------------------------------------------------
Oh my, I didn't consider that side of the situation. In DBMail 1.x, the
alias must always exist, even if the username is a full email address. A
number of people running such sites complained, and indeed it does seem
silly. So I made delivery check the users table first -- and not the
aliases table at all if it sees something.
The change that we'd need is to check the aliases table, too, and abide by
it if the delivery address is a forward.
I'll repost this on the mailing list, too -- but are there any semantics
that would be ruined if we changed from:
if (address is username)
put username on delivery list
else
if (address has aliases)
resolve aliases into deliveries and forwards
To:
if (address has aliases)
resolve aliases into deliveries and forwards
else
if (address is username)
put username on delivery list
Bug History
Date Modified Username Field Change
======================================================================
13-Jan-05 21:11OutboundIndex New Bug
14-Jan-05 01:59aaron Bugnote Added: 0000533
======================================================================
