Re: [courier-users] alias user in virtual tables

[Sam V. <mr...@co...>]

Mark Constable writes:

> Just a real low priority suggestion that may not be possible but having
> to have an extra alias@domain user entry in a virtual password table
> has always annoyed when using the same table with other services.
>
> ATM I am seeing 2 SQL lookups, one to check user id/password and another
> one to see if there is a alias@domain whereas the initial lookup could
> include one extra field to check for the alias option. Save a SQL query
> and also git rid of a lot of otherwise redundant alias database entries.
>
> Surely it would be possible to have the authdaemon check the same users
> entry and if there is a boolean yes/no "alias" column entry in a single
> lookup?

authdaemon makes these queries in response to a request from a client that  
connected to authdaemon.

The alias expansion occurs even before the message's control file gets  
written. The aliased-to addresses become the actual recipient addresses for  
the message, in the mail queue, and the alias is not looked up again.

Once a mail delivery attempt is made, then for addresses in one of the local  
domain the userid lookup takes place. By that time, a lot of water has  
passed under the bridge…