Date: Mon, 25 Feb 2002 22:47:54 -0800 From: "Crist J. Clark" <cjc@FreeBSD.ORG> To: Terry Lambert <tlambert2@mindspring.com> Cc: "Matthew D. Fuller" <fullermd@over-yonder.net>, "Jeremy C. Reed" <reed@reedmedia.net>, FreeBSD Chat <chat@FreeBSD.ORG> Subject: Re: blocked mail Message-ID: <20020225224754.G52727@blossom.cjclark.org> In-Reply-To: <3C7AEC08.223E422C@mindspring.com>; from tlambert2@mindspring.com on Mon, Feb 25, 2002 at 05:59:36PM -0800 References: <Pine.LNX.4.43.0202251413410.25937-100000@pilchuck.reedmedia.net> <3C7AC400.B8F3E9FC@mindspring.com> <20020225174520.L47910@over-yonder.net> <3C7AEC08.223E422C@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 25, 2002 at 05:59:36PM -0800, Terry Lambert wrote:
> "Matthew D. Fuller" wrote:
> > Terry Lambert, and lo! it spake thus:
> > >
> > > In addition, the MX requirement is often that the sending
> > > host be in the MX list for the "MAIL FROM <user@domain>"
> > > domain part, or the mail will be refused as a suspicious
> > > relay.
> >
> > That can't be right. Incoming MX servers, and outgoing sendmail servers,
> > are often different.
>
> Nevertheless, it's a common rule, and it used to be the
> default (it's called relay for MX) until the latest
> sendmail import; did you read Greg Shapiro's announcement
> on the changes?
Pretty sure relay_based_on_MX has nothing to do with the sender, the
MAIL FROM. It checks the _recipient's,_ the RCPT TO, domain's MX
points to itself. There is no conflict if outgoing and incoming (which
is the one MX records point at) are not the same.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020225224754.G52727>