Sam,
If the domain is listed only in "esmtpacceptmailfor", then courier acts as a relay for that domain--it accepts the e-mail, then looks up the MX record for that domain and sends it there.
If you want the mail for the domain to be delivered locally, you have to put the domain in "locals" as well. If the domain is virtual then the domain should be in "hosteddomains" instead of "locals".
This is explained in detail in the courier man-page.
William
Samuel Penn wrote:
Currently, Courier is getting my mail from some POP3 accounts via fetchmail. These deliver to the Courier ESMTP server which accepts them fine.
I've recently tried setting things up to accept mail directly via SMTP for a different domain. The mail reaches my server, then is bounced back to my ISP (which redelivers and is bounced, repeat a few times before something detects an infinite loop).
My understanding is that Courier should accept mail for domains listed in "esmtpacceptmailfor". This file contains all the domains I want to accept, and I have run the "makeacceptmailfor" program to update the .dat file.
Is there anything else I need to configure? The MX record for the new domain doesn't point to this machine (a feature of my ADSL setup which I can't change). Does courier still look at the MX record even if it's been told to accept mail for this domain?
Thanks for any help.
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
