5 messages in net.sourceforge.lists.courier-usersRE: [courier-users] "Smart" relay not...
FromSent OnAttachments
Randall ShawAug 6, 2002 1:42 am 
Patrick O'ReillyAug 6, 2002 3:00 am 
Randall ShawAug 6, 2002 7:53 am 
Bowie BaileyAug 6, 2002 8:56 am 
Randall ShawAug 6, 2002 9:16 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] "Smart" relay not actually smart?Actions...
From:Bowie Bailey (Bowi@BUC.com)
Date:Aug 6, 2002 8:56:42 am
List:net.sourceforge.lists.courier-users

-----Original Message----- From: Randall Shaw [SMTP:cour@thewebchoice.com] Sent: Tuesday, August 06, 2002 10:54 AM Cc: courier Subject: Re: [courier-users] "Smart" relay not actually smart?

One way I found to stop it (not sure if this is right, as it means more configuration headaches), but if for EACH new domain that is hosted on the machine, I have to add that domain to: esmtpacceptmailfor (new file in dir, or append to current file) hosteddomains (new file in dir, or append to current file) esmtproutes (append to TOP of file as "newdomain.com:" with the colon)

That seems to tell it to deliver those domains to their proper MX location (which ends up being the same machine).

It sounds like the hosteddomains file is not set up properly. Did you run makehosteddomains after editing it?

As I understand it, any domain listed in hosteddomains should bypass esmtproutes and be delivered locally. I have a similar configuration here with only a default smart relay host defined in esmtproutes and everything works perfectly.

It's also possible that it may also have something to do with your local delivery agent. My system is set up for Courier to deliver directly to the maildirs.

This is messy, and I cant believe this is how it should be ... so I may be wrong as well on this! LOL!

Bowie