zope, worldpilot, IMAP, POP...
I've been investigating how to do web-based email for zope users... it seemed like worldpilot was cool (BTW, where is it??) Then I was talking to a friend, who mentioned vaguely something about perl-script that implemented a yahoo or hotmail type system, and it solved the problem of username/password admin on the mail server, by avoiding it! Basically it took advantage of the 'dead letter' email account on a POP or IMAP server where all the bogus email goes, and it pulled it all in and parsed it against it's own list of users, etc. My question is, therefore, is it reasonable to try to do something like this in Zope, with the goal of using the Zope membership info (username & password) for defining the mail users? The only thing I find that's even close is POPMailProduct, but it's lacking the hard part... Marc
[marc lindahl] | I've been investigating how to do web-based email for zope users... it | seemed like worldpilot was cool (BTW, where is it??) http://www.zope.org/Members/morphex/ZopeGUM -- there's a mail / news agent located in that package. Cheers, Morten
This looks great, but it seems to assume pre-existing individual mail (POP or IMAP) accounts. I'm stuck on, how to create new email accounts when creating zope memberships, and keep the email accounts sync'd with the zope memberships (username and password).
http://www.zope.org/Members/morphex/ZopeGUM -- there's a mail / news agent located in that package.
Cheers,
Morten
[marc lindahl] | This looks great, but it seems to assume pre-existing individual mail (POP | or IMAP) accounts. I'm stuck on, how to create new email accounts when | creating zope memberships, and keep the email accounts sync'd with the zope | memberships (username and password). Well, I don't think it would be too much hassle to add some administrative functionality to keep them in sync (albeit, to be 100% percent sure will hurt a lot - I guess). I'm guessing that Morten is already working on this. On another note, I seem to recall seeing a ZMailIn product somewhere, which allows you to mail directly to a Zope instance. I don't know where I saw it, but if you searched for five minutes on Zope.org I'm almost sure you would find it :-). Anyway, that could probably rid you having to think about having files on the filesystem in sync with objects within Zope, don't know how GUM would talk with it, tough.
[Erik Enge] | Well, I don't think it would be too much hassle to add some | administrative functionality to keep them in sync (albeit, to be 100% | percent sure will hurt a lot - I guess). I'm guessing that Morten is | already working on this. Yup. The way that seems right is to proxy user-account creation through sudo (unix (linux?) only), thoughts / comments ? I'll post a script within a week or two. Cheers, Morten
[Morten W. Petersen] | Yup. The way that seems right is to proxy user-account creation through | sudo (unix (linux?) only), thoughts / comments ? Well, that probably depends on how you figure the administrator to work. I think I would've tried to abstract the whole notion about «something under the hood» away from the administrator, and tried to be clever when I added and delete users within Zope (that is, the code being clever, not me). I don't know. You'll probably come up with something, as always :)
That's why I thought it was a cool idea to use the 'catchall' or dead.letter account - there's no security problems or administration problems. Instead, the 'pain' is managing that stuff inside zope, including parsing through one big mailbox to 'divvy up' the mail - probably by some cron job every few minutes.
From: Erik Enge <erik+list@esol.no>
[Morten W. Petersen]
| Yup. The way that seems right is to proxy user-account creation through | sudo (unix (linux?) only), thoughts / comments ?
Well, that probably depends on how you figure the administrator to work. I think I would've tried to abstract the whole notion about «something under the hood» away from the administrator, and tried to be clever when I added and delete users within Zope (that is, the code being clever, not me).
[marc lindahl] | That's why I thought it was a cool idea to use the 'catchall' or dead.letter | account - there's no security problems or administration problems. Instead, | the 'pain' is managing that stuff inside zope, including parsing through one | big mailbox to 'divvy up' the mail - probably by some cron job every few | minutes. If you're thinking of not using mail accounts at all, that will probably be enabled (it's already some basic code there that reads /var/spool/mail/<username>) somewhere in the near future. As always, suggestions / wishlist / comments are welcome. Cheers, Morten
...except that assumes the mail server on the same box. Going thru dead.letter means it can be anywhere... the cron script or whatever gets the bulk mail has the username/password for that one account. Make sense?
From: morten@esol.no (Morten W. Petersen)
If you're thinking of not using mail accounts at all, that will probably be enabled (it's already some basic code there that reads /var/spool/mail/<username>) somewhere in the near future. As always, suggestions / wishlist / comments are welcome.
[marc lindahl] | ...except that assumes the mail server on the same box. Going thru | dead.letter means it can be anywhere... the cron script or whatever gets the | bulk mail has the username/password for that one account. Make sense? Ah, I think I know what you mean.. Do you 1) Want to be able to retrieve messages to the local box, from for example your ISP. 2) Want to be able to use an external host with mail account only 3) Same as 1, but retrieve the messages and store them in an arbitrary file I.e. 1) Have a local mail account, but retrieve from external mailhosts into it 2) Use *only* an external mail account as the source for mail, without intermittenly storing it at the local box 3) Make use of a pseudo spool file, located in ~/mbox, ~/misc/work-mail, etc. The first suggestion is supported, by using fetchmail and a python interface, but it isn't easily available in the interface (IIRC). The second is also supported, but the differantion in the interface isn't very clear, you may have to use <path-to-mail-instance>/base_edit. The third is partially supported, but interfaces and options that make it accessible will have to be built. Am I making any sense? =) Cheers, Morten
From: morten@esol.no (Morten W. Petersen)
1) Want to be able to retrieve messages to the local box, from for example your ISP.
It probably wouldn't be your ISP, unless you had a virtual domain. Because, you'd use the catchall account: http://lists.omnipotent.net/qmail/200006/msg00338.html http://www.qmail.org/qmail-manual-html/man8/qmail-send.html
3) Same as 1, but retrieve the messages and store them in an arbitrary file
Yeah, something like that but parsing thru the catchall account to distribute mail to the 'within zope users'. There seems to be a way to forward a whole catchall account (http://binarios.com/miscnotes/qmail.html), but can zope recieve it? If so, then it's just a of parsing the messages and managing the users.... Marc
I currently have a "parked" domain with DomainDirect (TUCOWS). They supply one POP mail box that can be set up, and mine is, as a catch-all. In addition I can have up to 5 additional forwards of addresses in the domain. Though I only use one address right now, I definatly see some value in have the zope solution capable of grabbing the contents of the POP mail box and then sorting it based on addressee. Jack On Thursday 21 December 2000 16:45, marc lindahl wrote:
From: morten@esol.no (Morten W. Petersen)
1) Want to be able to retrieve messages to the local box, from for example your ISP.
It probably wouldn't be your ISP, unless you had a virtual domain. Because, you'd use the catchall account: http://lists.omnipotent.net/qmail/200006/msg00338.html http://www.qmail.org/qmail-manual-html/man8/qmail-send.html
3) Same as 1, but retrieve the messages and store them in an arbitrary file
Yeah, something like that but parsing thru the catchall account to distribute mail to the 'within zope users'.
There seems to be a way to forward a whole catchall account (http://binarios.com/miscnotes/qmail.html), but can zope recieve it? If so, then it's just a of parsing the messages and managing the users....
Marc
_______________________________________________ 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 )
[Jack Ungerleider] | I currently have a "parked" domain with DomainDirect (TUCOWS). They supply | one POP mail box that can be set up, and mine is, as a catch-all. In addition | I can have up to 5 additional forwards of addresses in the domain. Though I | only use one address right now, I definatly see some value in have the zope | solution capable of grabbing the contents of the POP mail box and then | sorting it based on addressee. I do as well. I think this will be included, very soon. =) Cheers, Morten
[Erik Enge] | Well, that probably depends on how you figure the administrator to | work. I think I would've tried to abstract the whole notion about | «something under the hood» away from the administrator, and tried to | be clever when I added and delete users within Zope (that is, the code | being clever, not me). That was what I was thinking of. We set up sudo to with a permission to user nobody, which gets the right to use a script (under-the-hood) called something like create-account-if-not-already-there and remove-account-if-there-and-created-by-zope (yes, the names are for illustrative purposes. =) Cheers, Morten
participants (4)
-
Erik Enge -
Jack Ungerleider -
marc lindahl -
morten＠esol.no