Hi,
Address-book whitelisting is a crucial feature, as it puts the user in control to decide which individual senders or which domains they want to trust. After spending a lot of time with customers and THEIR clients, them insisting that the whitelisting is not working no matter WHAT they tried, I've confirmed the following two bugs: 1. Addressbook Whitelisting attempts to find address book under the IMAIL ALIAS name, instead of resolving aliases to the proper IMAIL USER name! Example: [email protected] is configured as an ALIAS for [email protected] Emails addressed to aec@... will NOT be whitelisted, but emails addressed to "Anthony_Cuomo" will be whitelisted: Did not find [ [email protected] ] in [ [email protected] ] address book Finish Address Book WhiteList Vs. Skipping4 E-mail from [email protected]; whitelisted [[email protected]]. Finish Address Book WhiteList Obviously, Declude must NOT use the ALIAS name to attempt finding (non-existing) Address Books, it must use the Q file to learn the "final" delivery USER name, and use THAT for Addressbook validation! 2. The original implementation of the Addressbook Whitelist (by Scott) had allowed for a generic domain whitelist, by using: [email protected] to whitelist ANY email addresses ending with "@sender.com". When the addressbook lookup was converted to the current Imail Contact Database, someone forgot to implement the proper SQL query that checks the recipient's address book for the FULL match of EITHER, "[email protected]" OR "[email protected]" Since whitelisting is so critical in any "blacklisting" solution (like Declude), I would ask that both these bugs be addressed - and certainly am willing to put my money where my mouth is - whether through purchasing additional "support" tickets or whatever other requirements you have. Best Regards, Andy
