aboutsummaryrefslogtreecommitdiffstats
path: root/FAQ
blob: a2e5648551691b0efce7cfbf0372ef65404f2d7e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
1. Why doesn't archivemail support bzip2 compression in addition to gzip?
-------------------------------------------------------------------------

I am quite happy to add bzip2 support to archivemail as soon as a 'bzip2'
module (similar to the gzip module) is available for python.  
[ Hint hint ;) ]


2. Can you add a switch to archive mailboxes greater than a certain size?
-------------------------------------------------------------------------

If you are using mbox format mailboxes instead, use the find(1) command instead, it is more flexible:

    find $HOME/Mail -type f ! -name '*archive*' 
rchiving? Otherwise we just drop the archive in in the current working directory. Switch to fcntl(2) locking? That would be NFS-safe. Perhaps make the locking method configurable? Check all items below, which are from the original author. :-) .archivemailrc support Specify an option to not seteuid() when run as root? When you get a file-not-found in the 6th mailbox of 10, it aborts the whole run. Better to fail gracefully and keep going. Think about the best way to specify the names of archives created with possibly an --archive-name option. Add more tests (see top of test_archivemail.py) We need some better checking to see if we are really looking at a valid mbox-format mailbox. Lock any original .gz files - is this necessary? Check for symlink attacks for tempfiles (although we don't use /var/tmp) Add an option to not cut threads. Add MMDF mailbox support Add Babyl mailbox support Add option to archive depending on mailbox size threshold - is this a good idea? Add option to archive depending on number of messages - is this a good idea?