OK, great that worked. Question though about the hosteddomains file: If all of our email is simply being passed through to the Exchange server for processing (except for the Mailman stuff) do we really need to have ANY domain(s) listed in the hosteddomains file?
Basically, as I see it, all we need is: hosteddomains - empty esmtprouted - one line with :[exchange.server.ip.addr] aliases/lists.foo.com - one line per list name that redirects the incoming email to Mailman. Is that correct? Mack King - Tech Support Guy -----Original Message----- From: Sam Varshavchik [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 26, 2003 5:44 PM To: [EMAIL PROTECTED] Subject: [courier-users] Re: Forwarding unknown address to another email server Technical Specialist writes: > Hi there all, > > Up untill recently, all of our incoming email had been being routed around > Courier (firewall rules) and directly to our MS Exchange mail server. We > have recently decided we want to add Mailman lists to our site and since > Courier was already installed on our webserver (RH 7.2 / Courier 0.40) we > figured we'd try to make it work with Courier. > > Here's what we want to do now: > - have all email coming into our network go through Courier first. > - if email is for a particular set of domains, just pass it through to > the Exchange server > - if email is for @lists.foo.com, have Courier handle it > - if the [EMAIL PROTECTED] account exists on the webserver (i.e. is a > configured Mailman mailing list) handle it (forward to Mailman) > - if the [EMAIL PROTECTED] account doesn't exist, pass the email through > to the Exchange server. > > I've got the esmtproutes file setup as follows: > lists.foo.com: > :[192.168.1.190] > > This sets it up so that any email we receive other then whats targeted for a > @lists.foo.com address gets passed though to the Exchange server just fine. > > I've created an entry in the aliases/lists.foo.com alias file that (for now) simply > redirects [EMAIL PROTECTED] -> [EMAIL PROTECTED] > > What I need now is to know how to setup an alias (or something in a dot-courier > file) that will take any email that has fallen through this far in the process > undelivered and will forward it to the Exchange server. The dot-courier man page enumerates environment variables that are available to .courier files, which can be used to forward mail to the same userid on another logical domain. A much better approach is NOT to define lists.foo.com as a local domain, thus letting all mail addressed to @lists.foo.com be forwarded; and then create aliases for all addresses that are to be delivered locally. ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
