aboutsummaryrefslogtreecommitdiffstats
path: root/test_archivemail
Commit message (Collapse)AuthorAgeFilesLines
* New option --archive-name, alias -a, to hard-code the archive filenameNikolaus Schulz2010-07-311-0/+28
|
* test suite: fix buggy test of --suffix and --prefix option parsingNikolaus Schulz2010-07-311-2/+2
|
* test suite: replace some plain assertions with TestCase.assertEqual()Nikolaus Schulz2010-07-311-4/+4
|
* Don't create hidden archives when archiving mailboxes with leading dots in ↵Nikolaus Schulz2010-07-311-0/+22
| | | | | | | | the name When archiving a mailbox with leading dots in the name and no archive name prefix specified, strip the dots off the archive name. This is targeting Maildir++ subfolders.
* Only use the default archive name suffix when the user specified no affixNikolaus Schulz2010-07-311-7/+32
| | | | Also add more archive name affix testing to the test suite.
* New option --archive-prefix, alias -pNikolaus Schulz2010-07-311-0/+34
| | | | | | | | | | | Technically, this works just like the --suffix option. This commit also updates the manpage accordingly. Currently, the prefix is not checked for slashes, so it could contain path components. (The same applies for the suffix, btw). Since the expanded string is prepended to the archive base name, this can be used to dynamically configure the archive directory, depending on the archive cutoff date. I'm not sure if this can be considered a reasonable feature, though.
* Detect and never archive IMAP server pseudo mbox messagesNikolaus Schulz2010-07-301-0/+22
| | | | | | | IMAP servers (Dovecot and UW-IMAP at least) may store mailbox meta data for mboxes in a pseudo message. Such messages are now detected and never archived. This commit includes a test case in the test suite.
* test suite: test unlocking an mbox after dotlocking failed with EACCESNikolaus Schulz2010-07-301-0/+1
|
* Rename archivemail.py to archivemailNikolaus Schulz2010-07-291-7/+7
| | | | | | | | | On Unix, most scripts don't come with a file extension, it's not needed, and we distribute the script as "archivemail" anyway. And most importantly, I like it better without the extension. :) With a little trick we can still load the script as a module from the test suite.
* Drop .py extension from the unittest scriptNikolaus Schulz2010-07-291-0/+1593