As a  matter of preference I hate being referred to as "Ireland, Martin" in conversation, and likewise I prefer to see my name in messages posted to newsgroups, blogs and this site in the form my parents gave me "Martin Ireland".   I know, I know, the good people at MS give us the choice, so "they" can produce a list in surname order in their address book.

 But on a serious note for this thread, this issue has been raised before, as has the issue of raw data or translated (to UTF8).   This never used to be a problem when all SMTP traffic was simple Ascii.

Martin

I am afraid that Pegasus (also the latest version 4.41) has the same problem as Mozilla based mail clients which is described in https://bugzilla.mozilla.org/show_bug.cgi?id=254519 

My company uses M$ exchange and M§ Outlook as main mail infrastructure but allows to use other mail clients. I encounter problems whenever I get mail from a colleague who has national characters (french accented  vowals, German umlauts or the like) in his name.

Outlook / Exchange  fill the name within the From:-Header with "last_name, first_name", and (beacause og the comma) correctly enclose this name with double quotes. However, if the name contains national characters, exchange or outlook encode the name by UTF8, and then no double quote is necessary any more. 

 Example: a sender "Mary Smith" will create a from header
From: "Smith, Mary" <mary.smith@some.com.example>

and if I press "reply", Pegasus will copy this entire  line into the "to" header line.  Everything is OK so far.

A sender with a German Umlaut, e.g., "Günter Schmidt", will  create  a header line:
From: =?iso-8859-1?Q?Schmidt=2C_G=FCnter?= <Guenter.Schmidt@some.com.example>

i.e. no double quotes. Displayinh this mail, Pegasus displays ist as
From: Schmidt, Günter <Guenter.Schmidt@some.com.example>

and ig I reply, it copies the decoded header line into the To-header. The consequence is that to To header loks as foillows:
To: Schmidt, Günter <Guenter.schmidt@some.com.example>

and - interpreting the non-quoted comma as a seprating character between two mail recipielnts - tries to send the reply to two adressees, one of them will of course fail.

Yes, I know that the exchange admins might be able to reconfigure their program in order to always enclose the name in quotes. But they state that they properly observe the RFCs, and the ywill not do that. They say that Pegasus should not copy the decoded From: header line but instead copy the encoded header line into the reply's address field, and then, everything will be OK. Yes, they are right.

I tried to find an option within Pegasus to achieve this - but I couldnt find any. U wozld be really grateful if anyone has an idea.

Best regards

 

Is this at all related to Mercury? Otherwise it might be a good idea to repost it in the Pegasus section!

/Rolf 

I can confirm this bug.

And the error message that is displayed after trying to send such a reply is confusing for an average user ("'SCHMIDT' is no valid address..."). There is no hint that the comma is the problem.