In our conversations, the overall goal was to have a stand-alone mail server running Ubuntu and whatever mail packages are installed in [as close to default as possible] configuration. The server should remain isolated and not be connected to any other box or resource. We would call into it programmatically for all administrative functions. Since we are a Microsoft shop, there is an overwhelming concern (read "fear") that we will be less qualified to maintain the platform as we add other services to the mix... in essence, we need to keep the overall mail platform as simplistic as possible to increase the chance that our folks can maintain it with ease. Unless an LDAP server was an absolute requirement for Postfix we could not look at it. And, more than likely, if it was a requirement, we would probably look to a different product.
Early on in this project we were given a requirement to allow our members the ability to receive "messages" from our server via IMAP. Someone assumed writing an IMAP server service would be simple and that we would have the cycles to do so. Over time we have discouraged this and tried to find another IMAP service that will be able to marshal and deliver our messages to the client. This was unsuccessful. Postfix, and a simple server like Ubuntu, seems like the easiest method for dropping in a box that can receive messages and allow a standard email client to pull them down. Ultimately, it would be great to find an IMAP Server Service to negotiate the client calls act as a proxy to our application. Until then, Postfix appears to be the path we are on. I hope this helps. - G. Deward On May 21, 2013, at 2:32 PM, Serge Fonville <serge.fonvi...@gmail.com> wrote: > Ah, ok. > > Well you can run OpenLDAP (for example) as a backend in the same way you > could use AD. > > Postfix can use multiple backends depending on your needs. > > What requirements do you have? > > > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > Convince Microsoft! > They need to add TRUNCATE PARTITION in SQL Server > https://connect.microsoft.com/SQLServer/feedback/details/417926/truncate-partition-of-partitioned-table > > > 2013/5/21 Greg Deward <greg.dew...@gmail.com> > Sorry... should have specified... cannot integrate with AD or the Microsoft > environment. This needs to remain entirely stand-alone. 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. > > - G. Deward > > > > On May 21, 2013, at 2:18 PM, Serge Fonville <serge.fonvi...@gmail.com> wrote: > >> Hi, >> >> From your mail it seems you desire a backend that can handle all that, you >> should be able to setup postfix to retrieve its users from AD. >> >> HTH >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> Convince Microsoft! >> They need to add TRUNCATE PARTITION in SQL Server >> https://connect.microsoft.com/SQLServer/feedback/details/417926/truncate-partition-of-partitioned-table >> >> >> 2013/5/21 Greg Deward <greg.dew...@gmail.com> >> NEWBIE WARNING: I have never used Postfix and am not a Linux guru. Please >> be gentile. >> >> Is there an existing .NET library (DLL, etc.) for controlling Postfix? If >> not, is there an existing API for applications that are NOT running on the >> same server as Postfix? More specifically, I have a need for creating >> users, deleting users, changing passwords, and the like. I have been tasked >> with implementing an Ubuntu mail server and tying it into our custom ERP >> application (written in ASP.NET MVC and running on Windows). The goal is to >> be able to dynamically create user accounts, leverage them for a period of >> time, and then shut them down when a project is finished. >> >> Thank you, in advance, for any assistance you may provide. >> >> - G. Deward >> > >
