The MailAttachment.document field is too short & raises the error below. The default FileField(..., max_length=100) does not hold long enough filenames.
Can MailAttachment.document accept a configured max_length, or have the default set higher?
ERROR: [django.security.SuspiciousFileOperation: 204] Storage can not find an available filename Please make sure that the corresponding file field allows sufficient "max_length".
Squashed commit of the following:
commit f3a782d0b0
Author: Adam Coddington <me@adamcoddington.net>
Date: Sat Jan 30 22:32:51 2016 -0800
Django 1.7 does not support Python 3.5.
commit c100ccf867
Author: Adam Coddington <me@adamcoddington.net>
Date: Sat Jan 30 22:28:09 2016 -0800
Ensure that message_id is always stripped.
commit ee5a023da1
Author: Adam Coddington <me@adamcoddington.net>
Date: Sat Jan 30 22:24:27 2016 -0800
Modern python versions do not have --use-mirrors.
commit 54aa74d984
Author: Adam Coddington <me@adamcoddington.net>
Date: Sat Jan 30 22:19:59 2016 -0800
Turn off sudo mode for django-mailbox.
> Errors should never pass silently
I waste a hours to debug that . I don't expect this kind of behaviour. In my app proccess incoming mails is critical and I should receive exception and on fail transaction should rollback everything and try again later.
Squashed commit of the following:
commit 5bcbac33d6
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 7 23:05:15 2015 -0700
Add handling for situations in which the message was deleted in another thread before processing.
commit 6183f68b39
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 7 22:58:15 2015 -0700
Always store message as attachment if its content-disposition is marked as such.
commit 4c16494b1a
Author: Adam Coddington <me@adamcoddington.net>
Date: Tue Jul 7 22:46:52 2015 -0700
Adding a (hopefully) failing test case for #52.
* Using a query parameter argument (rather than the entire query string)
to specify the folder into which e-mail messages should be archived.
* Duplicating the IMAP tests; this could probably be a bit more simply
done, but we'll at least be verifying both archived and non-archived
use cases.
* Simplifying some aspects of the documentation to include references
to this new feature.
