#22 crashes on zero-size mbox folder.

closed-invalid
None
5
2008-01-21
2007-07-13
Jonathan Ciesla
No

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.

Discussion

  • 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

     
    • assigned_to: nobody --> nikosch
     
  • 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.

     
  • 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.

     
  • Logged In: YES
    user_id=1594781
    Originator: NO

    This doesn't look like an archivemail bug. Jonathan, you've got a last chance to pick it up, otherwise the BTS bot will close this tracker in the next days. :-)

     
    • status: open --> pending-invalid
     
  • Logged In: YES
    user_id=791236
    Originator: YES

    Nah, I'll close it. Thanks. :)

     
    • status: pending-invalid --> closed-invalid