Menu
▾
▴
archivemail-devel — Discussions about archivemail development
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(13) |
Nov
(11) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(7) |
Aug
(1) |
Sep
(1) |
Oct
(3) |
Nov
(22) |
Dec
(3) |
| 2008 |
Jan
(8) |
Feb
|
Mar
(5) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
(11) |
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
(6) |
Nov
(1) |
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(12) |
Sep
(5) |
Oct
(6) |
Nov
(1) |
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
(2) |
Jul
(10) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
(2) |
Aug
(2) |
Sep
(1) |
Oct
(10) |
Nov
(4) |
Dec
|
|
From: SourceForge.net <no...@so...> - 2007-11-02 18:10:55
|
Patches item #1764851, was opened at 2007-07-31 21:24 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764851&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Nikolaus Schulz (nikosch) Summary: Add Keep support Initial Comment: Hi, recently I added the option --keep, which would archive mail, yet not delete the mail from the source mailbox. See attached patch. Thanks, Christian ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-02 19:10 Message: Logged In: YES user_id=1594781 Originator: NO This is now fixed in subversion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764851&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-02 18:08:01
|
Feature Requests item #981865, was opened at 2004-06-29 12:38 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456913&aid=981865&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Priority: 5 Private: No Submitted By: Nowicki Christophe (cscmeu) >Assigned to: Nikolaus Schulz (nikosch) Summary: small feature request : keep mail on the IMAP server Initial Comment: Hi all, I try to archive mail on my imap server. I've a lots of mailing lists on my IMAP server. When I try to archive them with archivemail I do like that : $archivemail -d 1 -v imap://cscm:passwod@server/INBOX.debian.users archivemail save all mails in the INBOX.debian.users_archive.gz file. But archivemail delete mails on the server and now INBOX.debian.users folders is empty :( I would like to have an -k, --keep options. To keep mails on the IMAP server. I would be very useful for me and for many people I think. Thanks a lot ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-02 19:08 Message: Logged In: YES user_id=1594781 Originator: NO archivemail 0.7.1 will include the --copy option which does what you want. I've just committed the changes to the subversion repo. Nikolaus ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-02-07 22:37 Message: Logged In: NO Thx! That's what i'm looking for :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456913&aid=981865&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-02 15:44:12
|
Bugs item #1007172, was opened at 2004-08-11 12:52 Message generated for change (Settings changed) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1007172&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Nikolaus Schulz (nikosch) Summary: Could not delete message from a "Sent"-File Initial Comment: Hi, I installed archivemail and it work fine for a lot of Files in an mbox-Format for imap. But When I do a archivemail --delete --days=7 /home/user/Sent it says: 0 of 1 deleted. And nothing happens to this file. But there are about 500 Mails in it and some are older than 7 Days. The System is a FreeBSD with Postfix and the Wash. University imapd. The Client is Mozilla 1.5. The "Sent"-Box is readable with Mozilla without any problems. But obviously archivemail is not able to separate the 500 mails. It thinks there is only one mail in it. Why? Thank you for tips, Bernd (mu...@eu...) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1007172&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-01 12:57:03
|
Patches item #1764846, was opened at 2007-07-31 21:19 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764846&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Nikolaus Schulz (nikosch) >Summary: Option to archive all available mail Initial Comment: Hi, thanks for working on archivemail. I think an option --archive-all would be useful. Attached is a patch, that would add that option and archive all available mails. ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-01 13:57 Message: Logged In: YES user_id=1594781 Originator: NO archivemail 0.7.1 will accept --days=0. Add --include-flagged, and you get the same effect. Still, I think a shortcut like --archive-all can be handy. The patch is incomplete, however, it only covers IMAP. Nikolaus ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764846&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-10-24 02:35:26
|
Bugs item #1783369, was opened at 2007-08-28 16:12 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1783369&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Elan Ruusamäe (ahmake) >Assigned to: Nikolaus Schulz (nikosch) Summary: archivemail fails to see all messages Initial Comment: # archivemail -n Maildir/.Trash Maildir/.Trash: I would have archived 10 of 92 message(s) (55.0kB of 1.7MB) in 0.3 seconds # find Maildir/.Trash/{cur,new} -type f | wc -l 44777 # archivemail --version archivemail v0.7.0 Copyright (C) 2002 Paul Rodger <pa...@pa...> (C) 2006 Peter Poeml <po...@su...>, (C) 2006 Nikolaus Schulz <mic...@we...> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. using -v doesn't reveal any much more information why it happens so i'm not pasting it here. please ask for more information as i'm not feeling comfortable of sharing my Trash folder contents for testing :) ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-10-24 04:35 Message: Logged In: YES user_id=1594781 Originator: NO Thanks for reporting this, and even more for tracking it down and for your patch. I wonder how such invalid sprint into existance, but anyway, I can find three bug reports which seem to be about this issue, so it affects people in real life. :-) Your patch looks good to me, I've only slightly modified it. The fix is now in subversion. Cheers, Nikolaus ---------------------------------------------------------------------- Comment By: Elan Ruusamäe (ahmake) Date: 2007-09-18 12:51 Message: Logged In: YES user_id=289546 Originator: YES looks like the loop was ended because this code (from mailbox.py) returned False when message contained just \n (has it's header and body). fn = self.boxes.pop() fp = open(fn) return self.factory(fp) http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/SOURCES/archivemail-invalid-message.patch File Added: archivemail-invalid-message.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1783369&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-10-23 23:56:02
|
Bugs item #1640878, was opened at 2007-01-21 18:06 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1640878&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 7 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nikolaus Schulz (nikosch) Summary: imap mailbox with username containing "@" character Initial Comment: Hi, imap mailbox specifications that contain the "@" character in the username field causes the spec parsing to fail. This is due to the changes made in version 0.7.0 in order to get more flexibility in the password handling of imap mailboxes. In versions before 0.7.0, the username substring was separated from the imap server substring by searching for an ":" in the specification. In version 0.7.0 this was replaced by the search for the "@" character, which causes the parser bug. I don't know much about python, but performing a reverse split instead of a 'normal' split in line 1308 seems to work: "imap_str.split('@', 1)" -> "imap_str.rsplit('@', 1)" I believe this to be stable because the last "@" character always specifies the separator between user name and server as long as the imap server configuration does not make use of this character as the folder separator... Best regards, Markus Pister we...@ma... ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-10-24 01:55 Message: Logged In: YES user_id=1594781 Originator: NO This is finally fixed in Subversion. There's a new IMAP URL parser which understands quoted usernames and passwords. Was surprisingly difficult to do it right, but I think I managed it. :-) Cheers, Nikolaus ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2007-01-22 13:05 Message: Logged In: YES user_id=1594781 Originator: NO Thanks for filing this bug. I'm attaching a patch which allows to backslash-escape '@' characters in IMAP usernames (and which has already been posted to the archivemail-user mailing list[1]). Note that your suggestion to split at the last '@' in the URL isn't entirely bullet-proof, since the '@' character is valid in mailbox names. I think there are not many people using archivemail with IMAP mailboxes, but this particular issue has been reported several times now, so I'm bumping it's priority a bit... Cheers, Nikolaus [1] http://sourceforge.net/mailarchive/forum.php?thread_id=31258509&forum_id=8450 File Added: archivemail-atnames-fix.diff ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1640878&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-10-22 22:14:48
|
Bugs item #1670422, was opened at 2007-02-28 01:00 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1670422&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed >Priority: 8 Private: No Submitted By: Ali Polatel (hawking2) >Assigned to: Nikolaus Schulz (nikosch) >Summary: crashes with maildir and python-2.5 Initial Comment: archivemail have problems running with python-2.5 Here is the traceback: hawking@mars:~ archivemail -d 5 .maildir/local Traceback (most recent call last): File "/usr/bin/archivemail", line 1469, in <module> main() File "/usr/bin/archivemail", line 687, in main archive(mailbox_path) File "/usr/bin/archivemail", line 1130, in archive _archive_dir(mailbox_name, final_archive_name, "maildir") File "/usr/bin/archivemail", line 1270, in _archive_dir add_status_headers(msg) File "/usr/bin/archivemail", line 809, in add_status_headers match = re.search(":2,(.+)$", message.fp.name) AttributeError: _ProxyFile instance has no attribute 'name' .maildir/local is a Maildir and message is a rfc822.Message instance. In python2.4 message.fp.name gives the path of the file where this message is stored. In python2.5 this doesn't exist but same info is avaliable from 'message.fp._file.name' I've written a patch for archivemail-0.7.0 to check for python version and decide whether to use message.fp.name or message.fp._file.name and the tool seems to work fine. ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-10-23 00:14 Message: Logged In: YES user_id=1594781 Originator: NO Thanks for pointing that out, that's indeed a rather major problem. A fix is now in Subversion. ---------------------------------------------------------------------- Comment By: Ali Polatel (hawking2) Date: 2007-05-10 11:38 Message: Logged In: YES user_id=1671462 Originator: YES Here is an updated patch fixing is_flagged and is_unread too File Added: archivemail-0.7.0-fpname.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1670422&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-09-18 10:51:09
|
Bugs item #1783369, was opened at 2007-08-28 17:12 Message generated for change (Comment added) made by ahmake You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1783369&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Elan Ruusamäe (ahmake) Assigned to: Nobody/Anonymous (nobody) Summary: archivemail fails to see all messages Initial Comment: # archivemail -n Maildir/.Trash Maildir/.Trash: I would have archived 10 of 92 message(s) (55.0kB of 1.7MB) in 0.3 seconds # find Maildir/.Trash/{cur,new} -type f | wc -l 44777 # archivemail --version archivemail v0.7.0 Copyright (C) 2002 Paul Rodger <pa...@pa...> (C) 2006 Peter Poeml <po...@su...>, (C) 2006 Nikolaus Schulz <mic...@we...> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. using -v doesn't reveal any much more information why it happens so i'm not pasting it here. please ask for more information as i'm not feeling comfortable of sharing my Trash folder contents for testing :) ---------------------------------------------------------------------- >Comment By: Elan Ruusamäe (ahmake) Date: 2007-09-18 13:51 Message: Logged In: YES user_id=289546 Originator: YES looks like the loop was ended because this code (from mailbox.py) returned False when message contained just \n (has it's header and body). fn = self.boxes.pop() fp = open(fn) return self.factory(fp) http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/SOURCES/archivemail-invalid-message.patch File Added: archivemail-invalid-message.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1783369&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-08-28 14:12:01
|
Bugs item #1783369, was opened at 2007-08-28 17:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1783369&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Elan Ruusamäe (ahmake) Assigned to: Nobody/Anonymous (nobody) Summary: archivemail fails to see all messages Initial Comment: # archivemail -n Maildir/.Trash Maildir/.Trash: I would have archived 10 of 92 message(s) (55.0kB of 1.7MB) in 0.3 seconds # find Maildir/.Trash/{cur,new} -type f | wc -l 44777 # archivemail --version archivemail v0.7.0 Copyright (C) 2002 Paul Rodger <pa...@pa...> (C) 2006 Peter Poeml <po...@su...>, (C) 2006 Nikolaus Schulz <mic...@we...> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. using -v doesn't reveal any much more information why it happens so i'm not pasting it here. please ask for more information as i'm not feeling comfortable of sharing my Trash folder contents for testing :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1783369&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-07-31 19:27:52
|
Patches item #1764855, was opened at 2007-07-31 12:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764855&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: look at received header Initial Comment: Hi, 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. Thanks, Christian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764855&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-07-31 19:24:11
|
Patches item #1764851, was opened at 2007-07-31 12:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764851&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Add Keep support Initial Comment: Hi, recently I added the option --keep, which would archive mail, yet not delete the mail from the source mailbox. See attached patch. Thanks, Christian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764851&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-07-31 19:21:13
|
Patches item #1764847, was opened at 2007-07-31 12:21 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764847&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Add bz2 support Initial Comment: Hi, I recently added bz2 support to archivemail. Please consider adding this patch. Thanks, Christian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764847&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-07-31 19:19:51
|
Patches item #1764846, was opened at 2007-07-31 12:19 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764846&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: archive all available mail Initial Comment: Hi, thanks for working on archivemail. I think an option --archive-all would be useful. Attached is a patch, that would add that option and archive all available mails. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764846&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-07-29 22:12:28
|
Bugs item #1762907, was opened at 2007-07-28 15:16 Message generated for change (Comment added) made by helloworld_c You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1762907&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: helloworld.c (helloworld_c) Assigned to: Nobody/Anonymous (nobody) Summary: Small bug setting gid Initial Comment: When using the verbose option on IMAP mailboxes and running under root, e.g. archivemail -v imap://user:pw@server/mb the variable 'former_id' in the following section around line 1100 stays at 'None': former_gid = None # groupid doesn't have to be '0' for root on solaris 8? if (os.getuid() == 0) and os.path.exists(mailbox_name): ... This is because mailbox_name is an IMAP mailbox and therefore the path doesn't exist. Later on, in the 'finally' section it tries to set the gid to 'None' which, of course, fails: # if we are running as root, revert the seteuid()/setegid() above if (os.getuid() == 0): vprint("changing effective groupid and userid back to root") os.setegid(former_gid) In order to catch this case I would suggest to replace the condition to: if os.getuid() == 0 and former_gid != None: Works fine here. ---------------------------------------------------------------------- >Comment By: helloworld.c (helloworld_c) Date: 2007-07-29 15:12 Message: Logged In: YES user_id=1760487 Originator: YES As I sent it I realized that the verbose option has absolutely nothing to do with it, so just using it as root with an IMAP mailbox should be enough to make it fail. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1762907&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-07-28 22:16:24
|
Bugs item #1762907, was opened at 2007-07-28 15:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1762907&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: helloworld.c (helloworld_c) Assigned to: Nobody/Anonymous (nobody) Summary: Small bug setting gid Initial Comment: When using the verbose option on IMAP mailboxes and running under root, e.g. archivemail -v imap://user:pw@server/mb the variable 'former_id' in the following section around line 1100 stays at 'None': former_gid = None # groupid doesn't have to be '0' for root on solaris 8? if (os.getuid() == 0) and os.path.exists(mailbox_name): ... This is because mailbox_name is an IMAP mailbox and therefore the path doesn't exist. Later on, in the 'finally' section it tries to set the gid to 'None' which, of course, fails: # if we are running as root, revert the seteuid()/setegid() above if (os.getuid() == 0): vprint("changing effective groupid and userid back to root") os.setegid(former_gid) In order to catch this case I would suggest to replace the condition to: if os.getuid() == 0 and former_gid != None: Works fine here. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1762907&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-07-13 17:36:15
|
Bugs item #1753702, was opened at 2007-07-13 12:36 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1753702&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Demarcus Cherish (limburgher) Assigned to: Nobody/Anonymous (nobody) Summary: crashes on zero-size mbox folder. Initial Comment: Traceback (most recent call last): File "/usr/bin/archivemail", line 6, in <module> main() File "/usr/share/archivemail/archivemail.py", line 686, in main archive(mailbox_path) File "/usr/share/archivemail/archivemail.py", line 1125, in archive new_temp_dir = tempfile.mkdtemp('archivemail') File "/usr/lib/python2.5/tempfile.py", line 320, in mkdtemp dir = gettempdir() File "/usr/lib/python2.5/tempfile.py", line 262, in gettempdir tempdir = _get_default_tempdir() File "/usr/lib/python2.5/tempfile.py", line 209, in _get_default_tempdir ("No usable temporary directory found in %s" % dirlist)) IOError: [Errno 2] No usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/root'] Happens on some empty folders. Does not happen on others. Not sure why, all the listed temp dirs exist on my systems. If I edit my wrapper script to only run archivemail against nonzero size boxes, i only get one error. Not sure who, but I have one user who's at quota. I'm the Fedora maintainer for this, so I'll submit a patch if I find a solution. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1753702&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-05-10 09:38:06
|
Bugs item #1670422, was opened at 2007-02-28 02:00 Message generated for change (Comment added) made by hawking2 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1670422&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ali Polatel (hawking2) Assigned to: Nobody/Anonymous (nobody) Summary: archivemail python-2.5 fix Initial Comment: archivemail have problems running with python-2.5 Here is the traceback: hawking@mars:~ archivemail -d 5 .maildir/local Traceback (most recent call last): File "/usr/bin/archivemail", line 1469, in <module> main() File "/usr/bin/archivemail", line 687, in main archive(mailbox_path) File "/usr/bin/archivemail", line 1130, in archive _archive_dir(mailbox_name, final_archive_name, "maildir") File "/usr/bin/archivemail", line 1270, in _archive_dir add_status_headers(msg) File "/usr/bin/archivemail", line 809, in add_status_headers match = re.search(":2,(.+)$", message.fp.name) AttributeError: _ProxyFile instance has no attribute 'name' .maildir/local is a Maildir and message is a rfc822.Message instance. In python2.4 message.fp.name gives the path of the file where this message is stored. In python2.5 this doesn't exist but same info is avaliable from 'message.fp._file.name' I've written a patch for archivemail-0.7.0 to check for python version and decide whether to use message.fp.name or message.fp._file.name and the tool seems to work fine. ---------------------------------------------------------------------- >Comment By: Ali Polatel (hawking2) Date: 2007-05-10 12:38 Message: Logged In: YES user_id=1671462 Originator: YES Here is an updated patch fixing is_flagged and is_unread too File Added: archivemail-0.7.0-fpname.patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1670422&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-02-28 00:00:04
|
Bugs item #1670422, was opened at 2007-02-28 02:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1670422&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: hawking2 (hawking2) Assigned to: Nobody/Anonymous (nobody) Summary: archivemail python-2.5 fix Initial Comment: archivemail have problems running with python-2.5 Here is the traceback: hawking@mars:~ archivemail -d 5 .maildir/local Traceback (most recent call last): File "/usr/bin/archivemail", line 1469, in <module> main() File "/usr/bin/archivemail", line 687, in main archive(mailbox_path) File "/usr/bin/archivemail", line 1130, in archive _archive_dir(mailbox_name, final_archive_name, "maildir") File "/usr/bin/archivemail", line 1270, in _archive_dir add_status_headers(msg) File "/usr/bin/archivemail", line 809, in add_status_headers match = re.search(":2,(.+)$", message.fp.name) AttributeError: _ProxyFile instance has no attribute 'name' .maildir/local is a Maildir and message is a rfc822.Message instance. In python2.4 message.fp.name gives the path of the file where this message is stored. In python2.5 this doesn't exist but same info is avaliable from 'message.fp._file.name' I've written a patch for archivemail-0.7.0 to check for python version and decide whether to use message.fp.name or message.fp._file.name and the tool seems to work fine. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1670422&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-01-22 12:08:49
|
Bugs item #1640901, was opened at 2007-01-21 18:37 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1640901&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Duplicate >Priority: 7 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Nikolaus Schulz (nikosch) Summary: imap mailbox with username containing "@" character Initial Comment: Hi, imap mailbox specifications that contain the "@" character in the username field causes the spec parsing to fail. This is due to the changes made in version 0.7.0 in order to get more flexibility in the password handling of imap mailboxes. In versions before 0.7.0, the username substring was separated from the imap server substring by searching for an ":" in the specification. In version 0.7.0 this was replaced by the search for the "@" character, which causes the parser bug. I don't know much about python, but performing a reverse split instead of a 'normal' split in line 1308 seems to work: "imap_str.split('@', 1)" -> "imap_str.rsplit('@', 1)" I believe this to be stable because the last "@" character always specifies the separator between user name and server as long as the imap server configuration does not make use of this character as the folder separator... Best regards, Markus Pister we...@ma... ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-01-22 13:08 Message: Logged In: YES user_id=1594781 Originator: NO Closing since it's a duplicate of #1640878. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1640901&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-01-22 12:05:32
|
Bugs item #1640878, was opened at 2007-01-21 18:06 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1640878&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None >Priority: 7 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Nikolaus Schulz (nikosch) Summary: imap mailbox with username containing "@" character Initial Comment: Hi, imap mailbox specifications that contain the "@" character in the username field causes the spec parsing to fail. This is due to the changes made in version 0.7.0 in order to get more flexibility in the password handling of imap mailboxes. In versions before 0.7.0, the username substring was separated from the imap server substring by searching for an ":" in the specification. In version 0.7.0 this was replaced by the search for the "@" character, which causes the parser bug. I don't know much about python, but performing a reverse split instead of a 'normal' split in line 1308 seems to work: "imap_str.split('@', 1)" -> "imap_str.rsplit('@', 1)" I believe this to be stable because the last "@" character always specifies the separator between user name and server as long as the imap server configuration does not make use of this character as the folder separator... Best regards, Markus Pister we...@ma... ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-01-22 13:05 Message: Logged In: YES user_id=1594781 Originator: NO Thanks for filing this bug. I'm attaching a patch which allows to backslash-escape '@' characters in IMAP usernames (and which has already been posted to the archivemail-user mailing list[1]). Note that your suggestion to split at the last '@' in the URL isn't entirely bullet-proof, since the '@' character is valid in mailbox names. I think there are not many people using archivemail with IMAP mailboxes, but this particular issue has been reported several times now, so I'm bumping it's priority a bit... Cheers, Nikolaus [1] http://sourceforge.net/mailarchive/forum.php?thread_id=31258509&forum_id=8450 File Added: archivemail-atnames-fix.diff ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1640878&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-01-21 17:37:37
|
Bugs item #1640901, was opened at 2007-01-21 09:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1640901&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: imap mailbox with username containing "@" character Initial Comment: Hi, imap mailbox specifications that contain the "@" character in the username field causes the spec parsing to fail. This is due to the changes made in version 0.7.0 in order to get more flexibility in the password handling of imap mailboxes. In versions before 0.7.0, the username substring was separated from the imap server substring by searching for an ":" in the specification. In version 0.7.0 this was replaced by the search for the "@" character, which causes the parser bug. I don't know much about python, but performing a reverse split instead of a 'normal' split in line 1308 seems to work: "imap_str.split('@', 1)" -> "imap_str.rsplit('@', 1)" I believe this to be stable because the last "@" character always specifies the separator between user name and server as long as the imap server configuration does not make use of this character as the folder separator... Best regards, Markus Pister we...@ma... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1640901&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-01-21 17:06:42
|
Bugs item #1640878, was opened at 2007-01-21 09:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1640878&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: imap mailbox with username containing "@" character Initial Comment: Hi, imap mailbox specifications that contain the "@" character in the username field causes the spec parsing to fail. This is due to the changes made in version 0.7.0 in order to get more flexibility in the password handling of imap mailboxes. In versions before 0.7.0, the username substring was separated from the imap server substring by searching for an ":" in the specification. In version 0.7.0 this was replaced by the search for the "@" character, which causes the parser bug. I don't know much about python, but performing a reverse split instead of a 'normal' split in line 1308 seems to work: "imap_str.split('@', 1)" -> "imap_str.rsplit('@', 1)" I believe this to be stable because the last "@" character always specifies the separator between user name and server as long as the imap server configuration does not make use of this character as the folder separator... Best regards, Markus Pister we...@ma... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1640878&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2006-11-29 03:20:13
|
Bugs item #847555, was opened at 2003-11-22 23:08 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=847555&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all Group: None >Status: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nikolaus Schulz (nikosch) Summary: archiving courier-imap maildirs Initial Comment: I have been completely unsuccessful in archiving mailboxes in the courier-imap Maildir format. All mailboxes are in the format ".mailbox_name" (notice the leading dot). The error received is: "IOError: [Errno 13] Permission denied: 'path/to/.gz_file/that/cannot/be/created' The destination archive directory is under the user's home directory and has the permissions set to 600. I've also tried 4600 and got the same results (Set user ID). I've included my archive script. I am using version: v0.6.1 --- Matthew Hayes sou...@al... ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2006-11-28 19:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2006-11-14 13:07 Message: Logged In: YES user_id=1594781 Originator: NO I've emailed both the submitter and ah...@us... last week, but got no reply. The bug report itself looks obscure, a directory with mode 600 is even less than read-only and pretty much useless. It doesn't look like the comment refers to the same problem. Set status to pending so we get rid of this thing if no one steps up with useful information. ---------------------------------------------------------------------- Comment By: Elan Ruusamäe (ahmake) Date: 2006-02-08 14:00 Message: Logged In: YES user_id=289546 i believe this has something to do with archivemail trying to move between temp file and destination dir. try reseting those env vars: export TMPDIR="$archivedir" export TMP="$TMPDIR" it fixed archiving for me. i tried to reproduce, for bug reporting, but wasn't successful, ie my test archival succeeded, when having TMPDIR and TMP on different partition than archived dir. maybe it's has something to do with file owner, because i noticed that temp dir was created under maildir owner uid, while the temp dir was owned by root only: # la /home/vmail/archived/{,tmpZhmKDtarchivemail} -d drwxrwx--- 74 root root 1936 Feb 8 23:45 /home/vmail/archived// drwx------ 2 vmail vmail 88 Feb 8 23:45 /home/vmail/archived/tmpZhmKDtarchivemail/ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=847555&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2006-11-23 03:20:04
|
Bugs item #1240580, was opened at 2005-07-18 16:53 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1240580&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nikolaus Schulz (nikosch) Summary: IO error Initial Comment: When run Archivemail gives an IO error. Bellow is the it shows. Traceback (most recent call last): File "/usr/bin/archivemail", line 1298, in ? main() File "/usr/bin/archivemail", line 619, in main archive(mailbox_path) File "/usr/bin/archivemail", line 1036, in archive _archive_mbox(mailbox_name, final_archive_name) File "/usr/bin/archivemail", line 1097, in _archive_mbox archive = ArchiveMbox(final_archive_name) File "/usr/bin/archivemail", line 486, in __init__ self.__init_uncompressed(final_name) File "/usr/bin/archivemail", line 504, in __init_uncompressed self.mbox_file = open(temp_name, "a") IOError: [Errno 13] Permission denied: '/tmp/tmpHKmQozarchivemail/tmp6NoIlwarchive' Archivemail error: 256 (jp.baudoin, 2005-1-1) ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2006-11-22 19:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2006-11-08 00:50 Message: Logged In: YES user_id=1594781 This seems to be v0.6.1. I cannot reproduce this. Sparse information, anonymous bug reporter... Set status to pending, I guess we'll just let the bot close it if no one objects. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1240580&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2006-11-16 18:10:23
|
Patches item #925645, was opened at 2004-03-29 23:57 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=925645&group_id=49630 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Accepted Priority: 3 Private: No Submitted By: Sebastian Prause (sprause) Assigned to: Nikolaus Schulz (nikosch) Summary: make --output-dir=~/Mail/old work (use os.path.expanduser) Initial Comment: hi, the --output-dir option has a small issue: if using the long option, the shell won't expand the tilde (~) for the userdir. I've created a patch that does this (using os.path.expanduser) The patch is attached ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2006-11-16 19:10 Message: Logged In: YES user_id=1594781 Originator: NO Yes, unfortunately archivemail was not actively maintained for a long time. I'm closing this tracker since we somewhat agree about the second hunk. :-) The first one is in HEAD, thanks for submitting the patch. Nikolaus ---------------------------------------------------------------------- Comment By: Sebastian Prause (sprause) Date: 2006-11-16 17:31 Message: Logged In: YES user_id=925608 Originator: YES I don't recall why I added the last expanduser call, too long ago already, sorry :) Right now, it simply looks superfluous to me. ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2006-11-14 23:18 Message: Logged In: YES user_id=1594781 Originator: NO Hi, I'm going over the tracker items for archivemail... Thanks for your report and for the patch. Regarding the patch, I don't see what the second hunk is supposed to fix -- the mailbox names should be expanded by the shell. Mind to explain? The first hunk looks good. --- archivemail 2002-10-31 00:54:55.000000000 +0100 +++ /usr/pkg/bin/archivemail 2004-03-29 23:38:11.000000000 +0200 @@ -199,7 +199,7 @@ archive_by = "days" self.days_old_max = string.atoi(a) if o in ('-o', '--output-dir'): - self.output_dir = a + self.output_dir = os.path.expanduser(a) if o in ('-h', '-?', '--help'): print usage sys.exit(0) @@ -616,7 +616,7 @@ options.sanity_check() for mailbox_path in args: - archive(mailbox_path) + archive(os.path.expanduser(mailbox_path)) ######## errors and debug ########## ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=925645&group_id=49630 |
1 message has been excluded from this view by a project administrator.
