S Shah wrote:
Sorry, something I am not clear about in regards to mailing lists...
--- Paul Everitt <paul@digicool.com> wrote:
1) Push the emails into Zope. Subscribe an account to the list. When a 2) Pull the emails into Zope. Subscribe an account to the list and make
I am afraid I do not understand which account is reffered to in the phrase "subscribe an account to the list".
No you create a separate e-mail account or alias for subscribing to the Zope list. This happens on your e-mail server linux box. This doesn't actually need to be an OS level account, just a sendmail alias ( it doesn't alias anything, "alias" is what you call a "pseudo-account" - it has an e-mail address but no OS level account ). Set up the sendmail alias to pipe the mail to a script. See Sendmail docs or O'Reilly book or even Mailman docs to see how an alias is set up. When the mail arrives it is piped to a script which invokes Zope methods via HTTP or Python and uploads the mail message to a previously created mail-database. You need to write the script, create the db etc. Hope this helps. Nitin Borwankar.
Does the Zope installation have some internal email account object? I know I am missing some key fact here. (Our mail is handled by a linux box). If I set up an alias, and subscribe the alias to the mailing list, WHO/WHAT am I aliasing? I am very confused...Option 1 sounds the most appealing, but I would appreciate any additional details anyone can provide. (full text of all Options at end of message)
Thanks for all your assistance...converting my student group's site to Zope is an incredible (albeit frustrating) learning experience.
--sachin shah
--- Paul Everitt <paul@digicool.com> wrote:
1) Push the emails into Zope. Subscribe an account to the list. When a mail message comes in, get the alias to run a program that loads the email into Zope (e.g. ZClient, xml-rpc, WebDAV, etc.) Advantages: the archive is always up to date. Disadvantage: somewhat intrusive on the system.
2) Pull the emails into Zope. Subscribe an account to the list and make it available on a POP or IMAP server. Write some Python (e.g. as an External Method) that pulls the data into Zope. Advantages: can archive any mailbox accessible by POP or IMAP, chance of dropping data reduced. Disadvantages: still need to write something (e.g. a cron job or sleeper thread) that notifies Zope to do the work.
3) Keep the data out of Zope. The "NotMail" unsupported product doesn't keep message data in Zope. Rather, it leaves it on the IMAP server. Searches are done using the IMAP server's search facility. Advantages: mostly simple. Disadvantages: throws out much of Zope's capability, slow IMAP performance (and load).
__________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope No cross posts or HTML encoding! (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )