Lucio Crusca writes:
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 createtheir 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.
What do you mean by a mailbox. If you mean a mail folder, they can use any IMAP client, of course, or sqwebmail.
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
Passwords can be changed via webmail, with some additional setup. They can be stored encrypted, however you must realize that fundamental laws of this universe will not allow you to use hash-based authentication via IMAP when encrypted passwords are used. The server must have password in plain text, in order to be able to recalculate the hashes.
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?)
Or, set a custom keyword with any IMAP client that supports IMAP keywords.
7. some users share a common mailbox (info@....). They SHOULD see unreadmessages as unread, even when another user has already read that same messages
Although that's possible when using filesystem permission-based shared folders, filesystem permission-based shared folders are require system accounts to be used, and are severaly feature-limited.
Virtual accounts and virtual shared folders are better, but with virtual shared folders all message metadata is shared. Everyone sees the same status of each message, subject to natural caching in IMAP or webmail-based views, of course.
from a different client, but if a user trashes a message, that message shouldgo to trash for all other users too (I don't even know if this is possible, mycustomer says he's this feature right now in gmail, but I'd never heard about that before).
That's what you'll have with virtual shared folders.What you won't have with Courier is all the account provisioning functionality. Courier has no account provisioning functionality. Rather, it's configurable to pull account metadata from alternative options, starting with /etc/password, and ending at a replicated LDAP server; however how the accounts are provisioned and new mailboxes get created are out of scope, with the only limited exceptions of the password change functionality in sqwebmail, which is possible with most authentication configurations. Everything else is pretty much there, when you choose to use virtual accounts.
pgpZ0YeghcqfE.pgp
Description: PGP signature
------------------------------------------------------------------------------ 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 [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
