YAM - Yet Another Mailer: Ticket Queryhttp://yam.ch/query?status=!closed&platform=All&order=id
The Open-Source Amiga E-mail suiteen-USYAM - Yet Another Mailerhttp://yam.ch/chrome/site/yam.gifhttp://yam.ch/query?status=!closed&platform=All&order=id
Trac 1.0.6.post2http://yam.ch/ticket/17
http://yam.ch/ticket/17#17: Don't just remove "two-chars:" on replyWed, 03 Mar 2010 15:39:08 GMTpadrino<p>
I think it is not nice that YAM removes any "two chars and colon"-strings on reply from the subject. E.g. a subject starting with "OT:&#34; should keep this string. Or try to send a MAC-Addresse like &#34;AB:CE:1A:0F" and see what's left of it. <img src="/chrome/emoticons/smile.png" alt=":-)" class="emoticon" width="18" height="18" style="vertical-align: middle" />
</p>
<hr />
<p>
Moved from SF:<br />
<a class="ext-link" href="https://sourceforge.net/tracker/?func=detail&amp;aid=1042997&amp;group_id=13560&amp;atid=464455"><span class="icon">​</span>https://sourceforge.net/tracker/?func=detail&amp;aid=1042997&amp;group_id=13560&amp;atid=464455</a>
</p>
Resultshttp://yam.ch/ticket/17#changeloghttp://yam.ch/ticket/124
http://yam.ch/ticket/124#124: Rework/Improvement of mailing-list functionalityFri, 05 Mar 2010 23:25:03 GMTdamato<p>
The current mailing-list feature of YAM is more than just plainly useless and unintuitive. Currently a user has to configure a mailing list by creating a new folder and configuring the mailing list settings in the folder settings. This, however, seems to be somewhat awkward and not very intuitive and cumbersome.
</p>
<h2 id="Proposedchange">Proposed change</h2>
<p>
A possible change/improvement could be:
</p>
<ul><li>move the folder-wise mailing list configuration to the global YAM config window (own section)
</li><li>a user should be able to configure a mailing list in the YAM config using the following settings:
<ol><li>configure mailing list address (To)
</li><li>configure if a mailing list sets a Reply-To: header or not (important for proper Mail-Reply-To support).
</li><li>set an optional destination folder where incoming mails should be moved to (this should generate hidden filter rules to move the mail to that folder based on To, etc. address)
</li><li>allow to setup the above settings semi-automatically like currently possible in the folder settings.
</li></ol></li><li>the Mail-Reply-To and Mail-Followup-To features should respect these new configuration settings.
</li><li>the mailing-list To-addresses should be suggested when creating a new mail and entering something in the To recipient gadget
</li><li>when starting to create a new mail while being in a folder linked to a particular mailing list the write window should immediately contain the To address of that mailing list in the To recipient gadget.
</li></ul>Resultshttp://yam.ch/ticket/124#changeloghttp://yam.ch/ticket/134
http://yam.ch/ticket/134#134: Add "Stop" Toolbar button which aborts e.g. filteringFri, 05 Mar 2010 23:49:47 GMTdamato<p>
As soon as we have implemented the user-definable toolbars we ought to add a "Stop" toolbar button in case there is some action in progress which might be able to be aborted (e.g. filtering, index scanning etc.)
</p>
Resultshttp://yam.ch/ticket/134#changeloghttp://yam.ch/ticket/246
http://yam.ch/ticket/246#246: Embedded mail pane to be displayed verticallyTue, 18 Jan 2011 06:56:03 GMTSprocki<h2 id="Summary">Summary</h2>
<p>
An option is wanted to flip the embedded mail view from horizontal to vertical view to place it left or right to the mail list.
</p>
<h2 id="Expectedresults">Expected results</h2>
<p>
Having a second checkmark in Config/Look&amp;Feel to allow switching from horizontal to vertical view plus a checkmark for either placing the embedded mail view in the middle between folder list and mail list per folder or on the right beneath mail list.
a) |Folder list|Mail preview|Mail list| or
b) |Folder list|Mail list|Mail preview|
</p>
Resultshttp://yam.ch/ticket/246#changeloghttp://yam.ch/ticket/267
http://yam.ch/ticket/267#267: Mark E-Mails with different priorityFri, 15 Jul 2011 00:12:47 GMTopiopi<p>
Mark E-Mails with different priority
</p>
<h2 id="Problem">Problem</h2>
<p>
YAM has only one level of mark an E-Mail (on or off)
</p>
<h2 id="Analysis">Analysis</h2>
<p>
YAM change the Filename and add an "M" if the mail is marked.
</p>
<h2 id="Enhancementrecommendation">Enhancement recommendation</h2>
<p>
It should be easy to change that to different levels.
E.g. all mails which are already marked get Priority 0.
All future mails could get an M1...M9 into the filename to differentiate the levels.
The level could be displayed with a picture like now but with a number into the picture.
The mark menu should get an sub menu for the different levels.
What do you think about that?
</p>
Resultshttp://yam.ch/ticket/267#changeloghttp://yam.ch/ticket/411
http://yam.ch/ticket/411#411: How about toggable status iconsWed, 21 Aug 2013 20:43:39 GMTAmigaPhil<h2 id="Problem">Problem</h2>
<p>
none
</p>
<h2 id="Analysis">Analysis</h2>
<p>
Status icons are statics. You change the status of a message for example from the contextual menu (RM<img src="/chrome/emoticons/cool.png" alt="B)" class="emoticon" width="18" height="18" style="vertical-align: middle" />.
</p>
<h2 id="Enhancementrecommendation">Enhancement recommendation</h2>
<p>
How about to make some of the status icons clickable (LM<img src="/chrome/emoticons/cool.png" alt="B)" class="emoticon" width="18" height="18" style="vertical-align: middle" /> so that you can change the status with a single mouse click, like with Evolution ?
Examples:
New toggles to Read
Read -&gt; Unread
Unread -&gt; Read
Unmark -&gt; Mark
Mark -&gt; Unmark
and so on (where its feseable°.
</p>
Resultshttp://yam.ch/ticket/411#changeloghttp://yam.ch/ticket/427
http://yam.ch/ticket/427#427: PGP Problem when sending MailFri, 20 Sep 2013 18:57:13 GMTtrekman<p>
Description:
Tried PGP with YAM on A4000T / OS3.9 / 68060 / YAM2.8p1
After editing a mail and choosing sign/encrypt I receive the message (when trying to send) : Error trying to add the file "RamDisk:T/YAMtxxxx.asc"
The file definetly doesnt exist in ram:t so the encrypted part cannot be sent. The mail is send without it.
</p>
<p>
On my MorphOS pc it goes to high <acronym title="Central Processing Unit">CPU</acronym> Usage and freezes.
</p>
Resultshttp://yam.ch/ticket/427#changeloghttp://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/465
http://yam.ch/ticket/465#465: Switch image file handling to guigfx.libraryWed, 27 Nov 2013 08:48:19 GMTtboeckel<h2 id="Problem">Problem</h2>
<p>
Currently YAM has to do all the ugly image handling itself. In general this is beyond the scope of an EMail application. Furthermore the datatypes system is not that system independent as it ought to be, because AmigaOS3 development stopped at one time in history and the datatypes system of the other 3 systems (AmigaOS4, MorphOS, AROS) cannot be treated as equal in all cases.
</p>
<h2 id="Enhancementrecommendation">Enhancement recommendation</h2>
<p>
guigfx.library offers a standardized interface for loading, remapping and displaying images. Although guigfx.library is still based on the datatypes system it offloads all that annoying stuff from YAM.
</p>
<p>
Currently there exists a branch in YAM's svn repository (<a class="source" href="http://yam.ch/browser/branches/guigfx">source:/branches/guigfx</a>) which already uses guigfx.library as a proof of concept. Unfortunately guigfx.library is yet missing some important features like correct handling of alpha channels. This needs to be implemented first before it can be used as a 100% replacement of the current image handling.
</p>
<p>
Please note that the sources of guigfx and its sub library (render.library) can be found here:
<a class="ext-link" href="http://users.neoscientists.org/%7ebifat/binarydistillery/"><span class="icon">​</span>http://users.neoscientists.org/%7ebifat/binarydistillery/</a>
</p>
Resultshttp://yam.ch/ticket/465#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/566
http://yam.ch/ticket/566#566: Add option to "GetMail" one account after anotherSat, 31 May 2014 06:42:44 GMTrhosigma@…<h2 id="Problem">Problem</h2>
<p>
Currently I've 8 email accounts to check for new mail, when I click the "GetMail" button then YAM does try to connect to all 8 accounts immediately. Well, it's no problem with a usual broadband internet connection, but if the connection is weak (eg. using a surfstick with only an EDGE network available) then most of the accounts will return a connection error, as the internet line is simply not fast enough to handle all connections in time. The only way in this case to go is to get mail from every single account by using the respective menu entries.
</p>
<h2 id="Enhancementrecommendation">Enhancement recommendation</h2>
<ul><li>The least thing would be an option in the config to tell YAM it shall connect/transfer/disconnect to every single account in the TCP/<acronym title="Internet Protocol">IP</acronym> list one after another, rather than trying to get mail from all accounts in the same time. This option could even just be placed in the [ADVANCED] section of the ".config" file.
</li><li>To make it more fancy, it could be placed as a global checkmark option on the TCP/<acronym title="Internet Protocol">IP</acronym> -&gt; Receive Mail page in the configuration dialog.
</li><li>Best solution <acronym title="In my humble opinion...">IMHO</acronym>, simply implement it as Shift-Click option on the "GetMail" button. In this case a regular click on the button would invoke the regular mail transfer as it is right now, hence connecting to all accounts a once. If I otherwise know I've a weak internet line, then I simply click the button while holding the shift key pressed, which would then invoke the mail transfer one after one account.
</li></ul><p>
So finally this is just another option to raise the comfort level of YAM, as it is already possible to get single accounts manually. It simply would be more convenient, if this could be automated and be as easy as setting a checkmark or pressing the shift key <img src="/chrome/emoticons/smile.png" alt=":)" class="emoticon" width="18" height="18" style="vertical-align: middle" />
</p>
Resultshttp://yam.ch/ticket/566#changeloghttp://yam.ch/ticket/567
http://yam.ch/ticket/567#567: Implement an account setup wizardMon, 02 Jun 2014 06:48:49 GMTtboeckel<h2 id="Phenomenon">Phenomenon</h2>
<p>
It has been mentioned quite often that setting up a new account in YAM is too complicated due to its amount of adjustable options.
</p>
<h2 id="Backgroundanalysis">Background analysis</h2>
<p>
Mail clients on other systems offer a setup wizard where you just have to enter your name, email address and password and the mail client will obtain all the other settings (i.e. <acronym title="Post Office Protocol">POP3</acronym> and <acronym title="Simple Mail Transfer Protocol">SMTP</acronym> server name, port number, security settings, etc) automatically so that the (possibly unexperienced) user has to care about as less stuff as possible.
</p>
<h2 id="Implementationrecommendation">Implementation recommendation</h2>
<p>
Implement a setup wizard similar to the one of Thunderbird. The "beginners" mode just requires the basic things like name, address and password. A possible "advanced" mode then offers editing some more details like server address, port number, etc just like the normal config window does.
</p>
Resultshttp://yam.ch/ticket/567#changeloghttp://yam.ch/ticket/570
http://yam.ch/ticket/570#570: GUI improvement (Configuration window)Tue, 01 Jul 2014 12:39:53 GMTstellan<p>
I noticed some incontinence in Configuration <acronym title="Graphical User Interface">GUI</acronym>. The following could be improved:
</p>
<ul><li>TCP/<acronym title="Internet Protocol">IP</acronym>
</li><li>Look &amp; Feel
</li></ul><p>
For "TCP/<acronym title="Internet Protocol">IP</acronym>" I would sparate the "Server List" into its own group like it is done in "Identities". Advantage is that "Server List is always visible if the "Configuration" window is small and you are scroll the "Server Settings". Further, it is easier to edit several "Server List" entries. You have to click less.
</p>
<p>
For "Look &amp; Feel" it is the same with the "Theme" list while scrolling. I don`t know if there is a good solution to improve the current separation. Maybe it is better to separate "Look &amp; Feel" into "Themes" and "Main window"? So you can select them direct from the config list on the left. At the moment I feel like "Main window" is hidden and not good to find.
</p>
<p>
This are the good examples how it <acronym title="In my humble opinion...">IMHO</acronym> should be:
</p>
<ul><li>Filter
</li><li>Identities
</li></ul>Resultshttp://yam.ch/ticket/570#changeloghttp://yam.ch/ticket/583
http://yam.ch/ticket/583#583: IMAP 'download' supportThu, 18 Sep 2014 22:22:59 GMTdamato<h2 id="Phenomenon">Phenomenon</h2>
<p>
Since the <acronym title="Internet Message Access Protocol">IMAP</acronym> protocol is a lot more complex than the <acronym title="Post Office Protocol">POP3</acronym> protocol, it is also a lot more complicated to implement full <acronym title="Internet Message Access Protocol">IMAP</acronym> synchronization support in short time. To be able to provide some first basic <acronym title="Internet Message Access Protocol">IMAP</acronym> support to users a stripped down <acronym title="Internet Message Access Protocol">IMAP</acronym> support should be implemented (so-called '<acronym title="Internet Message Access Protocol">IMAP</acronym> download') which should work essentially the same like the <acronym title="Post Office Protocol">POP3</acronym> protocl. That means it should only download emails and provide functionality like simple <acronym title="Post Office Protocol">POP3</acronym> download support.
</p>
<h2 id="Backgroundanalysis">Background analysis</h2>
<p>
For this to be implemented, the <acronym title="Internet Message Access Protocol">IMAP</acronym> protocol needs to be analyzed so that only a few commands are used to list new waiting emails, to extract UIDL identifiers and to download new emails. All other functionality such as synchronizing the read status, etc. should be kept for the upcoming full <acronym title="Internet Message Access Protocol">IMAP</acronym> support in YAM 3.0+.
</p>
<h2 id="Implementationrecommendation">Implementation recommendation</h2>
<p>
When implementing this '<acronym title="Internet Message Access Protocol">IMAP</acronym> download' support one should make sure that the future src/tcp/imap.c should already be prepared to provide full synchronization in future. That means, care should be taken not to implement such download support to basic but keep in mind to develop functions and functionality with synchronization support in mind. Furthermore, this functionality should always be advertised as "<acronym title="Internet Message Access Protocol">IMAP</acronym> download" support and care needs to be taken to distinguish between full <acronym title="Internet Message Access Protocol">IMAP</acronym> support (coming with YAM 3.0) and with such a basic "<acronym title="Internet Message Access Protocol">IMAP</acronym> download" support.
</p>
Resultshttp://yam.ch/ticket/583#changelog