<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to patches</title><link>https://sourceforge.net/p/archivemail/patches/</link><description>Recent changes to patches</description><atom:link href="https://sourceforge.net/p/archivemail/patches/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 11 Sep 2013 02:59:52 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/archivemail/patches/feed.rss" rel="self" type="application/rss+xml"/><item><title>Patch to hide passwords from the folder display</title><link>https://sourceforge.net/p/archivemail/patches/28/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I noticed that when a password is specified from the command line, it shows up in the output of the folder name. This is a patch that fixes that behavior.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">William Reading</dc:creator><pubDate>Wed, 11 Sep 2013 02:59:52 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netf581298e6cc564247739020cc7f832e254ab8cd1</guid></item><item><title>GSSAPI support</title><link>https://sourceforge.net/p/archivemail/patches/27/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I merged in some code from the offlineimap project to enable gssapi support.  It will attempt this first and then revert to other authentications methods if it fails.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dennis Gregorovic</dc:creator><pubDate>Fri, 19 Nov 2010 18:53:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net958a1f670af1468c56b2b95f62d7b7f7e9d4a4b0</guid></item><item><title>Patch: Root Disable Seteuid Option</title><link>https://sourceforge.net/p/archivemail/patches/26/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I needed to disable the root seteuid functionality so I wrote the attached patch.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kevin A. McGrail</dc:creator><pubDate>Tue, 28 Apr 2009 19:39:16 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net22c59176e71ff0bf1f8c857de1d1f3fd634d2334</guid></item><item><title>archivemail needs to preserve IMAP dummy message</title><link>https://sourceforge.net/p/archivemail/patches/25/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;archivemail will happily delete the dummy message that IMAP servers place in mbox files to keep track of the next UID.  This isn't the end of the world, but it is mildly unpleasant.&lt;/p&gt;
&lt;p&gt;This simple patch will preserve this message.  (A more rigorous implemention might ensure that this is the first message in the file.)&lt;/p&gt;
&lt;p&gt;Enjoy,&lt;/p&gt;
&lt;p&gt;--tlhackque at nospam.yahoo.com&lt;/p&gt;
&lt;p&gt;--- /usr/share/archivemail/archivemail.py~      2007-06-14 11:57:39.000000000 -0400&lt;br /&gt;
+++ /usr/share/archivemail/archivemail.py       2008-10-30 18:23:16.000000000 -0400&lt;br /&gt;
@@ -981,20 +981,25 @@&lt;br /&gt;
# I could probably do this in one if statement, but then I wouldn't&lt;br /&gt;
# understand it.&lt;br /&gt;
if not old:&lt;br /&gt;
return 0&lt;br /&gt;
if not options.include_flagged and is_flagged(message):&lt;br /&gt;
return 0&lt;br /&gt;
if options.min_size and is_smaller(message, options.min_size):&lt;br /&gt;
return 0&lt;br /&gt;
if options.preserve_unread and is_unread(message):&lt;br /&gt;
return 0&lt;br /&gt;
+    """TL: Do not remove IMAP header message"""&lt;br /&gt;
+    imaphdr = message.get('X-IMAP')&lt;br /&gt;
+    if imaphdr :&lt;br /&gt;
+        vprint("Message is an IMAP mailbox header ('%s')" % imaphdr)&lt;br /&gt;
+        return 0&lt;br /&gt;
return 1&lt;/p&gt;
&lt;p&gt;def is_older_than_time(time_message, max_time):&lt;br /&gt;
"""Return true if a message is older than the specified time,&lt;br /&gt;
false otherwise.&lt;/p&gt;
&lt;p&gt;Arguments:&lt;br /&gt;
time_message -- the delivery date of the message measured in seconds&lt;br /&gt;
since the epoch&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">tlhackque</dc:creator><pubDate>Thu, 30 Oct 2008 23:24:05 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net1ba6b4dc4b7c0ede391189d3235c3e727a29f5f6</guid></item><item><title>recursively archive all mails from an imap server</title><link>https://sourceforge.net/p/archivemail/patches/24/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br /&gt;
I thought, it would be nice, if archivemail could automatically archive messages from all folders in an imap server. This could for example be used for migrating all mails from one imap-server to another server.&lt;/p&gt;
&lt;p&gt;Attached is my first try to achieve this. I am not sure, how stable it is, especially the naming of the final archive could probably be improved and I am not sure how well this works with other imap servers beside cyrus, with which I've tested it.&lt;/p&gt;
&lt;p&gt;Greetings,&lt;br /&gt;
C.Brabandt&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Christian</dc:creator><pubDate>Tue, 18 Mar 2008 23:36:40 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net2c70ab98d7bfdea15ad6788dd14e48a3b8b6d76e</guid></item><item><title>empty Maildir fix for Python 2.5</title><link>https://sourceforge.net/p/archivemail/patches/23/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;when archiving an empty maildir an assertion is generated&lt;/p&gt;
&lt;p&gt;this patch fixes that&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Aidant</dc:creator><pubDate>Thu, 24 Jan 2008 14:44:14 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net0fedf7c73fad230f2752e5a1fba333c6a89d9a0d</guid></item><item><title>Allow writing to world-writable directory with sticky bit</title><link>https://sourceforge.net/p/archivemail/patches/22/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Current behavior:&lt;br /&gt;
If the destination directory is world-writable, halt.&lt;/p&gt;
&lt;p&gt;New behavior:&lt;br /&gt;
If the destination directory is world-writable, then proceed only if the directory's sticky bit is set.&lt;/p&gt;
&lt;p&gt;Rationale:&lt;br /&gt;
If the destination directory is world-writable with the sticky bit set, then only the user who owns the archived file (or the owner of the directory) can delete it. From the user's perspective, it's equivalent to the directory not being world-writable, so there's no need for concern.&lt;/p&gt;
&lt;p&gt;I'm including an svn diff of the quick change. If you'd like this another way, just let me know.&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;Tim&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim O'Donnell</dc:creator><pubDate>Fri, 18 Jan 2008 16:58:11 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net0b0e8e67c0f21db743f9356028e4480bc97e6d9c</guid></item><item><title>Archive DSpam identified mail.</title><link>https://sourceforge.net/p/archivemail/patches/21/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Checks the message headers for the DSPAM-Confidence tag, and acts on the confidence values.&lt;/p&gt;
&lt;p&gt;The quarantined files in /var/dspam/mail/dspam.mbox tend to grow large, and generally messages which are tagged at 58% and above are true spam.&lt;/p&gt;
&lt;p&gt;These files can be deleted.&lt;/p&gt;
&lt;p&gt;So the modifications to archive mails in this patch does these things:&lt;/p&gt;
&lt;p&gt;1) New option: spam_confidence&lt;br /&gt;
2) Command line flag: --spam=NUM&lt;br /&gt;
3) Sets minimum date &amp;gt;= 0 (instead of 1), so I can delete messages within the day&lt;br /&gt;
4) in should_archive, does the check between the message spam confidence and the option spam confidence threshold&lt;/p&gt;
&lt;p&gt;I can then cronjob archivemail to clear off all the true spams, and this works well.&lt;/p&gt;
&lt;p&gt;BTW, thanks for this utility.&lt;/p&gt;
&lt;p&gt;yk.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yong Yoon Kit</dc:creator><pubDate>Tue, 18 Dec 2007 11:37:39 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net3e270a2cde25bb139c9db313d0cae51506290259</guid></item><item><title>detect imap folder-seperator</title><link>https://sourceforge.net/p/archivemail/patches/20/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br /&gt;
I just looked around the debian BTS and saw bug 368112.&lt;br /&gt;
Attached is a patch, that will make archivemail trying to use a different folder-separator, if selecting the folder fails.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Christian</dc:creator><pubDate>Tue, 06 Nov 2007 11:30:41 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netd9b0f6a3f8507646e21878110a58eac4d5ccac80</guid></item><item><title>look at received header </title><link>https://sourceforge.net/p/archivemail/patches/19/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br /&gt;
and another patch, that will make archivemail aware of the Received Header. using the --received-date switch will make archivemail look at the first received header in the message to decide, whether to archive the mail or not.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br /&gt;
Christian&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 31 Jul 2007 19:27:54 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netc07ce18e4b85811ac2e3eec62688bbb83f82bd9c</guid></item></channel></rss>