Now, you may have the same address listed more than once, as a recipient; and each address has a different original recipient.
So how do you think the situation should be resolved?
Seems like if the submit process is going to "Run all recipient addresses through the system's alias database" and "Remove duplicate addresses from the recipient list", as its documentation describes, it should produce, as a result, a list of recipients that doesn't include duplcate destination addresses. If, as part of the duplicate removal, you want to retain a copy of the original addresses for the purposes of DSN's, it seems logical that each destination address be attached to a list of original recipient addresses which inserted it into the recipient list.
If you don't want to do it that way, I suppose each delivery module could comb through the control file and mark all deliveries to a recipient (regardless of the original recipient address, on this pass) with the result of its delivery attempt, but that seems like duplication of effort to me.
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
