#15793: Filebased email backend should save emails using the ".eml" standard
extension
-------------------------------------+-------------------------------------
Reporter: Kronuz | Owner: nobody
Type: | Status: new
Cleanup/optimization | Component: Core (Mail)
Milestone: | Severity: Normal
Version: | Keywords:
Resolution: | Has patch: 1
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 1 | Easy pickings: 1
Patch needs improvement: 1 |
-------------------------------------+-------------------------------------
Comment (by aaugustin):
Upon further investigation, the files created by the filebased email
backend aren't really emails:
- `('-' * 79 + '\n') ` is appended after each email, even if there is only
one;
- several message will be written to the same file if they are sent with
one call to `send_messages()`.
While I understand and support the case for renaming these files as .eml —
it's only a debug tool, being able to double-click the files will save
time — I wonder if we should go further and use the mbox format
(http://docs.python.org/library/mailbox.html#mailbox.mbox), which is the
standard container for dumping several email to the same file. That would
be more backwards incompatible, but at the same time much more useful. One
possibility is to create "mbox" backend and then deprecate the "filebased"
backend, but that seems overkill...
--
Ticket URL: <http://code.djangoproject.com/ticket/15793#comment:8>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
