<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/mailsync/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/mailsync/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 29 Feb 2024 15:29:30 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/mailsync/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>mailsync -D corrupts IMAP folders that contain only subfolders (no messages) </title><link>https://sourceforge.net/p/mailsync/bugs/29/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;&lt;strong&gt;mailsync -D&lt;/strong&gt; works as expected on folders that contain no subfolders. However, if folder 'foo' contains subfolders but no messages on stores A and B &lt;strong&gt;and if A is an IMAP store&lt;/strong&gt;, then mailsync -D will attempt at deleting 'foo' on A resulting in a corrupted mailbox. For example, if the state of the stores is&lt;/p&gt;
&lt;p&gt;A                                   B&lt;br/&gt;
  + foo                             + foo&lt;br/&gt;
     + f1                                 + f1&lt;br/&gt;
     + f2                                  + f2&lt;br/&gt;
         - m1                                 - m1&lt;/p&gt;
&lt;p&gt;calling mailsync -D will result in&lt;/p&gt;
&lt;p&gt;A                                   B&lt;br/&gt;
  + foo                             + foo&lt;br/&gt;
     + f2                                  + f2&lt;br/&gt;
         - m1                                 - m1&lt;/p&gt;
&lt;p&gt;as one would expect &lt;strong&gt;and in a corrupted 'foo' on A if A is an IMAP store&lt;/strong&gt;. The fact that 'foo' is corrupted is indicated differently in different mail clients. In Apple's Mail under iOS, the name of the folder gets grayed out. In Thunderbird the corrupted folder is shown in italics. In both cases it is still possible to open 'foo' and add messages to its subfolder. But it is no longer possible to add messages to 'foo' itself (on A if A is an IMAP store). Depending on the mail client, removing 'foo' (on A if A is an IMAP folder) yields an error.&lt;/p&gt;
&lt;p&gt;The solution should be to distinguish between "empty" folders that contain subfolders and empty folders that do not contain subfolders and avoid attempting at deleting "empty" folders that contain subfolders.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nicola Botta</dc:creator><pubDate>Thu, 29 Feb 2024 15:29:30 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net064c85e0e76b35d0b31e8a34102898e2d3bb93ae</guid></item><item><title>#15 compile error on mac os x</title><link>https://sourceforge.net/p/mailsync/bugs/15/?limit=25#8946</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Group&lt;/strong&gt;:  --&amp;gt; &lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tomas Pospisek</dc:creator><pubDate>Tue, 10 Nov 2020 18:04:50 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net5576f0e9ed2a7e83d74b32ac1dcd8d5306a7613b</guid></item><item><title>#20 "The configuration doesn't contain a store named ..." error message can be misleading</title><link>https://sourceforge.net/p/mailsync/bugs/20/?limit=25#077b</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;summary&lt;/strong&gt;: Bad error report --&amp;gt; "The configuration doesn't contain a store named ..." error message can be misleading&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Group&lt;/strong&gt;:  --&amp;gt; &lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tomas Pospisek</dc:creator><pubDate>Tue, 10 Nov 2020 18:02:53 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netdd4569b86c6758f0c2283c55ad4cfe00a099ecc2</guid></item><item><title>#13 configure does not work on Mailsync 5.1.0</title><link>https://sourceforge.net/p/mailsync/bugs/13/?limit=25#20da</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; wont-fix&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Group&lt;/strong&gt;:  --&amp;gt; &lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tomas Pospisek</dc:creator><pubDate>Tue, 10 Nov 2020 18:00:28 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net664ad45b463ac06b92310cb58a7146577e4832fc</guid></item><item><title>mails are being duplicated with md5 due to "Date: " mangling</title><link>https://sourceforge.net/p/mailsync/bugs/28/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When transferring a message to a mbox, mailsync will apparently fix up the "Date: " header to it's own canonical format.&lt;/p&gt;
&lt;p&gt;That implies, when making a md5 hash, that at this point includes the "Date: " header, the md5 sums of a mail saved on lets say an IMAP server and the local inbox will differ.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tomas Pospisek</dc:creator><pubDate>Sat, 26 Jan 2013 12:02:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.neta0bb6cd50f86627cec3bf87f41adc8750458caf3</guid></item><item><title>segfault when migrating from -t msgid to -t md5</title><link>https://sourceforge.net/p/mailsync/bugs/27/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When having a .mailsync_state file with msgid's and running mailsync with -t md5, mailsync would segfault&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tomas Pospisek</dc:creator><pubDate>Sat, 26 Jan 2013 11:51:56 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net16cbc32a788aaa04a9678da76bae47bc9692fd7b</guid></item><item><title>Very slow on large mailboxes</title><link>https://sourceforge.net/p/mailsync/bugs/25/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I have a mailbox containing tens of thousands of messages.  It takes an hour or more to sync, which is just way too long, since I want to repeat this process every hour or so.  I profiled it briefly and it seemed to be spending most of its time in c-client parsing imap messages.  Other software in this domain has ways of doing less work, though I'd rather use mailsync if it could be fast enough, for a variety of reasons.  I can imagine some simple approaches to incrementalism, but I wouldn't want to attempt any of them without guidance.  It seems as though the mailing list has been closed down?  How/where would this get discussed?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Abrahams</dc:creator><pubDate>Fri, 06 Jul 2012 15:47:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net9891b715d1722de8dbfbf8ee63d3583d3b0ecfed</guid></item><item><title>Very slow on large mailboxes</title><link>https://sourceforge.net/p/mailsync/bugs/26/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I have a mailbox containing tens of thousands of messages.  It takes an hour or more to sync, which is just way too long, since I want to repeat this process every hour or so.  I profiled it briefly and it seemed to be spending most of its time in c-client parsing imap messages.  Other software in this domain has ways of doing less work, though I'd rather use mailsync if it could be fast enough, for a variety of reasons.  I can imagine some simple approaches to incrementalism, but I wouldn't want to attempt any of them without guidance.  It seems as though the mailing list has been closed down?  How/where would this get discussed?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Abrahams</dc:creator><pubDate>Fri, 06 Jul 2012 15:47:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netc461a3fe93d86e0e7cbf8e7cee9da8cc91b111dc</guid></item><item><title>Suspicious message-ids</title><link>https://sourceforge.net/p/mailsync/bugs/24/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;See attached grep output from log file&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Abrahams</dc:creator><pubDate>Fri, 06 Jul 2012 15:33:50 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7e4c1309209dbce255a2b4c340c4781a711346bb</guid></item><item><title>[Patch] deal with a new kind of brain-damaged message-id</title><link>https://sourceforge.net/p/mailsync/bugs/23/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Square brackets are sometimes missing around IP addresses&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Abrahams</dc:creator><pubDate>Fri, 06 Jul 2012 15:28:38 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netfbccaaba9a38902c16ff8377eb5ceebe2609a0b8</guid></item></channel></rss>