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...> - 2006-11-16 16:31:51
|
Patches item #925645, was opened at 2004-03-29 23:57 Message generated for change (Comment added) made by sprause 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: Open 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: 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 |
|
From: SourceForge.net <no...@so...> - 2006-11-14 22:18:39
|
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: Pending >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-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 |
|
From: SourceForge.net <no...@so...> - 2006-11-14 21:07:03
|
Bugs item #847555, was opened at 2003-11-23 08:08 Message generated for change (Comment added) made by nikosch 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: Pending >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: Nikolaus Schulz (nikosch) Date: 2006-11-14 22: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 23: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-14 20:55:22
|
Bugs item #829230, was opened at 2003-10-23 23:10 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=829230&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: Out of Date Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Archives zero messages from MH mailbox Initial Comment: I use a perl-script to delete old mails with archivemail. The mailer is sylpheed (MH mailbox) The old mails are NOT deleted. No error occures from archivemail: the script: #!/usr/bin/perl -w # Posteingang von Sylpheed nach 180 Tagen len system "archivemail -u -d180 --delete ~/mail/sylpheed_imap/inbox/"; #print "Posteingang bereinigt!\n"; # Gesendete mails nach einem Jahr len system "archivemail -u -d365 --delete ~/mail/sylpheed_imap/sent/"; #print "Gesendete Mails bereinigt!\n"; .... and so on .... the output: /home/konrad/mail/sylpheed_imap/inbox: deleted 0 of 571 message(s) in 1.8 seconds /home/konrad/mail/sylpheed_imap/sent: deleted 0 of 490 message(s) in 0.9 seconds in the mailbox are mails from the last year, perhaps with header: From: Hans-Gert Schloegl <sh...@gm...> To: kuno Reply-To: sh...@gm... Subject: fast online update for suse Date: Tue, 22 Oct 2002 11:09:36 +0200 User-Agent: Mutt/1.4i Please, what can I do to delete the old mails really???? ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2006-11-14 21:55 Message: Logged In: YES user_id=1594781 Originator: NO My MH test boxes work just fine. I've emailed the submitter, he has meanwhile switched to Evolution and is no longer interested in this bug report. I'm closing this bug, since there's no way to track it down. ---------------------------------------------------------------------- Comment By: Heiss Konrad (konrad03) Date: 2003-12-15 01:05 Message: Logged In: YES user_id=898337 hello "knitterb" Sorry for the long delay, but I had other problems ...except archivemail in the meantime ;-) Thanks for help! Please answer to ko...@ai... and you get a guest account at my server to look for needed files. You can connect to my Server: aio4u.com user: gast when I get your e-mail, you get the password and I open the gast-account. in the directory /home/konrad/mail/sylpheed_imap/HK10- Sicherheit/ you can do some tests (with sudo). Many Thanks for help, Konrad ---------------------------------------------------------------------- Comment By: Brandon Knitter (knitterb) Date: 2003-10-31 07:51 Message: Logged In: YES user_id=11101 I just took this project over. I'll have to look into it. I'll need a couple of example MH files though, as I don't have anything for testing right now. Do you have any test files which can be used? Please let me know if there is confidential information in there and I won't keep it around. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-10-30 17:12 Message: Logged In: NO konrad@hk10:~$ archivemail -V archivemail v0.6.1 Copyright (C) 2002 Paul Rodger <pa...@pa...> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. konrad@hk10:~$ Konrad Heiss ko...@ai... ---------------------------------------------------------------------- Comment By: Brandon Knitter (knitterb) Date: 2003-10-29 03:53 Message: Logged In: YES user_id=11101 What version of archive mail are you using? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-10-23 23:11 Message: Logged In: NO Heiss Konrad ko...@ai... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=829230&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2006-11-08 12:23:14
|
Bugs item #1491229, was opened at 2006-05-18 23:31 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1491229&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: archivemail dies w/ MemoryError Initial Comment: Archivemail dies with a "MemoryError" on a certain mbox. I can provide more debugging information if you let me know what to give. The archivemail process itself doesn't seem to be sucking down much memory during this, so I don't think it's a problem with the system running out of memory / swap. This is on a 345M folder, which may contain some big messages. archivemail v0.6.1 $ archivemail -v -D "30 apr 2006" /home/xxxxx/mymaildir/PG_Reports message is 1812.20 days older than the specified date message is not flagged important decision: archive message saving message to file '/tmp/@27975.0archivemail/@27975.1archive.gz' Traceback (most recent call last): File "/home/william/bin/archivemail", line 1298, in ? main() File "/home/william/bin/archivemail", line 619, in main archive(mailbox_path) File "/home/william/bin/archivemail", line 1036, in archive _archive_mbox(mailbox_name, final_archive_name) File "/home/william/bin/archivemail", line 1105, in _archive_mbox msg = original.next() File "/usr/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/usr/lib/python2.2/rfc822.py", line 106, in __init__ self.readheaders() File "/usr/lib/python2.2/rfc822.py", line 153, in readheaders line = self.fp.readline() File "/usr/lib/python2.2/mailbox.py", line 63, in readline data = self.fp.readline(length) MemoryError ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2006-11-08 13:23 Message: Logged In: YES user_id=1594781 I cannot reproduce this. My box has 256MB memory. I've disabled swap and hammered archivemail with a 370MB mbox containing 52000 messages and at least one large message (26 MB attachment). 274MB got archived. No problem. TTBOMK even no indication that the system's struggling with memory. Besides, it is the rfc822 module throwing the exception, so I guess it's the module's implementation that is overstretched here, not archivemail itself. But I'd be interested in mailboxes triggering that exception, so if you think you can give away one that hasn't too private content, feel free to email me about that. (Of course we would have to stick to FTP or HTTP for the transfer of such a large mailbox.) Hmm, do I understand correctly that it depends on the total volume of the mailboxes an archivemail process is archiving? Weird. I fail to see how multiple mailboxes can add up in any way to hit some limit. Nikolaus ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-06-13 23:22 Message: Logged In: NO I think the problem is when pass a large amount of data to a single archivemail process. I was able to work around it using a little bit of bash: for i in `ls /var/spool/mail`; do archivemail -d 60 -o /var/spool/bak /var/spool/mail/$i; done hope this helps. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-06-06 00:45 Message: Logged In: NO I'm having the same exact problem. I corrected it by removing the message it got stuck on (after seeing it with the -v arg), but I'd rather have it go through without erroring out randomly. Micheal ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1491229&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2006-11-08 11:01:33
|
Bugs item #847555, was opened at 2003-11-23 08:08 Message generated for change (Settings changed) made by nikosch 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: Open Resolution: None 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: Elan Ruusamäe (ahmake) Date: 2006-02-08 23: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-08 08:50:15
|
Bugs item #1240580, was opened at 2005-07-19 01:53 Message generated for change (Comment added) made by nikosch 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: Pending >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: Nikolaus Schulz (nikosch) Date: 2006-11-08 09: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-03 03:11:40
|
Bugs item #1574720, was opened at 2006-10-10 20:37 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1574720&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: g2boojum (g2boojum) Assigned to: Nikolaus Schulz (nikosch) Summary: packaging request Initial Comment: I'm in the process of packaging 0.6.2 for Gentoo, and I've come across a couple of things that make packaging a bit of a pain for us. The first is that "python setup.py build" doesn't work out-of-the-box, because the tarball contains archivemail.py. and not archivemail. The second is that "python setup.py install" fails because "archivemail.1" isn't present in the archive. It's possible to generate it using "make archivemail.1", but then our users need to have docbook2X installed as a build dependency, and it's pretty heavy. Would it be possible to have the setup.py script updated to use "archivemail.py" instead of "archivemail" by default, and an already-generated "archivemail.1" file included in the tarball for the next release, please? ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2006-11-03 04:11 Message: Logged In: YES user_id=1594781 This is fixed in archivemail 0.7.0, which was released today. Thanks for reporting! ---------------------------------------------------------------------- Comment By: Peter Poeml (poeml) Date: 2006-10-13 14:55 Message: Logged In: YES user_id=78531 In my package (SUSE ;) I don't see any breakage with the latest tarball. I use: sed -i 's,man/man1,share/man/man1,' setup.py %{__python} setup.py build to build, and %{__python} setup.py install --prefix=%{_prefix} --root %{buildroot} ln -s archivemail.py %{buildroot}/%{_bindir}/archivemail to install. If there was previously a file "archivemail" in the tarball, sorry, I have no idea why and how it was created. What's odd about a *.py python script? :-) I actually used this Makefile (uncommitted change) to create the tarball: Index: Makefile =============================================== ==================== --- Makefile (revision 115) +++ Makefile (working copy) @@ -31,8 +31,13 @@ cvs tag -F current cvs tag -F $(VERSION_TAG) +tarball: + svn export https://svn.sourceforge.net/svnroot/archivemail/trunk archivemail-$(VERSION) + tar czf $(TARFILE) archivemail-$(VERSION) + rm -r archivemail-$(VERSION) + upload: - (cd dist && lftp -c 'open upload.sf.net && cd incoming && put $ (TARFILE)') + (lftp -c 'open upload.sf.net && cd incoming && put $(TARFILE)') With a 'cp' or 'mv', applied to the archivemail directory before tar'ing it up, the archivemail script could be created. About the man page: I didn't know how to generate it. All those docbook util cruft is a mystery to me. (On some machines I may have the right tools installed by accident, but that's about it.) ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2006-10-12 04:26 Message: Logged In: YES user_id=1594781 Thanks for your report. You are right, the last released tarball looks odd. A new release is pending anyway, I'll take care that this is fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1574720&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2006-10-20 23:47:22
|
Feature Requests item #1481316, was opened at 2006-05-03 21:08 Message generated for change (Settings changed) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456913&aid=1481316&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 Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Option to use date from most recent Received: header Initial Comment: Often, mail sent from others is sent while their machine has a incorrect time/date (sometimes months or years off). The current version of archivemail trusts that the time in the headers by their sending software is correct, when that is often not the case, and often results in messages getting archived when they shouldn't, and vice versa. It also negatively affects proper message ordering. I prefer to trust the datestamps from the last-hop Received header, because I KNOW my mailserver always has the correct time. I'm more interested in when it was received rather than when it was sent anyway. So, feature request: Either add an override to use the date from Received: or put it as the first date source for the header date checks. I know that using received may be trickier, since the format is not standardized, but most servers do put fairly standardized dates within the header, and is should be easy to cover the vast majority of cases with very little variation. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456913&aid=1481316&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2006-10-20 23:45:51
|
Feature Requests item #981865, was opened at 2004-06-29 12:38 Message generated for change (Settings changed) 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: Open Priority: 5 Submitted By: Nowicki Christophe (cscmeu) Assigned to: Nobody/Anonymous (nobody) 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: 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...> - 2006-10-20 23:09:55
|
Bugs item #904652, was opened at 2004-02-26 00:01 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=904652&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 Submitted By: Paul Rodger (paulrodger) Assigned to: Nikolaus Schulz (nikosch) Summary: test suite fails on sparc solaris 2.6 Initial Comment: Hello, I get the following message during test_archivemail.py Is this expected on sparc solaris 2.6? FAIL: exclusive_lock/unlock should create/delete an advisory lock ---------------------------------------------------------------------- Traceback (most recent call last): File "test_archivemail.py", line 163, in testExclusiveLock self.assertRaises(IOError, fcntl.flock, file.fileno(), lock_nb) File "/dist/sparc/solaris/Python/lib/python2.3/unittest.py", line 295, in failUnlessRaises raise self.failureException, excName AssertionError: IOError ---------------------------------------------------------------------- Ran 54 tests in 1477.271s FAILED (failures=1) ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2006-10-21 01:09 Message: Logged In: YES user_id=1594781 Hi, short version: this is fixed in subversion. Longer version: archivemail uses fcntl.flock() for locking. The corresponding flock(2) system call is not POSIX- compliant but a BSD thing. While it seems that most Unices provide the flock() syscall nowadays, they might emulate it with fcntl(2), which is a very different deer. Apparently Solaris does so, and the testsuite didn't anticipate that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=904652&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2006-10-20 14:29:10
|
Bugs item #904652, was opened at 2004-02-26 00:01 Message generated for change (Settings changed) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=904652&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 Submitted By: Paul Rodger (paulrodger) >Assigned to: Nikolaus Schulz (nikosch) Summary: test suite fails on sparc solaris 2.6 Initial Comment: Hello, I get the following message during test_archivemail.py Is this expected on sparc solaris 2.6? FAIL: exclusive_lock/unlock should create/delete an advisory lock ---------------------------------------------------------------------- Traceback (most recent call last): File "test_archivemail.py", line 163, in testExclusiveLock self.assertRaises(IOError, fcntl.flock, file.fileno(), lock_nb) File "/dist/sparc/solaris/Python/lib/python2.3/unittest.py", line 295, in failUnlessRaises raise self.failureException, excName AssertionError: IOError ---------------------------------------------------------------------- Ran 54 tests in 1477.271s FAILED (failures=1) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=904652&group_id=49630 |
|
From: Nikolaus S. <mic...@we...> - 2006-10-16 15:07:26
|
Hi, mailman's recipient filter option "require_explicit_destination" is now unset, I hope tracker items will no longer trigger moderation requests. Nikolaus |
|
From: SourceForge.net <no...@so...> - 2006-10-16 02:20:13
|
Bugs item #884481, was opened at 2004-01-25 16:45 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=884481&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: Invalid Priority: 5 Submitted By: Paul Rodger (paulrodger) Assigned to: Nikolaus Schulz (nikosch) Summary: Finds zero messages in Apple Mail folder Initial Comment: From: Pascal Chavaillaz <pa...@ch...> Subject: Question about your archivemail python script Date: Sun, 25 Jan 2004 16:34:12 +0100 I have tried to use your python script against Apple OSX Mail implementation but I seem to have a few problems ! Performing a dry run on a copy of my "Mail" directory, I get the following log : iBook-de-Pascal:~/Travail/archivemail-0.6.1 pascal$ ./archivemail -d1 --no-compress -v -n -o $HOME/Travail/Archive $HOME/Travail/Mail/Mailboxes/* ./archivemail:760: SyntaxWarning: assignment to None (None, last_dir) = os.path.split(os.path.dirname(message.fp.name)) archiving '/Users/pascal/Travail/Mail/Mailboxes/#Adoption' to '/Users/pascal/Travail/Archive/#Adoption_archive' ... set tempfile directory to '/tmp/tmpaD_WWxarchivemail' guessing mailbox is of type: MH finished reading messages /Users/pascal/Travail/Mail/Mailboxes/#Adoption: I would have archived 0 of 0 message(s) in 0.0 seconds archiving '/Users/pascal/Travail/Mail/Mailboxes/#Adoption.mbox' to '/Users/pascal/Travail/Archive/#Adoption.mbox_archive' ... set tempfile directory to '/tmp/tmpDJOeVfarchivemail' guessing mailbox is of type: MH finished reading messages /Users/pascal/Travail/Mail/Mailboxes/#Adoption.mbox: I would have archived 0 of 0 message(s) in 0.0 seconds archiving '/Users/pascal/Travail/Mail/Mailboxes/#Les Amis de Svieta' to '/Users/pascal/Travail/Archive/#Les Amis de Svieta_archive' ... set tempfile directory to '/tmp/tmpBbhQKYarchivemail' guessing mailbox is of type: MH finished reading messages /Users/pascal/Travail/Mail/Mailboxes/#Les Amis de Svieta: I would have archived 0 of 0 message(s) in 0.0 seconds archiving '/Users/pascal/Travail/Mail/Mailboxes/#Les Amis de Svieta.mbox' to '/Users/pascal/Travail/Archive/#Les Amis de Svieta.mbox_archive' ... set tempfile directory to '/tmp/tmpHGHnrQarchivemail' guessing mailbox is of type: MH finished reading messages /Users/pascal/Travail/Mail/Mailboxes/#Les Amis de Svieta.mbox: I would have archived 0 of 0 message(s) in 0.0 seconds archiving '/Users/pascal/Travail/Mail/Mailboxes/#Priv?' to '/Users/pascal/Travail/Archive/#Priv?_archive' ... set tempfile directory to '/tmp/tmpU5cnU2archivemail' guessing mailbox is of type: MH finished reading messages /Users/pascal/Travail/Mail/Mailboxes/#Priv?: I would have archived 0 of 0 message(s) in 0.0 seconds archiving '/Users/pascal/Travail/Mail/Mailboxes/#Priv?.mbox' to '/Users/pascal/Travail/Archive/#Priv?.mbox_archive' ... set tempfile directory to '/tmp/tmpGpkCm0archivemail' guessing mailbox is of type: MH finished reading messages /Users/pascal/Travail/Mail/Mailboxes/#Priv?.mbox: I would have archived 0 of 0 message(s) in 0.0 seconds archiving '/Users/pascal/Travail/Mail/Mailboxes/#Professionnel.mbox' to '/Users/pascal/Travail/Archive/#Professionnel.mbox_archive' ... set tempfile directory to '/tmp/tmp_42rhsarchivemail' guessing mailbox is of type: MH finished reading messages /Users/pascal/Travail/Mail/Mailboxes/#Professionnel.mbox: I would have archived 0 of 0 message(s) in 0.0 seconds archiving '/Users/pascal/Travail/Mail/Mailboxes/Deleted Messages (.Mac ).mbox' to '/Users/pascal/Travail/Archive/Deleted Messages (.Mac ).mbox_archive' ... set tempfile directory to '/tmp/tmprSsTHYarchivemail' guessing mailbox is of type: MH finished reading messages /Users/pascal/Travail/Mail/Mailboxes/Deleted Messages (.Mac ).mbox: I would have archived 0 of 0 message(s) in 0.0 seconds archiving '/Users/pascal/Travail/Mail/Mailboxes/Deleted Messages.mbox' to '/Users/pascal/Travail/Archive/Deleted Messages.mbox_archive' ... set tempfile directory to '/tmp/tmpYHWBcVarchivemail' guessing mailbox is of type: MH finished reading messages /Users/pascal/Travail/Mail/Mailboxes/Deleted Messages.mbox: I would have archived 0 of 0 message(s) in 0.0 seconds archiving '/Users/pascal/Travail/Mail/Mailboxes/Outbox.mbox' to '/Users/pascal/Travail/Archive/Outbox.mbox_archive' ... set tempfile directory to '/tmp/tmpiEIqJ6archivemail' guessing mailbox is of type: MH finished reading messages /Users/pascal/Travail/Mail/Mailboxes/Outbox.mbox: I would have archived 0 of 0 message(s) in 0.0 seconds cleaning up ... cleaning up ... cleaning up ... cleaning up ... cleaning up ... cleaning up ... cleaning up ... cleaning up ... cleaning up ... cleaning up ... iBook-de-Pascal:~/Travail/archivemail-0.6.1 pascal$ My first question is about the 760:SyntaxWarning, what does it mean ? And second, even though I had selected 1 day old messages, dry run shows that no message would be archived !! What am I doing wrong ? Thanks in advance for any tip Cheers Pascal ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2006-10-15 19:20 Message: Logged In: YES user_id=1312539 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-10-01 16:31 Message: Logged In: YES user_id=1594781 You're commanding archivemail to archive all mailboxes in ~/Travail/Mail/Mailboxes. Looking at the mailboxes of Mail.app on a machine running MacOS 10.3.9, I find a folder ~/Library/Mail/Mailboxes, I guess it's the equivalent of the one you were looking at. This directory contains various *.mbox entities, but these are _folders_ carrying the 'real' mailboxes in mbox format inside. So they're no valid mailboxes itself. One could argue that archivemail should handle invalid mailbox targets more gracefully, but your problem doesn't look like a bug in archivemail. The syntax warning has meanwhile been fixed, so I'm closing this bug. ---------------------------------------------------------------------- Comment By: Peter Poeml (poeml) Date: 2006-04-25 14:17 Message: Logged In: YES user_id=78531 the syntax warning is fixed in CVS ---------------------------------------------------------------------- Comment By: Thomas Arnhold (slyzer2k) Date: 2004-05-08 12:32 Message: Logged In: YES user_id=645517 First question is answered in Bug #843890 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=884481&group_id=49630 |
|
From: Nikolaus S. <mic...@we...> - 2006-10-14 22:31:56
|
Hi, tracker state notifications are now forwarded to this list. This can be a little bit verbose, but I think the added convenience is worth it. Nikolaus |
|
From: SourceForge.net <no...@so...> - 2006-10-14 21:39:50
|
Feature Requests item #1058880, was opened at 2004-11-02 16:18 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456913&aid=1058880&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: Interface Improvements (example) Group: Next Release (example) >Status: Closed Priority: 5 Submitted By: Fernan Aguero (fernan) Assigned to: Nobody/Anonymous (nobody) Summary: allow user to change tempdir Initial Comment: I've got a failed archivemail run because my /tmp partition filled up. Other utilities honor TMPDIR or similar env variables. Then I can set TMPDIR to say /usr/tmp or /var/tmp and be happy. archivemail does not use TMPDIR (I've tried), but perhaps some other env variable? Perhaps you could add this option? Or perhaps it's already there but not described in the man page? Thanks for a useful piece of software! Fernan ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2006-10-14 23:39 Message: Logged In: YES user_id=1594781 archivemail *does* honor TMPDIR. To be precise, it should pick the first of TMPDIR, TEMP, TMP where the user can create files in. This is standard Python behaviour. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456913&aid=1058880&group_id=49630 |
|
From: Brandon K. <kni...@bl...> - 2006-10-14 17:14:19
|
For -users, you may be right. Sorry, didn't look that closely. For -devel, you can get both! :) You could set up certain senders as =20 "auto accept" messages, and others requiring approval for subscription =20 and/or message submission. The nice thing about some folks on a =20 whitelist and others on an approval list means that you could have two =20 levels of submitters: those who are known and trusted, those who are =20 helpful but are not part of the core team. Again, just my opinion. Please do whatever you think will help. Of =20 course, if you find something doesn't work, you can always change it =20 with ease. I'm not active on this project so I'm trying to be careful =20 not to inject too much of my opinions here, it might not reflect the =20 current active development team. Hope this helps! :) --=20 -bk Quoting Nikolaus Schulz <mic...@we...>: > On Fri, Oct 13, 2006 at 08:23:03PM -0700, Brandon Knitter wrote: >> Users list you may want to open up for subscription with verification >> email confirmation. > > Isn't that the current configuration? Anyone can subscribe, both to > -user and -devel. Only subscribers can post directly, non-subscriber > postings are discarded for -user, but moderated for -devel. > > Am I missing something? > >> The -devel list I would recommend you keep it as is for two reasons: >> >> 1. keeps spammers out; > > If sf.net doesn't provide spam-filtering, I guess we might have to bite > that bullet. That is, forget about a really open list. :-( > >> 2. keeps end-user support questions out which should be on the -users >> list > > See below... > >> Please take my commments as a recommendation and adjust the settings >> to what you feel are appropriate. > > Thanks. > > I thought about using the -devel list address as a general purpose, > simple means to reach all of us, that is, the people in charge. For > example, as the maintainer email address in the archivemail > distribution, or to automatically forward tracker state notifications > to -devel, so that anyone who cares can pick items up. > > Regarding the latter, I've found the trackers still configured to send > notifications to Paul, and I've temporarily set it to my email address. > Obviously it would be much better to direct such general stuff to > -devel. But I don't think this will work with a moderated list. > > IMO list moderation means work for the moderators, involves annoying > extra traffic (autogenerated blurb) for all parties, and leaves the > sender both still barred from the list and in an uncertain state until > his email is approved, with an unpredictable delay. I guess most people > wouldn't want to subscribe, because they simply have not enough interest > in archivemail. > > Any suggestions how to get a *usable* general contact address for all of > us? > > Nikolaus > >> Quoting Nikolaus Schulz <mic...@we...>: >> >> >Hi, >> > >> >apparently mailing lists at sourceforge.net are subscribers-only by >> >default, that is, postings of non-members are moderated. I would really >> >prefer it to be open for anyone, so that users can easily contact us, >> >but what about spam? The sf.net docs don't state if they spam-filter >> >the lists. What's your bet? Do you have experience with open mailing >> >lists at sf.net? > > !DSPAM:4531170e317314848360862! > > > |
|
From: Nikolaus S. <mic...@we...> - 2006-10-14 17:06:24
|
On Fri, Oct 13, 2006 at 08:23:03PM -0700, Brandon Knitter wrote: > Users list you may want to open up for subscription with verification > email confirmation. Isn't that the current configuration? Anyone can subscribe, both to -user and -devel. Only subscribers can post directly, non-subscriber postings are discarded for -user, but moderated for -devel. Am I missing something? > The -devel list I would recommend you keep it as is for two reasons: > > 1. keeps spammers out; If sf.net doesn't provide spam-filtering, I guess we might have to bite that bullet. That is, forget about a really open list. :-( > 2. keeps end-user support questions out which should be on the -users > list See below... > Please take my commments as a recommendation and adjust the settings > to what you feel are appropriate. Thanks. I thought about using the -devel list address as a general purpose, simple means to reach all of us, that is, the people in charge. For example, as the maintainer email address in the archivemail distribution, or to automatically forward tracker state notifications to -devel, so that anyone who cares can pick items up. Regarding the latter, I've found the trackers still configured to send notifications to Paul, and I've temporarily set it to my email address. Obviously it would be much better to direct such general stuff to -devel. But I don't think this will work with a moderated list. IMO list moderation means work for the moderators, involves annoying extra traffic (autogenerated blurb) for all parties, and leaves the sender both still barred from the list and in an uncertain state until his email is approved, with an unpredictable delay. I guess most people wouldn't want to subscribe, because they simply have not enough interest in archivemail. Any suggestions how to get a *usable* general contact address for all of us? Nikolaus > Quoting Nikolaus Schulz <mic...@we...>: > > >Hi, > > > >apparently mailing lists at sourceforge.net are subscribers-only by > >default, that is, postings of non-members are moderated. I would really > >prefer it to be open for anyone, so that users can easily contact us, > >but what about spam? The sf.net docs don't state if they spam-filter > >the lists. What's your bet? Do you have experience with open mailing > >lists at sf.net? |
|
From: Brandon K. <kni...@bl...> - 2006-10-14 03:31:40
|
Users list you may want to open up for subscription with verification
email confirmation.
The -devel list I would recommend you keep it as is for two reasons:
1. keeps spammers out;
2. keeps end-user support questions out which should be on the -users list
Please take my commments as a recommendation and adjust the settings
to what you feel are appropriate.
--
-bk
Quoting Nikolaus Schulz <mic...@we...>:
> Hi,
>
> apparently mailing lists at sourceforge.net are subscribers-only by
> default, that is, postings of non-members are moderated. I would really
> prefer it to be open for anyone, so that users can easily contact us,
> but what about spam? The sf.net docs don't state if they spam-filter
> the lists. What's your bet? Do you have experience with open mailing
> lists at sf.net?
>
> Thanks,
> Nikolaus
>
>
> !DSPAM:45303dd3190531479266655!
>
>
>
|
|
From: Nikolaus S. <mic...@we...> - 2006-10-14 01:39:28
|
Hi, apparently mailing lists at sourceforge.net are subscribers-only by default, that is, postings of non-members are moderated. I would really prefer it to be open for anyone, so that users can easily contact us, but what about spam? The sf.net docs don't state if they spam-filter the lists. What's your bet? Do you have experience with open mailing lists at sf.net? Thanks, Nikolaus |
|
From: Nikolaus S. <mic...@we...> - 2006-10-01 21:43:23
|
Hello Peter, hello Brandon,
this email is not very short, so if you're in a hurry, you may want to
skip forward to the last two paragraphs, which I think are the most
important.
As Peter suggested, I've set up a dedicated mailing list for
archivemail development. Actually I first thought this would be drastic
overkill, but this way discussions will be public, automatically
archived, and separated from the -user list. We are all list admins
with our sf.net addresses; I'll send you the admin password separately,
so no one's tempted to followup to -devel without deleting it. :-) To
encourage you a little bit, I'm CC'ing our new, shiny list. So, I
invite you to subscribe... Say hi, list! :-)
By the way: I've finally subscribed to the -user list. And while I
missed Peter's analysis of the test suite failure when he posted it
there, his findings there still enabled me to derive a fix, which I took
the liberty to commit last night. Thanks, Peter!
And while at organizing communications: it's not really important,
but I hereby propose to shutdown the archivemail web forums. There has
been a total of one (1) posting in the forums since 2002. I don't want
to hide my bias here; I don't like such forums in general, and IMO the
sf.net web interface has a particularly rotten layout.[1] Since no one
seems to use them, why keep them around? Forums might be nicer for
noobs that depend on a GUI for everything, but our users likely aren't
of that kind. What do you think?
So much for communications, let's turn to the real stuff... I've
committed some first fixes to the repository. These shouldn't be very
controversial, but look out. ;-) If you haven't done so already, you
may want to update your working copies to pull in the changes; the svn
log should be self-explanatory.
While starting this email, I wanted to compile a complete list of
further issues that have caught my attention recently and include it
here, but the mail is long enough without. :-) Expect details, more
bugfixes here and there, and perhaps queries from my side about various
things soon. Please tell me if you're working on something or planning
to do so. Or if you know about issues that should be fixed in the next
release but you don't have the time to tackle, again, don't mind to tell
me, I'll do my best. Brandon, some old tracker items are still assigned
to you; what about these? Do you mind to share your thoughts? If you
started to prepare some code but got stuck with it, I'd be interested in
incomplete stuff, too.
Now, here's my big pet goal. Considering that IMAP doesn't really
work in the last release, and I still being a Debian guy *g*, I'd really
like to push for another release soon. This would a) fix IMAP for our
users not running Debian -- the Debian package is already fixed in this
regard -- and b) would make the upcoming Debian release, codename Etch,
for which the freeze is scheduled for October 18th. Actually, to be in
time for Debian, we would have to release at least 12 days before the
freeze, that is October 6th. Wow, that's next Friday! Geez!
Would such a close deadline mean to go for a hasty release? I don't
think so -- the IMAP issue pretty much warrants a quick bugfix release
on its own, and if we manage to get further fixes or even some minor new
feature in, perfect. And although the Debian package has some fixes
already, it is not really in the clean state I would like it to be for
the next two years that people will run Debian Etch, so the Debian users
would still profit. So, personally, I'd want to try and fix as many
things as possible in the next days, and release in time so we make
Debian 4.0. If you feel comfortable with this tight goal, but also too
overloaded to contribute, I would be willing to do the administrative
work, too: preparing release notes, doing the release itself, making an
announcement, etc. The sf.net site is pretty well-documented, so I'm
optimistic that I could get it done without someone babysitting me all
around. :-)
What do you think?
Cheers,
Nikolaus
[1] This applies to the list archives as well, but most of the time one
doesn't have to use that.
|
1 message has been excluded from this view by a project administrator.
