Community Discussions and Support
Address Bug was "Who gets the reply?"

As far as I understand RFC2047 there is no need to worry about the comma (=2C) in the encoded word. I.e. as I understand it

"Lastname, Firstname" 

<jxyz@abc.com>

and

=?iso-8859-1?Q?Lastname=2C_Firstname?= <jxyz@abc.com>

are legal addresses with the same recipient. But Pegasus transforms the latter from field to the reply address

 

=?iso-8859-1?Q?Lastname?=, Firstname <jxyz@abc.com>

I think this violates RFC2047 which says: "IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's
  by an RFC 822 parser". Since this is the case here, Pegasus should not split up the encoded word.

P.S. Sorry for not providing screenshots, but I can't publish someone else's email address in a public forum. 

&lt;p&gt;As far as I understand RFC2047 there is no need to worry about the comma (=2C) in the encoded word. I.e. as I understand it&lt;/p&gt;&lt;p&gt;&quot;Lastname, Firstname&quot;&amp;nbsp; &amp;lt;jxyz@abc.com&amp;gt; &lt;/p&gt;&lt;p&gt;and&lt;/p&gt;&lt;p&gt;=?iso-8859-1?Q?Lastname=2C_Firstname?= &amp;lt;jxyz@abc.com&amp;gt;&lt;/p&gt;&lt;p&gt;are legal addresses with the same recipient. But Pegasus transforms the latter from field to the reply address&lt;/p&gt;&lt;p&gt;&amp;nbsp; =?iso-8859-1?Q?Lastname?=, Firstname &amp;lt;jxyz@abc.com&amp;gt; &lt;/p&gt;&lt;p&gt;I think this violates RFC2047 which says: &quot;IMPORTANT: &#039;encoded-word&#039;s are designed to be recognized as &#039;atom&#039;s &amp;nbsp; by an RFC 822 parser&quot;. Since this is the case here, Pegasus should not split up the encoded word.&lt;/p&gt;&lt;p&gt;P.S. Sorry for not providing screenshots, but I can&#039;t publish someone else&#039;s email address in a public forum.&amp;nbsp;&lt;/p&gt;

I am no expert on email adresses and don't know how email programs are supposed to handle "encrypted words".

However:

The FROM field reads 

=?iso-8859-1?Q?L=F6stname=2C_Firstname?= <email address>

and Pegasus replies to

=?iso-8859-1?Q?L=F6stname?=, Firstname <email address>

This is probably not as it should be.

&lt;p&gt;I am no expert on email adresses and don&#039;t know how email programs are supposed to handle &quot;encrypted words&quot;.&lt;/p&gt;&lt;p&gt;However: &lt;/p&gt;&lt;p&gt;The FROM field reads&amp;nbsp; &lt;/p&gt;&lt;p&gt;=?iso-8859-1?Q?L=F6stname=2C_Firstname?= &amp;lt;email address&amp;gt; &lt;/p&gt;&lt;p&gt;and Pegasus replies to&lt;/p&gt;&lt;p&gt; =?iso-8859-1?Q?L=F6stname?=, Firstname &amp;lt;email address&amp;gt;&lt;/p&gt;&lt;p&gt;This is probably not as it should be. &lt;/p&gt;

[quote user="vdhagen"]I am no expert on email adresses and don't know how email programs are supposed to handle "encrypted words".[/quote]

... encoded, not encrypted ...

[quote user="vdhagen"]

The FROM field reads  

=?iso-8859-1?Q?L=F6stname=2C_Firstname?= <email address>

and Pegasus replies to

 =?iso-8859-1?Q?L=F6stname?=, Firstname <email address>[/quote]

??? Please provide a screenshot, I have no idea what this is supposed to mean. If this is the same issue already reported why did you create another thread? Aside from this David Harris has been notified about the issue reported in the original thread. His reply was something to the extent of I didn't know about such an issue ... ???

&lt;p&gt;[quote user=&quot;vdhagen&quot;]I am no expert on email adresses and don&#039;t know how email programs are supposed to handle &quot;encrypted words&quot;.[/quote]&lt;/p&gt;&lt;p&gt;... &lt;em&gt;encoded&lt;/em&gt;, not encrypted ...&lt;/p&gt;&lt;p&gt;[quote user=&quot;vdhagen&quot;] The FROM field reads &amp;nbsp;&lt;/p&gt;&lt;p&gt;=?iso-8859-1?Q?L=F6stname=2C_Firstname?= &amp;lt;email address&amp;gt; &lt;/p&gt;&lt;p&gt;and Pegasus replies to&lt;/p&gt;&lt;p&gt;&amp;nbsp;=?iso-8859-1?Q?L=F6stname?=, Firstname &amp;lt;email address&amp;gt;[/quote]&lt;/p&gt;&lt;p&gt;??? Please provide a screenshot, I have no idea what this is supposed to mean. If this is the same issue already reported why did you create another thread? Aside from this David Harris has been notified about the issue reported in the original thread. His reply was something to the extent of &lt;em&gt;I didn&#039;t know about such an issue&lt;/em&gt; ... ???&lt;/p&gt;
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

[quote user="vdhagen"]

I am no expert on email adresses and don't know how email programs are supposed to handle "encrypted words".

=?iso-8859-1?Q?L=F6stname=2C_Firstname?= <email address>

and Pegasus replies to

=?iso-8859-1?Q?L=F6stname?=, Firstname <email address>


[/quote]

The above lines show the reply goes to two addresses separated by a comma.

If you use the right side of the split Reply button and set default options and then do your reply using the Reply button what is selected for the default address to be used? Is it replying to the From or the Reply address or both or something different. Try with all unchecked once and then also with only the reply address checked. Is the action the same then?

Is the message sender using any default reply address or is it blank indication reply to the From address is to be used?

[quote user=&quot;vdhagen&quot;]&lt;p&gt;I am no expert on email adresses and don&#039;t know how email programs are supposed to handle &quot;encrypted words&quot;.&lt;/p&gt;=?iso-8859-1?Q?L=F6stname=2C_Firstname?= &amp;lt;email address&amp;gt; &lt;p&gt;and Pegasus replies to&lt;/p&gt;&lt;p&gt; =?iso-8859-1?Q?L=F6stname?=, Firstname &amp;lt;email address&amp;gt;&lt;/p&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt;[/quote]&lt;/p&gt;&lt;p&gt;The above lines show the reply goes to two addresses separated by a comma.&lt;/p&gt;&lt;p&gt;If you use the right side of the split Reply button and set default options and then do your reply using the Reply button what is selected for the default address to be used? Is it replying to the From or the Reply address or both or something different. Try with all unchecked once and then also with only the reply address checked. Is the action the same then?&lt;/p&gt;&lt;p&gt;Is the message sender using any default reply address or is it blank indication reply to the From address is to be used? &lt;/p&gt;

I always use reply with option. The sender does not provide a reply address ( there is a field "Return Path: <email address>" but I can't choose that in Pegasus as destination for the reply). Therefore, the reply goes to the "From" field (regardless of whether it is checked or not).

I started a new thread because my curiosity about "Who gets the reply?" was satisfied and I thought I reported a bug in Pegasus' treatment of "encoded words".

BTW,  if the encoded word in the From field does not contain a comma (=2C), e.g. =?iso-8859-1?Q?L=F6stname_Firstname?= <email address>, Pegasus creates the reply address =?iso-8859-1?Q?L=F6stname_Firstname <email address>?=

&lt;p&gt;I always use reply with option. The sender does not provide a reply address ( there is a field &quot;Return Path: &amp;lt;email address&amp;gt;&quot; but I can&#039;t choose that in Pegasus as destination for the reply). Therefore, the reply goes to the &quot;From&quot; field (regardless of whether it is checked or not).&lt;/p&gt;&lt;p&gt;I started a new thread because my curiosity about &quot;Who gets the reply?&quot; was satisfied and I thought I reported a bug in Pegasus&#039; treatment of &quot;encoded words&quot;.&lt;/p&gt;&lt;p&gt;BTW,&amp;nbsp; if the encoded word in the From field does not contain a comma (=2C), e.g. =?iso-8859-1?Q?L=F6stname_Firstname?= &amp;lt;email address&amp;gt;, Pegasus creates the reply address =?iso-8859-1?Q?L=F6stname_Firstname &amp;lt;email address&amp;gt;?= &lt;/p&gt;

[quote user="vdhagen"]BTW,  if the encoded word in the From field does not contain a comma (=2C), e.g. =?iso-8859-1?Q?L=F6stname_Firstname?= <email address>, Pegasus creates the reply address =?iso-8859-1?Q?L=F6stname_Firstname <email address>?= [/quote]

Of course it does, that's what RFC 5322 says and Jerry explained in his post: A comma is a special character used to separate email addresses in address headers, that's why it can only be used in addresses (i.e. their informal parts) with special precautions as explained in RFC 5322.

&lt;p&gt;[quote user=&quot;vdhagen&quot;]BTW,&amp;nbsp; if the encoded word in the From field does not contain a comma (=2C), e.g. =?iso-8859-1?Q?L=F6stname_Firstname?= &amp;lt;email address&amp;gt;, Pegasus creates the reply address =?iso-8859-1?Q?L=F6stname_Firstname &amp;lt;email address&amp;gt;?= [/quote]&lt;/p&gt;&lt;p&gt;Of course it does, that&#039;s what RFC 5322 says and Jerry explained in his post: A comma is a &lt;em&gt;special character&lt;/em&gt; used to separate email addresses in address headers, that&#039;s why it can only be used in addresses (i.e. their informal parts) with special precautions as explained in RFC 5322.&lt;/p&gt;
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft