Zope acts as a publishing medium between documents that can be rendered on the server side and clients. So far there is http, ftp, webdav etc as protocols for this interaction. How about mail? I send a mail. It gets mapped to a zope object somehow. This object gets rendered and sent back. Zope could support smtp or it could use pop polling. Using it as a list server it would probably inefficient but for processing email forms etc it would be very cool.
"Jay, Dylan" wrote:
Zope acts as a publishing medium between documents that can be rendered on the server side and clients. So far there is http, ftp, webdav etc as protocols for this interaction. How about mail? I send a mail. It gets mapped to a zope object somehow.
I guess you could put something like "| add_may_mail_to_right_zope_folder" into your .forward file and then have a simple (?) program that submits the incoming mail to zope. It can either un-mime the mail itself or submit it as one big chunk and have zope external methods do the work of splitting the parts, decoding and saving with appropriate mime type
This object gets rendered and sent back.
To send something back is easy - just use MailHost.
Zope could support smtp or it could use pop polling.
Supporting SMTP directly is probably a bad idea for current (1.10.x) unthreaded servers as mail could be arraiving real slow. The technique described above is the equivalent of using apache with (p)cgi.
Using it as a list server it would probably inefficient but for processing email forms etc it would be very cool.
With ZCatalog it would also make a nice searchable mail storage. ----- Hannu
participants (2)
-
Hannu Krosing -
Jay, Dylan