On 5/21/2013 1:28 PM, Greg Deward wrote: > Sorry... should have specified... cannot integrate with AD or the Microsoft > environment.
It's a bit ironic that you're summarily eliminating the one interface you already know very well, which would work perfectly for you. I'd guess this is due to... > This needs to remain entirely stand-alone. Fear. You fear the unknown system you have zero experience with, so you desire to completely isolate it from anything else. This is a mistake. Face your fear and let it pass through you. Postfix never modifies LDAP/AD/mysql data. As others have mentioned that is not its job. It simply queries for user and domain names, possibly credentials if you're allowing submission, other table data, etc. Given that you're an all Microsoft shop, implementing a *nix mail server without using LDAP/AD queries for user info is akin to hog tiring yourself. > This means our member base will be stored in the application's database and > we will need to call out to Postfix to manually perform account provisioning > and the like. Again as others noted, Postfix doesn't perform user management. It doesn't create nor delete user accounts. You can perform these functions blindfolded using AD can you not? Then use it. And if you actually intend to have users "pull" this email as you described, instead of delivering it to their existing mailboxes, then you need a mailbox/IMAP/POP server, as others mentioned. To make this much easier and avoid running a mailbox/IMAP/POP server, simply deliver these emails to users' existing mailboxes, wherever those may be: freemail, ISP, internal corporate, etc. If you do this, all you need is your MS hosted AD database and Postfix. Your description of the workload requirements is somewhat vague so keep that in mind when reading replies. -- Stan
