[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
[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
[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
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
[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
|
[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 -
...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: [EMAIL PROTECTED] (Morten W. Petersen)
If you're thinking of not using
[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)
From: [EMAIL PROTECTED] (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:
For managing a "catchall" account, also called a drop box, check out the excellent
program getmail at:
http://www.qcc.sk.ca/~charlesc/software/getmail-2.0/getmail.html
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED] (Morten W. Petersen)
1) Want to be
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
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
12 matches
Mail list logo