YAM - Yet Another Mailer: Ticket #3: Don't accept () as email delimitershttp://yam.ch/ticket/3
<p>
If &lt;&gt; are the only valid email delimiters as the
comments to feature request <a class="missing ticket">#583703</a> seem to imply,
YAM shouldn't accept () in the first place when
writing an email. Currently YAM won't complain at
all if you post a message with a From: header
like "name (user@host)".
</p>
<hr />
<p>
Moved from SF:<br />
<a class="ext-link" href="https://sourceforge.net/tracker/?func=detail&amp;aid=1753002&amp;group_id=13560&amp;atid=113560"><span class="icon">​</span>https://sourceforge.net/tracker/?func=detail&amp;aid=1753002&amp;group_id=13560&amp;atid=113560</a>
</p>
en-usYAM - Yet Another Mailerhttp://yam.ch/chrome/site/yam.gifhttp://yam.ch/ticket/3
Trac 1.0.4damatoWed, 03 Mar 2010 13:47:27 GMThttp://yam.ch/ticket/3#comment:1
http://yam.ch/ticket/3#comment:1
<p>
Well, the problem is here that ( and ) are prefectly valid characters for
including in the full email address. So e.g. something like "Jens (damato)
Langner &lt;Jens.Langner@…&gt;" is perfectly valid and should
therefore also be allowed in YAM. However, the ( and ) chars are clear
'comment' characters and not the delimiters for seperating the email part
from the real name part. So something like "Jens Langner
(Jens.Langner@…)" is definitly wrong and violates any <a class="acronym" href="http://www.ietf.org/rfc.html"><acronym title="IETF Request For Comment">RFC</acronym></a>.
</p>
<p>
So, <acronym title="In my opinion...">IMO</acronym> we should keep the possibility to add ( and ) to your real name.
However, YAM should never send any email with such a broken
recipient/sender adress and AFAIR it isn't possible to send such a mail
(apart from manually modifying the From: header line in the write window).
And if YAM should eventually receive such a broken email it should not try
to be smart any treat those ( ) chars as the realname&lt;&gt;email delimiters
instead of &lt;&gt; as this is calling for trouble... Broken mail are broken, and
nothing more <img src="/chrome/emoticons/smile.png" alt=":)" class="emoticon" width="18" height="18" style="vertical-align: middle" />
</p>
<hr />
<p>
Moved from SF. Original poster: damato
</p>
TicketdamatoWed, 03 Mar 2010 13:48:01 GMThttp://yam.ch/ticket/3#comment:2
http://yam.ch/ticket/3#comment:2
<p>
The whole point is that YAM *does* allow to send an email
with a From: line like "Name (user@…)", literally,
at least with my mail server. And yes, I tried this by
editing this header in the Write window.
</p>
<p>
If that's illegal, YAM is only contributing to the problem,
so it should throw an error immediately.
</p>
<hr />
<p>
Moved from SF. Original poster: tactica
</p>
TicketdamatoWed, 03 Mar 2010 13:48:34 GMThttp://yam.ch/ticket/3#comment:3
http://yam.ch/ticket/3#comment:3
<p>
Yes, you are right. YAM should not allow to send an email with such an
illegal From: and/or To: line whatsoever. So I will see how I can fix that
issue and raise an error instead. However, please note that YAm should also
make sure that it isn't possible to end up with such an address in any
automatic way. So please also check that it isn't possible to enter such an
illegal address in either the addressbook or any other <acronym title="Graphical User Interface">GUI</acronym> element in the
configuration, for example. But please keep in mind that something like
"Name (doe@…) &lt;doe@…&gt;" is valid even if it doesn't make sense.
</p>
<hr />
<p>
Moved from SF. Original poster: damato
</p>
TicketdamatoWed, 03 Mar 2010 13:50:35 GMThttp://yam.ch/ticket/3#comment:4
http://yam.ch/ticket/3#comment:4
<p>
According to <a class="acronym" href="http://www.ietf.org/rfc.html"><acronym title="IETF Request For Comment">RFC</acronym></a> 2282 even something like this is valid, although not
encouraged:
</p>
<pre class="wiki">From: Pete(A wonderful \) chap) &lt;pete(his account)@silly.test(his host)&gt;
To:A Group(Some people)
:Chris Jones &lt;c@(Chris's host.)public.example&gt;,
joe@example.org,
John &lt;jdoe@one.test&gt; (my dear friend); (the end of the group)
Cc:(Empty list)(start)Undisclosed recipients :(nobody(that I know))
</pre><p>
Text within () should be treated as (nested) comment which reduces the
examples above to something like this (if I understood the <a class="acronym" href="http://www.ietf.org/rfc.html"><acronym title="IETF Request For Comment">RFC</acronym></a> correctly):
</p>
<pre class="wiki">From: Pete &lt;pete@silly.test&gt;
To:A Group
:Chris Jones &lt;c@public.example&gt;,
joe@example.org,
John &lt;jdoe@one.test&gt;;
Cc:Undisclosed recipients :;
</pre><p>
Hence to be on the safe side we would need another lexical analyzer to
parse/check an email address. Simply forbidding () in the address part is
not enough.
</p>
<hr />
<p>
Moved from SF. Original poster: thboeckel
</p>
TicketdamatoWed, 03 Mar 2010 13:51:12 GMThttp://yam.ch/ticket/3#comment:5
http://yam.ch/ticket/3#comment:5
<p>
As the issue seems to require a rework of our current email address parser
routines and we are running out of time till the 2.5 release, I'll
reschedule that issue for the 2.6 release cycle.
</p>
<hr />
<p>
Moved from SF. Original poster: damato
</p>
TicketdamatoThu, 04 Mar 2010 13:20:58 GMTpriority changed; severity sethttp://yam.ch/ticket/3#comment:6
http://yam.ch/ticket/3#comment:6
<ul>
<li><strong>priority</strong>
changed from <em>major</em> to <em>undecided</em>
</li>
<li><strong>severity</strong>
set to <em>major</em>
</li>
</ul>
TicketdamatoThu, 04 Mar 2010 22:34:45 GMTcomponent changedhttp://yam.ch/ticket/3#comment:7
http://yam.ch/ticket/3#comment:7
<ul>
<li><strong>component</strong>
changed from <em>nightly build</em> to <em>undefined</em>
</li>
</ul>
TicketdamatoFri, 05 Mar 2010 08:54:08 GMTcc deletedhttp://yam.ch/ticket/3#comment:8
http://yam.ch/ticket/3#comment:8
<ul>
<li><strong>cc</strong>
<em>yamos-svn@…</em> removed
</li>
</ul>
TicketdamatoSun, 07 Mar 2010 10:40:21 GMTpriority, status, component changed; milestone sethttp://yam.ch/ticket/3#comment:9
http://yam.ch/ticket/3#comment:9
<ul>
<li><strong>priority</strong>
changed from <em>undecided</em> to <em>low</em>
</li>
<li><strong>status</strong>
changed from <em>new</em> to <em>accepted</em>
</li>
<li><strong>component</strong>
changed from <em>undefined</em> to <em>MIME handling</em>
</li>
<li><strong>milestone</strong>
set to <em>YAM 2.7</em>
</li>
</ul>
<p>
We do have to check if this ticket is still valid and how we can easily fix it for the next release.
</p>
TickettboeckelWed, 17 Nov 2010 12:16:35 GMTstatus, description changed; resolution sethttp://yam.ch/ticket/3#comment:10
http://yam.ch/ticket/3#comment:10
<ul>
<li><strong>status</strong>
changed from <em>accepted</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>worksforme</em>
</li>
<li><strong>description</strong>
modified (<a href="/ticket/3?action=diff&amp;version=10">diff</a>)
</li>
</ul>
<p>
I just checked this ticket again with lots of variations of names and addresses with and without bracket and for me YAM either correctly rejected them as invalid or surrounded the brackets with quotes to make them part of the real name.
</p>
<p>
Hence from my point of view there is nothing to be fixed.
</p>
<p>
Closing this one as "works for me".
</p>
<p>
Feel free to reopen this ticket if YAM is doing something wrong in this respect.
</p>
Ticket