Add display name when sending emails

Description

Ref : https://groups.google.com/forum/?nomobile=true#!topic/idempiere/1drqoFpiWEY

For sender, idea is to add 2 user preferences :

  • SentEmailFromDisplayNameType : list with 3 values (0-Nothing ; 1-UserName ; 2-Text)

  • SentEmailFromDisplayName : text displays when SentEmailFromDisplayNameType = 2


For recipients, it will depends on the content of AD_User.EMail ;
-> If you want to use personal in email as sender - then you fill your user email as "Nicolas <nmi...@mailserver.com>"
-> If you don't want it, then as usual just "nmi...@mailserver.com"

Environment

None

Attachments

1

Activity

Nicolas Micoud 
July 17, 2018 at 1:11 PM

Hi ,
Using new fields could allow to handle different use cases (for instance, for emails sent from process1, i would like to display "Nicolas", and for process2, i would prefer "Support").

But, that could be achieved by filling accordingly the "from" of EMail.EMail

Thanks,

Nicolas

Carlos Ruiz 
July 9, 2018 at 7:23 PM

Hi ,

Please check the committed approach, it is different from yours.

I still don't get why this needs to be a user preference. IMHO it all depends on how the emails are saved in the system.

If in a user the email is defined as
carlos@dominio.com
then it doesn't have a personal address, but if is defined as
Carlos <carlos@dominio.com>
then - it has and uses a personal address. I think this is not a user preference, more like a company communication definition, and is configurable in the email addresses themselves.

Now, I found in WEMailDialog that it's not working well with personal names with spaces (a very common case) - so I dropped the space in the StringTokenizer.

Still there would be a problem with "personal" addresses containing commas or semicolons.

Regards,

Carlos Ruiz

Nicolas Micoud 
June 15, 2018 at 12:49 PM

Hi ,

Please find a patch that allow to set display name for sender and recipient (To and Cc).

Regards,

Nicolas

Fixed

Details

Assignee

Reporter

Labels

Priority

Created May 25, 2018 at 3:20 PM
Updated September 1, 2018 at 11:01 AM
Resolved July 9, 2018 at 7:23 PM