On approximately 10/7/2009 7:37 PM, came the following characters from
the keyboard of Bill Janssen:
Barry Warsaw <ba...@python.org> wrote:
5. Mailing list archiver. Input will be bytes or message objects,
output will be strings (typically HTML documents or XML
fragments).
I use the email package to implement an email archiver, and I do bytes
in and bytes out. I do threading (using header instances), and process
attachments separately, which requires that they come out of the message
in their native format, whatever that is -- I treat it as bytes.
I also maintain a Python IMAP server which uses the email package to
construct messages, and then deconstructs them to send out in response
to IMAP requests.
Bill
OK, so there's another nice item for the use case list. Thanks Bill for
responding, I figured there had to be something like that out there.
That's why I was pushing back on Stephen's cases as making too
restrictive of assumptions... but now that I understand his purpose, it
is appropriate just to add the additional case.
--
Glenn -- http://nevcal.com/
===========================
A protocol is complete when there is nothing left to remove.
-- Stuart Cheshire, Apple Computer, regarding Zero Configuration Networking
_______________________________________________
Email-SIG mailing list
Email-SIG@python.org
Your options:
http://mail.python.org/mailman/options/email-sig/archive%40mail-archive.com
