Aaron Stone wrote: > On Fri, Jan 14, 2005, Thomas Mueller <[EMAIL PROTECTED]> said: > > Currently: > >> > if (address is username) > >> > put username on delivery list > >> > else > >> > if (address has aliases) > >> > resolve aliases into deliveries and forwards > > Aaron's Proposal: > >> > if (address has aliases) > >> > resolve aliases into deliveries and forwards > >> > else > >> > if (address is username) > >> > put username on delivery list > > Thomas' Proposal: > > if (address is username) > > put username on delivery list > > if (address has aliases) > > resolve aliases into deliveries and forwards > > > > The only difficulty is that double delivery should be prevented in case > > username is [EMAIL PROTECTED] and there is an alias > > [EMAIL PROTECTED]>[EMAIL PROTECTED] > > Yeah, that's the situation I was hoping to avoid by way of the sequence of > logic. So what do we do with this: > > dbmail_users (id, user): > 1 [EMAIL PROTECTED] > 2 [EMAIL PROTECTED] > > dbmail_aliases (alias, deliver-to): > [EMAIL PROTECTED] 2 > > That is to say, we're trying to get all mail to '[EMAIL PROTECTED]' to land in > the INBOX of '[EMAIL PROTECTED]'. What happens: > > Currently: > Mail for '[EMAIL PROTECTED]' goes to user 1. > > Aaron's Proposal: > Mail for '[EMAIL PROTECTED]' goes to user 2. > > Thomas' Proposal: > Mail for '[EMAIL PROTECTED]' goes to user 2 and user 1. > > > I'm inclined to say that the question in this case is about what we *want* > to have happen. I can't think of any other demonstation cases / corner > cases right now, but let's keep the thinking caps on before doing anything > on this.
What about that one: I have a user [EMAIL PROTECTED], no aliases. Then I go to holiday and add an alias [EMAIL PROTECTED]>[EMAIL PROTECTED] I would expect that I only get a copy and every mail still is in my [EMAIL PROTECTED] INBOX. Thomas -- http://www.tmueller.com for pgp key (95702B3B)
