This is a re-request of this issue : http://drupal.org/node/277848.

I would like to have listhandler use the email address rather than the name when it checks for users.

After looking at using mailalias as suggested in the previous request I decided against it because I have hundreds of users/emails that needs to be defined and maintained for mailalias to work.

And... I have seen a lot of instances where the users change email clients, causing the name to change.

Example: When email is send from Lotus notes I get this but send from the web client I see

Thanks
Ian

Comments

cor3huis’s picture

cor3huis CreditAttribution: cor3huis commented

@pcs305, you wrote:

...but send from the web client I see

The line ends at "...I see". Did you forget to post your example? If so, please add it, this help looking into your request.

IMHO the feature request is one to have a one off benefit in your specific situation. Could you give a more descriptive usecase where your improvement proposal is discussed? This would help you getting more serious attention to your feature request.

pcs305’s picture

pcs305 CreditAttribution: pcs305 commented

My apologies. I think I added some tags that was incorrect.

What I experienced was this: The listserv I use have a web interface as well as the email interface.
So some users use email and the web interface to reply to posts. the naming conventions for email and the web interface is not the same.
IE: the user's lotus notes have the email name/address string as Smith,John <john.smith@example.com> but with the web interface the user register as "John Smith" and his name/address string is John Smith<john.smith@example.com>.

The same happens where the user uses ,for example, a Lotus email client and then a web client for the same email address.

The last name first name may be different from client to client for the same email address. This does not work well with listhandler.

Thank you.

cor3huis’s picture

cor3huis CreditAttribution: cor3huis commented

Additional thought:

In the rare case that users, which can have multiple emails added to their user account via a module like multiple_emails would have identical emailaddresses the check would then revert to the username and if not possible disallow the post.

This feature must have a good writeup of all possible scenarios before an implementation can be created.

kentr’s picture

kentr CreditAttribution: kentr commented

Initial user detection is actually done by mailhandler, and it's pluggable. Listhandler only creates a new user if mailhandler doesn't find the user.

Look for HOOK_mailhandler_authenticate_info().

which can have multiple emails added to their user account via a module like multiple_emails would have identical emailaddresses the check would then revert to the username and if not possible disallow the post.

I have a starter plugin for multiple_email, if you're interested. Contact me directly via profile contact form, I don't check d.o. much.