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...> - 2008-01-18 23:24:28
|
Support Requests item #1874094, was opened at 2008-01-17 21:44 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456911&aid=1874094&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: Yes Submitted By: Curtis Wong (ckwsp101) Assigned to: Nikolaus Schulz (nikosch) Summary: exception against 14G imap account Initial Comment: set tempfile directory to '/tmp/tmppQtyp1archivemail' guessing mailbox is of type: imap(s) imap filter: '(BEFORE 21-Jul-2007 UNFLAGGED)' establishing connection to server localhost logging in to server as cro...@ic... examining imap folder 'inbox' read-only folder has 9742 message(s) searching messages matching criteria 0 messages are matching filter fetching size of messages... cleaning up ... removing stale tempfile directory '/tmp/tmppQtyp1archivemail' Traceback (most recent call last): File "/home/mis/bin/archivemail", line 1603, in ? main() File "/home/mis/bin/archivemail", line 702, in main archive(mailbox_path) File "/home/mis/bin/archivemail", line 1145, in archive _archive_imap(mailbox_name, final_archive_name) File "/home/mis/bin/archivemail", line 1401, in _archive_imap result, response = imap_srv.fetch('1:*', '(RFC822.SIZE)') File "/usr/lib/python2.3/imaplib.py", line 417, in fetch typ, dat = self._simple_command(name, message_set, message_parts) File "/usr/lib/python2.3/imaplib.py", line 1000, in _simple_command return self._command_complete(name, self._command(name, *args)) File "/usr/lib/python2.3/imaplib.py", line 832, in _command_complete raise self.abort('command: %s => %s' % (name, val)) imaplib.abort: command: FETCH => socket error: EOF ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2008-01-19 00:24 Message: Logged In: YES user_id=1594781 Originator: NO Private email conversation with the submitter suggests that his server his broken or overloaded, therefore I'm closing this tracker. ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2008-01-18 23:49 Message: Logged In: YES user_id=1594781 Originator: NO Upon request of the submitter, I set this tracker item to private because the report includes a private email address. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456911&aid=1874094&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2008-01-18 22:49:42
|
Support Requests item #1874094, was opened at 2008-01-17 21:44 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456911&aid=1874094&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 >Private: Yes Submitted By: Curtis Wong (ckwsp101) >Assigned to: Nikolaus Schulz (nikosch) Summary: exception against 14G imap account Initial Comment: set tempfile directory to '/tmp/tmppQtyp1archivemail' guessing mailbox is of type: imap(s) imap filter: '(BEFORE 21-Jul-2007 UNFLAGGED)' establishing connection to server localhost logging in to server as cro...@ic... examining imap folder 'inbox' read-only folder has 9742 message(s) searching messages matching criteria 0 messages are matching filter fetching size of messages... cleaning up ... removing stale tempfile directory '/tmp/tmppQtyp1archivemail' Traceback (most recent call last): File "/home/mis/bin/archivemail", line 1603, in ? main() File "/home/mis/bin/archivemail", line 702, in main archive(mailbox_path) File "/home/mis/bin/archivemail", line 1145, in archive _archive_imap(mailbox_name, final_archive_name) File "/home/mis/bin/archivemail", line 1401, in _archive_imap result, response = imap_srv.fetch('1:*', '(RFC822.SIZE)') File "/usr/lib/python2.3/imaplib.py", line 417, in fetch typ, dat = self._simple_command(name, message_set, message_parts) File "/usr/lib/python2.3/imaplib.py", line 1000, in _simple_command return self._command_complete(name, self._command(name, *args)) File "/usr/lib/python2.3/imaplib.py", line 832, in _command_complete raise self.abort('command: %s => %s' % (name, val)) imaplib.abort: command: FETCH => socket error: EOF ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2008-01-18 23:49 Message: Logged In: YES user_id=1594781 Originator: NO Upon request of the submitter, I set this tracker item to private because the report includes a private email address. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456911&aid=1874094&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2008-01-18 16:58:05
|
Patches item #1874868, was opened at 2008-01-18 11:58 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=1874868&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: Tim O'Donnell (tim_odonnell) Assigned to: Nobody/Anonymous (nobody) Summary: Allow writing to world-writable directory with sticky bit Initial Comment: Current behavior: If the destination directory is world-writable, halt. New behavior: If the destination directory is world-writable, then proceed only if the directory's sticky bit is set. Rationale: If the destination directory is world-writable with the sticky bit set, then only the user who owns the archived file (or the owner of the directory) can delete it. From the user's perspective, it's equivalent to the directory not being world-writable, so there's no need for concern. I'm including an svn diff of the quick change. If you'd like this another way, just let me know. Thanks! Tim ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1874868&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2008-01-17 20:44:24
|
Support Requests item #1874094, was opened at 2008-01-17 12:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456911&aid=1874094&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 Private: No Submitted By: Curtis Wong (ckwsp101) Assigned to: Nobody/Anonymous (nobody) Summary: exception against 14G imap account Initial Comment: set tempfile directory to '/tmp/tmppQtyp1archivemail' guessing mailbox is of type: imap(s) imap filter: '(BEFORE 21-Jul-2007 UNFLAGGED)' establishing connection to server localhost logging in to server as cro...@ic... examining imap folder 'inbox' read-only folder has 9742 message(s) searching messages matching criteria 0 messages are matching filter fetching size of messages... cleaning up ... removing stale tempfile directory '/tmp/tmppQtyp1archivemail' Traceback (most recent call last): File "/home/mis/bin/archivemail", line 1603, in ? main() File "/home/mis/bin/archivemail", line 702, in main archive(mailbox_path) File "/home/mis/bin/archivemail", line 1145, in archive _archive_imap(mailbox_name, final_archive_name) File "/home/mis/bin/archivemail", line 1401, in _archive_imap result, response = imap_srv.fetch('1:*', '(RFC822.SIZE)') File "/usr/lib/python2.3/imaplib.py", line 417, in fetch typ, dat = self._simple_command(name, message_set, message_parts) File "/usr/lib/python2.3/imaplib.py", line 1000, in _simple_command return self._command_complete(name, self._command(name, *args)) File "/usr/lib/python2.3/imaplib.py", line 832, in _command_complete raise self.abort('command: %s => %s' % (name, val)) imaplib.abort: command: FETCH => socket error: EOF ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456911&aid=1874094&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-12-18 11:37:34
|
Patches item #1852984, was opened at 2007-12-18 19:37 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=1852984&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: Yong Yoon Kit (yoonkit) Assigned to: Nobody/Anonymous (nobody) Summary: Archive DSpam identified mail. Initial Comment: Checks the message headers for the DSPAM-Confidence tag, and acts on the confidence values. The quarantined files in /var/dspam/mail/dspam.mbox tend to grow large, and generally messages which are tagged at 58% and above are true spam. These files can be deleted. So the modifications to archive mails in this patch does these things: 1) New option: spam_confidence 2) Command line flag: --spam=NUM 3) Sets minimum date >= 0 (instead of 1), so I can delete messages within the day 4) in should_archive, does the check between the message spam confidence and the option spam confidence threshold I can then cronjob archivemail to clear off all the true spams, and this works well. BTW, thanks for this utility. yk. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1852984&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-12-17 23:13:04
|
Feature Requests item #1852179, was opened at 2007-12-17 10:16 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456913&aid=1852179&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: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Allow IMAP login with '@' in username Initial Comment: The IMAP server I use is configured to use user@host as the username. Since the only way to supply your username is within the url, this doesn't work. Workaround: replace string.split with string.rsplit in split_qstr() (line 1540) and use user@host@domain ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-12-18 00:13 Message: Logged In: YES user_id=1594781 Originator: NO archivemail 0.7.1 and newer allow quoting the username, which fixes this issue. Actually, I think this problem only exists in v0.7.0. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456913&aid=1852179&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-12-17 09:16:38
|
Feature Requests item #1852179, was opened at 2007-12-17 01:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456913&aid=1852179&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 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Allow IMAP login with '@' in username Initial Comment: The IMAP server I use is configured to use user@host as the username. Since the only way to supply your username is within the url, this doesn't work. Workaround: replace string.split with string.rsplit in split_qstr() (line 1540) and use user@host@domain ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456913&aid=1852179&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-13 22:39:23
|
Patches item #1764846, was opened at 2007-07-31 21:19 Message generated for change (Comment added) made by chrisbra 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: Christian (chrisbra) Date: 2007-11-13 23:39 Message: Logged In: YES user_id=1928606 Originator: NO ok, whatever you like more is fine with me. Christian ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-05 22:03 Message: Logged In: YES user_id=1594781 Originator: NO That's interesting. I don't know why, but I really didn't consider your approach; I have a different, "optimized" implementation of --archive-all. I'm attaching the patch; it applies against the current trunk. Actually I'm not sure which of the two patches is cleaner. Or should I say "less unclean"? Well. Perhaps I should postpone this decision for the v0.7.1 release. Nikolaus File Added: archivemail-all-optim.diff ---------------------------------------------------------------------- Comment By: Christian (chrisbra) Date: 2007-11-03 13:55 Message: Logged In: YES user_id=1928606 Originator: NO Hi, sorry, I must have made a mistake when submitting the patch. But if it is true, that --archive-all will be the same as --days=0 and --include-flagged, then the following patch should achieve it (against 0.7.0): --- archivemail.orig 2007-11-03 13:36:10.000000000 +0100 +++ archivemail.all 2007-11-03 13:35:55.000000000 +0100 @@ -201,7 +201,7 @@ """ try: opts, args = getopt.getopt(args, '?D:S:Vd:hno:F:P:qs:uv', - ["date=", "days=", "delete", "dry-run", "help", + ["archive-all", "date=", "days=", "delete", "dry-run", "help", "include-flagged", "no-compress", "output-dir=", "filter-append=", "pwfile=", "dont-mangle", "archive-name=", @@ -213,6 +213,13 @@ archive_by = None for o, a in opts: + if o == '--archive-all': + if archive_by: + user_error("you cannot specify --archive-all and -d or -D options") + archive_by = "all" + self.archive_all = 1 + self.days_old_max = 0 + self.include_flagged = 1 if o == '--delete': self.delete_old_mail = 1 if o == '--include-flagged': @@ -223,12 +230,12 @@ self.warn_duplicates = 1 if o in ('-D', '--date'): if archive_by: - user_error("you cannot specify both -d and -D options") + user_error("you cannot specify --archive-all and -d or -D options") archive_by = "date" self.date_old_max = self.date_argument(a) if o in ('-d', '--days'): if archive_by: - user_error("you cannot specify both -d and -D options") + user_error("you cannot specify --archive-all and -d or -D options") archive_by = "days" self.days_old_max = string.atoi(a) if o in ('-o', '--output-dir'): @@ -647,6 +654,7 @@ mailbox compressed with gzip. Options are as follows: + --archive-all archive all messages -d, --days=NUM archive messages older than NUM days (default: %d) -D, --date=DATE archive messages older than DATE -o, --output-dir=DIR directory to store archives (default: same as original) regards, Christian ---------------------------------------------------------------------- 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-11-13 22:37:42
|
Patches item #1764855, was opened at 2007-07-31 21:27 Message generated for change (Comment added) made by chrisbra 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: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nikolaus Schulz (nikosch) 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 ---------------------------------------------------------------------- Comment By: Christian (chrisbra) Date: 2007-11-13 23:37 Message: Logged In: YES user_id=1928606 Originator: NO Glad to see some progress in archivemail. Thanks for applying the patch. Christian ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-13 22:18 Message: Logged In: YES user_id=1594781 Originator: NO This will be in archivemail 0.7.3. Note that I didn't add an option to honour 'received' headers, but made it standard behaviour to do so. The patch had to be fixed a little bit, but it was pretty close, thanks. :-) Nikolaus ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764855&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-13 21:18:02
|
Patches item #1764855, was opened at 2007-07-31 21:27 Message generated for change (Comment added) made by nikosch 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: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Nikolaus Schulz (nikosch) 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 ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-13 22:18 Message: Logged In: YES user_id=1594781 Originator: NO This will be in archivemail 0.7.3. Note that I didn't add an option to honour 'received' headers, but made it standard behaviour to do so. The patch had to be fixed a little bit, but it was pretty close, thanks. :-) Nikolaus ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1764855&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-13 20:58:28
|
Feature Requests item #1481316, was opened at 2006-05-03 21:08 Message generated for change (Comment added) 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: Closed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Nikolaus Schulz (nikosch) 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. ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-13 21:58 Message: Logged In: YES user_id=1594781 Originator: NO I agree. Note that archivemail in fact determines the age of a message by delivery time. If present, it uses the 'Delivery-date' header, which should be fine, but this header is not standard. So, if this fails, archivemail 0.7.3 will try the latest 'Received' header before resorting to headers that precede the message transport. The order in which messages are saved is an unrelated issue, though; archivemail does not sort messages in any way. Oh, and the 'Received' header *is* standardized in RFC 2822, although not all mailers may follow the standard. Nikolaus ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456913&aid=1481316&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-09 17:12:37
|
Bugs item #1753702, was opened at 2007-07-13 19:36 Message generated for change (Comment added) made by nikosch 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: Jonathan Ciesla (limburgher) Assigned to: Nikolaus Schulz (nikosch) 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. ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-09 18:12 Message: Logged In: YES user_id=1594781 Originator: NO I strongly doubt newer archivemail versions will behave differently. Can we agree to close this bug? Looks like it's just the quota that's barfing, so it's not related to archivemail. ---------------------------------------------------------------------- Comment By: Jonathan Ciesla (limburgher) Date: 2007-11-09 12:08 Message: Logged In: YES user_id=791236 Originator: YES Actually, you're right, it is quota related. Though it may not occur with 0.7.1, so I'll check and let you know. ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-09 04:23 Message: Logged In: YES user_id=1594781 Originator: NO I don't see how this relates to the mailboxes in question, since at this point, archivemail may have checked if the mailbox exists, and may have seteuid() to the owners uid, but it has not yet opened the mailbox. The error is pretty bizarre. Did you try to track this down? I would guess this might be related to your quota, although I barely know about quotas. :-) Nikolaus ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1753702&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-09 17:06:49
|
Bugs item #1007172, was opened at 2004-08-11 12:52 Message generated for change (Comment added) 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: Closed >Resolution: Out of Date 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...) ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-09 18:06 Message: Logged In: YES user_id=1594781 Originator: NO Another very old bug... I've contacted the submitter, and he can no longer reproduce this. Closing. ---------------------------------------------------------------------- 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-09 11:08:55
|
Bugs item #1753702, was opened at 2007-07-13 12:36 Message generated for change (Comment added) made by limburgher 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: Jonathan Ciesla (limburgher) Assigned to: Nikolaus Schulz (nikosch) 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. ---------------------------------------------------------------------- >Comment By: Jonathan Ciesla (limburgher) Date: 2007-11-09 05:08 Message: Logged In: YES user_id=791236 Originator: YES Actually, you're right, it is quota related. Though it may not occur with 0.7.1, so I'll check and let you know. ---------------------------------------------------------------------- Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-08 21:23 Message: Logged In: YES user_id=1594781 Originator: NO I don't see how this relates to the mailboxes in question, since at this point, archivemail may have checked if the mailbox exists, and may have seteuid() to the owners uid, but it has not yet opened the mailbox. The error is pretty bizarre. Did you try to track this down? I would guess this might be related to your quota, although I barely know about quotas. :-) Nikolaus ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1753702&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-09 03:23:55
|
Bugs item #1753702, was opened at 2007-07-13 19:36 Message generated for change (Comment added) made by nikosch 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: Jonathan Ciesla (limburgher) >Assigned to: Nikolaus Schulz (nikosch) 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. ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-09 04:23 Message: Logged In: YES user_id=1594781 Originator: NO I don't see how this relates to the mailboxes in question, since at this point, archivemail may have checked if the mailbox exists, and may have seteuid() to the owners uid, but it has not yet opened the mailbox. The error is pretty bizarre. Did you try to track this down? I would guess this might be related to your quota, although I barely know about quotas. :-) Nikolaus ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1753702&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-09 03:08:16
|
Bugs item #855269, was opened at 2003-12-06 12:08 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=855269&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: Karl Chen (quarl) >Assigned to: Nikolaus Schulz (nikosch) Summary: need an option to skip procmail_lock Initial Comment: To operate on mboxes in e.g. $MAIL=/var/mail/$USER, you can't use procmail locks (/var/mail/$USER.lock) since you don't have write permission to that directory. Since procmail doesn't write there either, this should be allowed via a command-line option (or even automatically detect if directory is not writeable by user) ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-09 04:08 Message: Logged In: YES user_id=1594781 Originator: NO Okay, I see this is a problem. As far as I know procmail *does* dotlocking in /var/mail. I am not an overall Unix wizard, but on my Debian boxes, /var/mail is writeable for group mail, and there exist several utilities for dotlocking, all of which are setgid mail. The mailbox module in python 2.5 does indeed just skip dotlocking, if the program has no write permissions. Of course that's not really ideal. :-) archivemail could search for known dotlocking utilities and try to acquire a dotlock with their help... I have to think about it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=855269&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-09 01:22:25
|
Bugs item #1507394, was opened at 2006-06-16 17:57 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1507394&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: os.setegid(0) Fails on RHEL4 Initial Comment: On newer 2.6 kernels archivemail fails to set it's UID and GID back to root and gives the error: --------------------------------------------------------- /var/spool/mail/mwaltz: archived 0 of 1360 message(s) in 6.7 seconds changing effective groupid and userid back to root 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 1057, in archive os.setegid(0) OSError: [Errno 1] Operation not permitted cleaning up ... --------------------------------------------------------- This happens with pythton v2.2, 2.3, and 2.4. The archive is created, but only if the users mbox and archive directory are in the same group and have the correct permissions. Solutions I've come across range from disabling SElinux(Done, still not luck), creating a c-wrapper for the script since apparently the 2.6 kernels don't allow python scripts to run as suid. A final suggestion is to disable all SELinux options and recompile the kernel. ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-09 02:22 Message: Logged In: YES user_id=1594781 Originator: NO This is strange. I must admit I have no clue at all about SELinux... Well, this bug is rather old, anonymous reporter, no one else has ever complained, and I suspect this might have been a misconfigured machine. Moreover, this the seteuid feature is now deprecated and will go away in the near future. Closing. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-06-16 18:11 Message: Logged In: NO I should probably clarify that is only appears on RedHat Enterprise Linux v4 systems. I tested it on Debian and it doesn't have this issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1507394&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-08 00:16:29
|
Patches item #1826757, was opened at 2007-11-06 12:30 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1826757&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: Christian (chrisbra) >Assigned to: Nikolaus Schulz (nikosch) Summary: detect imap folder-seperator Initial Comment: Hi, I just looked around the debian BTS and saw bug 368112. Attached is a patch, that will make archivemail trying to use a different folder-separator, if selecting the folder fails. ---------------------------------------------------------------------- >Comment By: Nikolaus Schulz (nikosch) Date: 2007-11-08 01:16 Message: Logged In: YES user_id=1594781 Originator: NO This problem is fixed in archivemail 0.7.1, with a different implementation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1826757&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-06 11:30:43
|
Patches item #1826757, was opened at 2007-11-06 12:30 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=1826757&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: Christian (chrisbra) Assigned to: Nobody/Anonymous (nobody) Summary: detect imap folder-seperator Initial Comment: Hi, I just looked around the debian BTS and saw bug 368112. Attached is a patch, that will make archivemail trying to use a different folder-separator, if selecting the folder fails. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=1826757&group_id=49630 |
|
From: SourceForge.net <no...@so...> - 2007-11-05 21:03:36
|
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-05 22:03 Message: Logged In: YES user_id=1594781 Originator: NO That's interesting. I don't know why, but I really didn't consider your approach; I have a different, "optimized" implementation of --archive-all. I'm attaching the patch; it applies against the current trunk. Actually I'm not sure which of the two patches is cleaner. Or should I say "less unclean"? Well. Perhaps I should postpone this decision for the v0.7.1 release. Nikolaus File Added: archivemail-all-optim.diff ---------------------------------------------------------------------- Comment By: Christian (chrisbra) Date: 2007-11-03 13:55 Message: Logged In: YES user_id=1928606 Originator: NO Hi, sorry, I must have made a mistake when submitting the patch. But if it is true, that --archive-all will be the same as --days=0 and --include-flagged, then the following patch should achieve it (against 0.7.0): --- archivemail.orig 2007-11-03 13:36:10.000000000 +0100 +++ archivemail.all 2007-11-03 13:35:55.000000000 +0100 @@ -201,7 +201,7 @@ """ try: opts, args = getopt.getopt(args, '?D:S:Vd:hno:F:P:qs:uv', - ["date=", "days=", "delete", "dry-run", "help", + ["archive-all", "date=", "days=", "delete", "dry-run", "help", "include-flagged", "no-compress", "output-dir=", "filter-append=", "pwfile=", "dont-mangle", "archive-name=", @@ -213,6 +213,13 @@ archive_by = None for o, a in opts: + if o == '--archive-all': + if archive_by: + user_error("you cannot specify --archive-all and -d or -D options") + archive_by = "all" + self.archive_all = 1 + self.days_old_max = 0 + self.include_flagged = 1 if o == '--delete': self.delete_old_mail = 1 if o == '--include-flagged': @@ -223,12 +230,12 @@ self.warn_duplicates = 1 if o in ('-D', '--date'): if archive_by: - user_error("you cannot specify both -d and -D options") + user_error("you cannot specify --archive-all and -d or -D options") archive_by = "date" self.date_old_max = self.date_argument(a) if o in ('-d', '--days'): if archive_by: - user_error("you cannot specify both -d and -D options") + user_error("you cannot specify --archive-all and -d or -D options") archive_by = "days" self.days_old_max = string.atoi(a) if o in ('-o', '--output-dir'): @@ -647,6 +654,7 @@ mailbox compressed with gzip. Options are as follows: + --archive-all archive all messages -d, --days=NUM archive messages older than NUM days (default: %d) -D, --date=DATE archive messages older than DATE -o, --output-dir=DIR directory to store archives (default: same as original) regards, Christian ---------------------------------------------------------------------- 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: Nikolaus S. <mic...@we...> - 2007-11-05 20:27:20
|
Hi, the subversion import is now complete and the repo should be fully functional again. Thanks, Nikolaus |
|
From: Nikolaus S. <mic...@we...> - 2007-11-05 16:25:16
|
Hi, I am importing the website into subversion. As I understand it, this requires to re-load the subversion repo from a dump; I will schedule this operation today. I don't know how this might interfere with commits to the repository, but we probably better be careful. By the way, I'm planning to release v0.7.1 very soon. Thanks, Nikolaus |
|
From: SourceForge.net <no...@so...> - 2007-11-03 12:55:16
|
Patches item #1764846, was opened at 2007-07-31 21:19 Message generated for change (Comment added) made by chrisbra 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: Christian (chrisbra) Date: 2007-11-03 13:55 Message: Logged In: YES user_id=1928606 Originator: NO Hi, sorry, I must have made a mistake when submitting the patch. But if it is true, that --archive-all will be the same as --days=0 and --include-flagged, then the following patch should achieve it (against 0.7.0): --- archivemail.orig 2007-11-03 13:36:10.000000000 +0100 +++ archivemail.all 2007-11-03 13:35:55.000000000 +0100 @@ -201,7 +201,7 @@ """ try: opts, args = getopt.getopt(args, '?D:S:Vd:hno:F:P:qs:uv', - ["date=", "days=", "delete", "dry-run", "help", + ["archive-all", "date=", "days=", "delete", "dry-run", "help", "include-flagged", "no-compress", "output-dir=", "filter-append=", "pwfile=", "dont-mangle", "archive-name=", @@ -213,6 +213,13 @@ archive_by = None for o, a in opts: + if o == '--archive-all': + if archive_by: + user_error("you cannot specify --archive-all and -d or -D options") + archive_by = "all" + self.archive_all = 1 + self.days_old_max = 0 + self.include_flagged = 1 if o == '--delete': self.delete_old_mail = 1 if o == '--include-flagged': @@ -223,12 +230,12 @@ self.warn_duplicates = 1 if o in ('-D', '--date'): if archive_by: - user_error("you cannot specify both -d and -D options") + user_error("you cannot specify --archive-all and -d or -D options") archive_by = "date" self.date_old_max = self.date_argument(a) if o in ('-d', '--days'): if archive_by: - user_error("you cannot specify both -d and -D options") + user_error("you cannot specify --archive-all and -d or -D options") archive_by = "days" self.days_old_max = string.atoi(a) if o in ('-o', '--output-dir'): @@ -647,6 +654,7 @@ mailbox compressed with gzip. Options are as follows: + --archive-all archive all messages -d, --days=NUM archive messages older than NUM days (default: %d) -D, --date=DATE archive messages older than DATE -o, --output-dir=DIR directory to store archives (default: same as original) regards, Christian ---------------------------------------------------------------------- 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-11-02 18:48:48
|
Bugs item #1762907, was opened at 2007-07-29 00:16 Message generated for change (Comment added) made by nikosch 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: Closed >Resolution: Fixed >Priority: 3 Private: No Submitted By: helloworld.c (helloworld_c) >Assigned to: Nikolaus Schulz (nikosch) 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: Nikolaus Schulz (nikosch) Date: 2007-11-02 19:48 Message: Logged In: YES user_id=1594781 Originator: NO Fixed in subversion. Will go into 0.7.1. ---------------------------------------------------------------------- Comment By: helloworld.c (helloworld_c) Date: 2007-07-30 00: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-11-02 18:10:55
|
Patches item #988803, was opened at 2004-07-11 09:59 Message generated for change (Comment added) made by nikosch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=456912&aid=988803&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: Nowicki Christophe (cscmeu) >Assigned to: Nikolaus Schulz (nikosch) Summary: --keep option as requested in bug #981865 Initial Comment: Hi, I've requested a small feature : keep mail on the imap server in my bug repport #981865 : http://sourceforge.net/tracker/index.php?func=detail&aid=981865&group_id=49630&atid=456910 I've wrote it my self ;) Thanks ---------------------------------------------------------------------- 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=988803&group_id=49630 |
1 message has been excluded from this view by a project administrator.
