YAM - Yet Another Mailer: Ticket Queryhttp://yam.ch/query?status=!closed&component=MIME+handling&order=type
The Open-Source Amiga E-mail suiteen-USYAM - Yet Another Mailerhttp://yam.ch/chrome/site/yam.gifhttp://yam.ch/query?status=!closed&component=MIME+handling&order=type
Trac 1.0.6.post2http://yam.ch/ticket/432
http://yam.ch/ticket/432#432: Accents not show correctly in mailsTue, 24 Sep 2013 04:46:52 GMTrmsyam<h2 id="Summary">Summary</h2>
<p>
When reading mails, the accents are not shown correctly but get replaced by a "?"
</p>
<h2 id="Stepstoreproduce">Steps to reproduce</h2>
<ol><li>simply open a mail
2.
</li></ol><h2 id="Expectedresults">Expected results</h2>
<p>
caracters like éàè as well as apostrophs should be shown like this
</p>
<h2 id="Actualresults">Actual results</h2>
<p>
these caracters get replaced by ? or other caracter combinations
</p>
<h2 id="Regression">Regression</h2>
<h2 id="Notes">Notes</h2>
Resultshttp://yam.ch/ticket/432#changeloghttp://yam.ch/ticket/600
http://yam.ch/ticket/600#600: in html files sent as attachments, non-breaking-spaces (typed in with alt_space) are transformedTue, 12 May 2015 20:09:09 GMTJosDuchIt<h2 id="Summary">Summary</h2>
<p>
Wheras Simplemail does send the same file containing non-breaking blanks undistorted, YAM2.10 Dev does ,
</p>
<h2 id="Stepstoreproduce">Steps to reproduce</h2>
<blockquote>
<p>
1.Insert the line
</p>
</blockquote>
<p>
"NBSstart NBSstop" in a html file
</p>
<ol start="2"><li>attach the file to a mail addressed to you
</li><li>Inspect the file attached to the received mail
</li></ol><p>
Look at the inserted line
</p>
<h2 id="Expectedresults">Expected results</h2>
<p>
Inserted line should still be the same:
"NBSstart NBSstop"
</p>
<h2 id="Actualresults">Actual results</h2>
<p>
"NBSstartÃÂÃÂ ÃÂÃÂ ÃÂÃÂ ÃÂÃÂ ÃÂÃÂ ÃÂÃÂ ÃÂÃÂ ÃÂÃÂ ÃÂÃÂ ÃÂÃÂ ÃÂÃÂ ÃÂÃÂ ÃÂÃÂ NBSstop" when looked at with CED (in CED the blanks in the preceding line appear as squares)
In IBrowse the line is presented as.
"NBSstartÃfÂ,Ã,Â ÃfÂ,Ã,Â ÃfÂ,Ã,Â ÃfÂ,Ã,Â ÃfÂ,Ã,Â ÃfÂ,Ã,Â ÃfÂ,Ã,Â ÃfÂ,Ã,Â ÃfÂ,Ã,Â ÃfÂ,Ã,Â ÃfÂ,Ã,Â ÃfÂ,Ã,Â ÃfÂ,Ã,Â NBSstop"
</p>
<h2 id="Regression">Regression</h2>
<h2 id="Notes">Notes</h2>
Resultshttp://yam.ch/ticket/600#changeloghttp://yam.ch/ticket/74
http://yam.ch/ticket/74#74: Implement format=flowed support!Thu, 04 Mar 2010 19:18:40 GMTdamato<p>
To solve long standing problems like the errorneous "&gt;From" quoting due to procmail and to be more future conform to other modern clients and implementation of the text/plain format=flowed is required. YAM would definitly benefit out of that, however some modifications to TextEditor.mcc might be require to make that new feature possible. So it might be a bigger job... However, here is the link to the <a class="acronym" href="http://www.ietf.org/rfc.html"><acronym title="IETF Request For Comment">RFC</acronym></a> explaining the format=flowed mechanism:
</p>
<p>
<a class="ext-link" href="http://www.ietf.org/rfc/rfc2646.txt"><span class="icon">​</span>http://www.ietf.org/rfc/rfc2646.txt</a>
</p>
<hr />
<p>
Moved from SF:<br />
<a class="ext-link" href="https://sourceforge.net/tracker/?func=detail&amp;aid=1356345&amp;group_id=13560&amp;atid=363560"><span class="icon">​</span>https://sourceforge.net/tracker/?func=detail&amp;aid=1356345&amp;group_id=13560&amp;atid=363560</a>
</p>
Resultshttp://yam.ch/ticket/74#changeloghttp://yam.ch/ticket/89
http://yam.ch/ticket/89#89: RFC-2369 compliant reply-to-list featureThu, 04 Mar 2010 19:54:30 GMTanonymous<p>
I would like to see a <a class="acronym" href="http://www.ietf.org/rfc.html"><acronym title="IETF Request For Comment">RFC</acronym></a>-2369 compliant reply to list feature for mailinglists
</p>
<p>
<a class="ext-link" href="http://www.faqs.org/rfcs/rfc2369.html"><span class="icon">​</span>http://www.faqs.org/rfcs/rfc2369.html</a>
</p>
<hr />
<p>
Moved from SF:<br />
<a class="ext-link" href="https://sourceforge.net/tracker/?func=detail&amp;aid=1688167&amp;group_id=13560&amp;atid=363560"><span class="icon">​</span>https://sourceforge.net/tracker/?func=detail&amp;aid=1688167&amp;group_id=13560&amp;atid=363560</a>
</p>
Resultshttp://yam.ch/ticket/89#changeloghttp://yam.ch/ticket/518
http://yam.ch/ticket/518#518: Rework the removal of attachmentsFri, 31 Jan 2014 12:21:53 GMTtboeckel<h2 id="Problem">Problem</h2>
<p>
Currently attachments can be deleted from a mail, but as explained in <a class="closed ticket" href="http://yam.ch/ticket/517" title="bug: wrong character conversation after deleting attachments (closed: fixed)">#517</a> the mail body will be reencoded as UTF8 as a fast workaround for the problem described in <a class="closed ticket" href="http://yam.ch/ticket/517" title="bug: wrong character conversation after deleting attachments (closed: fixed)">#517</a>. The drawback is that the original charset will get lost in this case, which might not be desireable.
</p>
<h2 id="Enhancementrecommendation">Enhancement recommendation</h2>
<p>
Recreate the raw mail after deleting the attachments just like creating a new mail with full support for the original charset. For this to work the usual struct Compose structure must be created with all single parts to be kept and finally the WriteOutMessage() function must be called to recreate the mail.
</p>
Resultshttp://yam.ch/ticket/518#changeloghttp://yam.ch/ticket/130
http://yam.ch/ticket/130#130: S/MIME supportFri, 05 Mar 2010 23:45:05 GMTdamato<p>
Besides the wanted GnuPG support for signing/encrypting messages, a future version of YAM should also probably consider implementing S/MIME. The current uptodate <a class="acronym" href="http://www.ietf.org/rfc.html"><acronym title="IETF Request For Comment">RFC</acronym></a> for S/MIME can be found here:
</p>
<p>
<a class="ext-link" href="http://tools.ietf.org/html/rfc5751"><span class="icon">​</span>http://tools.ietf.org/html/rfc5751</a>
</p>
<p>
Mailers like Thunderbird already support S/MIME and it seems together with AmiSSL such an S/MIME functionality can be implemented quite straight forward.
</p>
Resultshttp://yam.ch/ticket/130#changeloghttp://yam.ch/ticket/137
http://yam.ch/ticket/137#137: Replace flex-based scanner with re2c based oneFri, 05 Mar 2010 23:54:42 GMTdamato<p>
There seems to be a new, faster and easier scanner engine out there which looks quite promising. Even the <acronym title="Hypertext Preprocessor">PHP</acronym> people seem to have switched from a flex-based scanner to a re2c based one. Therefore it might be worth a look.
</p>
<p>
See here for more information: <a class="ext-link" href="http://re2c.org/"><span class="icon">​</span>http://re2c.org/</a>
</p>
<p>
It also supports the CONDITION support which we are using in our flex-based scanners, thus it should be relatively easy to use re2c instead of flex <img src="/chrome/emoticons/wink.png" alt=";)" class="emoticon" width="18" height="18" style="vertical-align: middle" />
</p>
Resultshttp://yam.ch/ticket/137#changelog