Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 May 2000 16:07:45 -0400 (EDT)
From:      OCtane <zhaoc@escape.com>
To:        freebsd-questions@freebsd.org
Subject:   Sendmail is not recognizing hosts we MX for, even with the feature enabled?
Message-ID:  <Pine.BSI.4.21.0005131503300.23195-100000@escape.com>

next in thread | raw e-mail | index | archive | help
Hello, I'm running a stock 3.4-RELEASE mail server with built in sendmail
version 8.9.3.  /etc/sendmail.cf is the one that comes by default. We
provide virtual host service (no problems there), as well as secondary MX
for those clients who run their own dedicated mail server.

Name server set up is typical (here we are the isp, us.dom):
client.dom	IN	MX 10 mail.client.dom.
		IN	MX 20 mail.us.dom.

Sending straight to mail.client.dom works, and mail sent from us.dom to
them through mail.us.dom works since we are local.

Now here's the problem.  Mail sent to mail.us.dom with receipt to
user@client.dom from anywhere else will get bounced (If their server is
down, or telnetting to mail.us.dom 25, etc.)

From /var/log/maillog (slightly modified):
May 13 03:46:21 mail sendmail[5874]: YXS72024: ruleset=check_rcpt,
arg1=<user@client.dom>, relay=host.outside.dom
[xx.yy.zz.ww], reject=550 <user@client.dom>... Relaying denied

I've verified this by running sendmail -bt and running check_rcpt
manually with different .D{client_addr} and .D{client_name} settings.

I can work around this problem by explicitly setting client.dom in class
R, /etc/mail/relay-domains, thus making it local.  But what I don't
understand is why I have to do this when FreeBSD's sendmail configuration
has:
#####  @(#)relay_based_on_MX.m4 8.7 (Berkeley) 5/19/1998  #####

As I understand matters after hours of going through sendmail.org,
shouldn't this automatically check to see if mail.us.dom is a MX for
client.dom and accept the message?  Does anyone have any idea what I'm
missing or misunderstanding?  I have searched the sendmail faq/site, and
deja.com, but I can't find anything addressing this problem in relation to
having FEATURE(relay_based_on_MX) enabled.

Other lines which may relate to the matter, to show I have them...
Please let me know if someone needs the whole file, or other
information (but remember this file is unmodified).  Thanks for any
insight.

# MX map (to allow relaying to hosts that we MX for)
Kmxserved bestmx -z: -T<TEMP>

From the check_rcpt section (never did get around to reading the bat book,
so i'm pretty lost when it comes to the rule sets).
 
# allow relaying for hosts which we MX serve
R$+ < @ $* >            $: < : $(mxserved $2 $) : > $1 < @ $2 >
R< : $* <TEMP> : > $*   $#error $@ 4.7.1 $: "450 Can not check MX records
for recipient host " $1
R<$* : $=w . : $*> $*   $@ OK
R< : $* : > $*          $: $2

I guess this is where it falls apart, but with the MX lookups, this
shouldn't happen?

# anything else is bogus
R$*                     $#error $@ 5.7.1 $: "550 Relaying denied"



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.4.21.0005131503300.23195-100000>