Incoming mail goes through a normal SMTP server, and you define an alias or forwarding rule, which then delivers the mail to the mailman service (calling a hook process on the same machine the mail arrived at)
You would need that rule for every list address you have defined. So, if you had a list for doctors, and one for patients, you would have to configure "[email protected]" and "[email protected]" on the Exchange server and have them both relay to the mailman box, where it's MTA would pick it up. On the mailman box, you configure the MTA to define "doctors" and "patients" aliases to call mailman hooks. Outgoing mail can be sent straight out from mailman, allowing that the mailman machine (probably running sendmail or postfix) has outbound port 25 privileges to the world at large. If it doesn't, you can configure sendmail or postfix to have a "relay", which would be your exchange server, which should be configured to just relay anything coming from your mailman host. I'm wondering if the version of Exchange on your server doesn't have a list management system built-in? It probably wouldn't have a web-based subscription panel, so would require more sysadmin work on the part of the Exchange administrator, but those guys usually have tons of time on their hands... :) Joel Brauer wrote: > Our email server here uses Exchange. If I set up a list at > [email protected], then the list serve has to be able to work with > exchange to access that info and process it. Understand, I haven't read > how that is set up. Does the Mailman server act as an MTA to receive > mail? Or does it pull it from another system?
