11 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: locals .domai...
FromSent OnAttachments
Chris MeadorsJan 10, 2001 11:18 am 
Sam VarshavchikJan 10, 2001 2:26 pm 
Chris MeadorsJan 12, 2001 10:39 am 
Chris MeadorsJan 15, 2001 6:12 am 
Tomas FasthJan 15, 2001 7:24 am 
Chris MeadorsJan 15, 2001 8:01 am 
Chris MeadorsJan 15, 2001 8:47 am 
Lindsay HaisleyJan 15, 2001 9:11 am 
Brian CandlerJan 15, 2001 9:33 am 
Chris MeadorsJan 15, 2001 9:49 am 
Chris MeadorsJan 15, 2001 10:08 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Re: locals .domain except 1 hostActions...
From:Chris Meadors (cour@clubneon.com)
Date:Jan 15, 2001 6:12:53 am
List:net.sourceforge.lists.courier-users

On Fri, 12 Jan 2001, Sam Varshavchik wrote:

There must be an underlying reason for this exception. Let's focus on the root cause of this. There's probably a better way to do what you're trying to do.

Basicly I run the ISP part of this company. We have 1 mail server for our domain, and some mispellings of it. I want all mail sent to any host in our domain to be picked up by this mail server (will be putting a wildcard MX in place soon too).

But there is 1 exception. We have a seperate machine that belongs to the paging service also run by this company. There are a few accounts on this machine. When e-mail is directed at an account on this machine it sends the page out the serial port to the paging terminal. From outside of our SMTP server everything works fine (even with the wildcard MX in place, named knows that "epage" is defined and doesn't try to replace it with the catch all).

I saw the esmtproutes config file. That seemed like what I needed, just to specify a special rule for this 1 host. But I seems that the locals file is considered before esmtproutes.

-Chris