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? ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users