|Lucio Crusca||Sep 27, 2011 10:39 am|
|Sam Varshavchik||Sep 27, 2011 2:49 pm|
|Lindsay Haisley||Sep 27, 2011 9:05 pm|
|Lucio Crusca||Sep 28, 2011 1:05 am|
|Sam Varshavchik||Sep 28, 2011 3:55 am|
|Lucio Crusca||Sep 28, 2011 5:05 am|
|Sam Varshavchik||Sep 28, 2011 5:30 am|
|Alessandro Vesely||Sep 28, 2011 8:34 am|
|Lucio Crusca||Sep 29, 2011 5:11 am|
|Lucio Crusca||Sep 29, 2011 5:31 am|
|Alessandro Vesely||Sep 29, 2011 11:13 am|
|Lucio Crusca||Oct 2, 2011 2:20 am|
|Alessandro Vesely||Oct 3, 2011 1:46 am|
|Lucio Crusca||Nov 11, 2011 9:55 am|
|Sam Varshavchik||Nov 11, 2011 4:38 pm|
|Alessandro Vesely||Nov 12, 2011 2:09 am|
|Lucio Crusca||Nov 15, 2011 9:18 am|
|Matus UHLAR - fantomas||Nov 15, 2011 11:34 am|
|Subject:||[courier-users] virtual mailboxes|
|From:||Lucio Crusca (luc...@sulweb.org)|
|Date:||Sep 27, 2011 10:39:11 am|
I'm new here but I've been using courier for 10 years. Mostly courier-imap, but a few years ago I've also used courier-mta. Then I moved to a mixed setup with Postfix+courier-imap+MySQL.
Now I have a new server to configure (Ubuntu 10.04 server) and I'm quite annoyed by the postfix mess and the sasl hell, not to mention the back and forth of messages between daemons only to apply spam filters, that kind of setup is too muddled for my taste. So I feel like going back to my origins and use courier-mta instead.
However when I used courier-mta back then I did not need virtual mailboxes (though I used them anyway with authuserdb) nor more than one domain; now things are different.
Here is what I need to do, please head me in the direction of the best setup (sql backend?). I don't need a detailed howto, I'm able to figure out most things with google, I only need some hint about the setup.
0. I am the sysadmin, my customer is the user of the system and related mailboxes. 1. users (a few identified people working @ my customer) MUST be able to create their own mailboxes through some sort of web interface, no shell access. It's ok if they are not able to create new domains, I can do that once for all. 2. users are all in charge for all the domains, so they MUST NOT be limited about what domains they can manage. 3. users MUST be able to reset passwords from the web interface, and MUST be able to change their password in the webmail 4. passwords MUST NOT be stored in plaintext 5. incoming mail MUST be filtered with common spam filters (sa, others?) and marked as spam/deleted based on spam rating received. 6. users must be able to mark messages as spam/ham (sa-learn), (maybe by moving those messages in a dedicated folder?) 7. some users share a common mailbox (info@....). They SHOULD see unread messages as unread, even when another user has already read that same messages from a different client, but if a user trashes a message, that message should go to trash for all other users too (I don't even know if this is possible, my customer says he's this feature right now in gmail, but I'd never heard about that before).
Thanks in advance for any hint. Lucio.
------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________ courier-users mailing list cour...@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users