On Sat, 2008-05-24 at 00:29 +0100, Bastien Nocera wrote:
On Fri, 2008-05-23 at 09:06 -0400, Matthias Clasen wrote:
<snip> > > At least for some SMBs (those who don't trust Google/Yahoo/... with > > their mails), a user mgmt tool should at some point (by way of a plugin > > or else) do exactly that, e.g. log into the company's cyrus-imapd and > > create a mailbox for the user. Maybe that's better suited for the > > enterprisey kind of user mgmt tool, however. > > In fact, an earlier draft of the design had the idea of plugins for this > kind of setup tasks. Maybe we'll have to revisit it. > For the client-side email setup, I guess you could get 90% of the way > there sabayon - just give the user a sabayon profile that has all the > mail configuration set up except for the email address, that evolution > can then pick up from the user service...
I'm not sure we should be having e-mail addresses, or even e-mail setup in the system (unless it was possible to do for sysadmins as a Python plugin, or something).
That's roughly what I meant -- this would really only have a tangible benefit in multi user situations with homogenous email settings, e.g. a company where most users will have mail addresses that can be generated programatically ("username@domain.tld", "firstname.surname@domain.tld", ...), with known POP/IMAP/SMTP servers. Granted, "multi" may be as low as "2", for instance home user systems where you have one computer buff in the family who administrates the system.
Nils