I know that it's happening. I have not researched why it's happening. Alias expansion is tricky, and there might be a reason for that, I don't recall all the nitty gritty details off the top of my head. I'll look at it, eventually, but I don't see this as a hold-the-presses major malfunction.
A few debugging statements inserted, and I get this in my logs:
Jun 25 11:31:07 wanderlust submit: ChkRecipient run with key: local/gordon!!500!500!/home/gordon!!/gordon/rfc822;[EMAIL PROTECTED], gdbm not open
Jun 25 11:31:07 wanderlust submit: ChkRecipient run with key: local/gordon!!500!500!/home/gordon!!/gordon/rfc822;[EMAIL PROTECTED], gdbm not open
Jun 25 11:31:07 wanderlust submit: ChkRecipient run with key: local/gordon!!500!500!/home/gordon!!/gordon, gdbm not open
Now, if I change submit.C to log envdsn and run ChkRecipient even when envdsn != "N", I get this:
Jun 25 12:19:34 wanderlust submit: envdsn is:
Jun 25 12:19:34 wanderlust submit: ChkRecipient run with key: local/gordon!!500!500!/home/gordon!!/gordon, gdbm not open
Jun 25 12:19:34 wanderlust submit: ChkRecipient run with key: local/gordon!!500!500!/home/gordon!!/gordon/rfc822;[EMAIL PROTECTED], gdbm not open
Jun 25 12:19:34 wanderlust submit: envdsn is:
Jun 25 12:19:34 wanderlust submit: ChkRecipient run with key: local/gordon!!500!500!/home/gordon!!/gordon, gdbm not open, Lookup returned true.
Jun 25 12:19:34 wanderlust submit: ChkRecipient run with key: local/gordon!!500!500!/home/gordon!!/gordon/rfc822;[EMAIL PROTECTED], gdbm not open
Jun 25 12:19:34 wanderlust submit: envdsn is:
Jun 25 12:19:34 wanderlust submit: ChkRecipient run with key: local/gordon!!500!500!/home/gordon!!/gordon, gdbm not open, Lookup returned true.
Jun 25 12:19:34 wanderlust submit: ChkRecipient run with key: local/gordon!!500!500!/home/gordon!!/gordon, gdbm not open
And this time, only one recipient is added to the message, as it should be. I'm not sure what the proper fix is, since I'm not clear on why the DSN options would affect how you look for duplicates. I'm also not sure why you'd ever bother to consider the original recipient when looking for duplicates in the list of actual recipients.
In any case, I hope that clarifies why it's happening, and I don't expect that fixing the problem will prove difficult.
Thanks for your time MSG
------------------------------------------------------- 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
