Actually, it's not specifying the format of a configuration file. It's specifying the format of the DNS response. It just so happens that most DNS servers simply respond with what's in their configuration file, so it appears the same.
In this case, Courier is querying DNS and looking at the result. If the result breaks RFC1035 (which superceded 974) then it won't deliver. I don't remember the reasoning behind the 1035 spec, but I follow it. Best regards, ssh > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 25, 2003 6:26 PM > To: Steve Hultquist > Cc: [EMAIL PROTECTED] > Subject: Re: [courier-users] RFC 1035 unpleasantness > > What kinda cracked out RFC specifies the format of a configuration file!! > No wonder maintaining DNS is such a pain, the lame file format is actually > specified in the RFC! > Anyways MX records point to A records & are not IP addresses & as a > 'special > case' in RFC 974 MX records can also be CNAMEs... > thanks, > Mark > > On Tue, Nov 25, 2003 at 05:47:43PM -0700, Steve Hultquist wrote: > > Mark, > > > > Did you look at RFC 1035? The error is with the way the MX is set up. > The MX > > needs to have an IP address, not point to a CNAME or A record. > > > > Best regards, > > ssh > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:courier-users- > > > [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > > > Sent: Tuesday, November 25, 2003 4:56 PM > > > To: [EMAIL PROTECTED] > > > Subject: [courier-users] RFC 1035 unpleasantness > > > > > > Howdy, > > > Whenever I try to send an email thru courier-esmtpd via Outlook > > > Express > > > (& maybe other mail clients) esmtpd denies it with: > > > > > > Nov 25 10:25:56 [courieresmtpd] > > > error,relay=xx.xx.xx.xx,from=<[EMAIL PROTECTED]>: 517-Domain does not > exist: > > > xxxxxx.com. > > > Nov 25 10:25:56 [courieresmtpd] > > > error,relay=xx.xx.xx.xx,from=<[EMAIL PROTECTED]>: 517 Invalid domain, see > > > <URL:ftp://ftp.isi.edu/in-notes/rfc1035.txt> > > > > > > Which is very bizzarro for several reasons: > > > > > > - That domain it's complaining about is hosted by the same machine > courier > > > esmptd is running on > > > - The domain is listed in /etc/hosts > > > - The domain's primary DNS server resides on the same machine as > > > courier esmtpd is running on > > > - The DNS severs listed in /etc/resolv.conf can resolve that domain > name > > > no > > > problem > > > - That domain is listed in both esmtpdacceptmailfor and hosteddomains > > > - Other domains hosted by the same machine work fine > > > - Sending email from this account via locally installed squirrelmail > works > > > > > > Where the monkey else does this domain need to exist for courier > esmtpd > > > to allow it??????????????? > > > I am requiring remote IMAP users to authenticate w/esmtpd to relay > their > > > email, > > > which I don't think matters. > > > Thanks!!! > > > Mark > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: SF.net Giveback Program. > > > Does SourceForge.net help you be more productive? Does it > > > help you create better code? SHARE THE LOVE, and help us help > > > YOU! Click Here: http://sourceforge.net/donate/ > > > _______________________________________________ > > > courier-users mailing list > > > [EMAIL PROTECTED] > > > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier- > users > > ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
