> > On Fri, Dec 13, 2002 at 09:18:25AM +0000, Jason Flatt wrote: > > > Recently I've > > > had an odd situation and I'm not sure how to get around it. I'm getting > > > the 513 Relaying denied error for one particular domain. I suspect that > > > I'm getting it because the DNS is setup to point to one address for the > > > main domain and to a different address for the mail.* part. Is there > > > someway I can get my server to accept mail for this domain w/o > > > compromising the server? > > > > What is the domain in question? > > > > Should be very easy to diagnose. > > > > Anyone trying to send mail to '[EMAIL PROTECTED]' follows these rules: > > 1. look up MX records for 'foo.com'. If any are found, deliver to those > > machines (trying the lowest-preference value MX record first) > > 2. if no MX records are found, look for an A record for 'foo.com' > > 3. if no MX or A records are found, bounce the mail > > > > Sounds to me like the MX records for the domain are pointing at the wrong > > server(s). > > Well, it may be a moot point as they have decided to just go with Network > Solutions for everything, but I am still curious why Courier was bouncing > apparently valid e-mails.
Well, if you point MX records for foo.com to machine mail.foo.com (or any other host), and that host is not configured to accept mail to [EMAIL PROTECTED] as a local domain, then it will think you are trying to relay through it. Sorry I don't know what configuration file you need to set in Courier to handle this (I only use the pop3/imap and sqwebmail components). In exim it would be "local_domains". Note that it is "foo.com" which has to appear in that configuration, not "mail.foo.com" (unless you want people to send mail to "[EMAIL PROTECTED]") > There is only one MX record, and it reads like this: > IN MX 10 mail.domainname.com. > > Then the A records read like this: > domainname.com. IN A 123.123.123.123 > www.domainname.com. IN A 123.123.123.123 > ftp.domainname.com. IN A 123.123.123.123 > mail.domainname.com. IN A 111.111.111.111 So then if machine 111.111.111.111 gives a "relaying denied" error then it is not configured correctly to receive mail for [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
