ruleset=check_mail..Sender domain must resolve

ruleset=check_mail..Sender domain must resolve

Post by Douglas Denaul » Sat, 14 Oct 2000 04:00:00



I had a transient problem with Sendmail 8.9.3

For several hours from 10/9/00 11:00 EDT - 10/10/00 08:00 EDT I got
messages of the form:

Oct  9 11:03:40 harbor sendmail[23065]: LAA23065: ruleset=check_mail,


Both before and after this interval they are able to relay. During the
time frame I was getting the errors, I was able to do both forward and
reverse lookups on the domain in the message. No other users seemed be
effected

I did this using as DNS servers: harbor (the mail relay in question); a
mail server at cmu.edu, and one of the authoritative name server for
popsite.net.

So my questions are: (a) is this error triggered by something in the
envelope that does not appear in the message; (b) can anything besides
DNS trigger this; (c) any ideas?

Thanks for any help

 
 
 

ruleset=check_mail..Sender domain must resolve

Post by Claus Assman » Tue, 17 Oct 2000 04:00:00



> I had a transient problem with Sendmail 8.9.3

Which OS?


> So my questions are: (a) is this error triggered by something in the
> envelope that does not appear in the message; (b) can anything besides
> DNS trigger this; (c) any ideas?

(a) No.
(b) Depends on your service switch file.
(c) Depends on your OS; we got a report that Solaris 2.x may cause
problems if nsswitch.conf has a certain format.

--
If you feel the urgent wish to send me a courtesy copy of a Usenet
posting, then make sure it's recognizable as such!
The FAQ: http://www.sendmail.org/faq/              Before you ask.

 
 
 

ruleset=check_mail..Sender domain must resolve

Post by Douglas Denaul » Tue, 24 Oct 2000 04:00:00




> > I had a transient problem with Sendmail 8.9.3

> Which OS?

BSDI 3.1. As a BTW this was a transient condition that went away with no
action on my part and has not reoccurred. The user claims to have taken
no action, thinking I fixed the problem.


> > So my questions are: (a) is this error triggered by something in the
> > envelope that does not appear in the message; (b) can anything besides
> > DNS trigger this; (c) any ideas?

> (a) No.
> (b) Depends on your service switch file.

Sorry - I do know the terminology, does this mean sendmail.c[Tw],
virtusertable, access DB and the like??

Quote:> (c) Depends on your OS; we got a report that Solaris 2.x may cause
> problems if nsswitch.conf has a certain format.

As above BSDI 3.1 - straight install. We are using _RELAY_ACCESS_FROM_
from http://www.sendmail.org/~ca/email/chk89-opt.html. I do not know the
BSD equivalent of nsswitch.conf
 
 
 

ruleset=check_mail..Sender domain must resolve

Post by Claus Assman » Wed, 25 Oct 2000 09:05:59




> > (b) Depends on your service switch file.
> Sorry - I do know the terminology, does this mean sendmail.c[Tw],
> virtusertable, access DB and the like??

No. See doc/op/op.me:

   2.5.  The Service Switch
        ...  The
      ServiceSwitchFile option points to the name of a  file
      that  has  the service definitions.  Each line has the
      name of a service and the possible implementations  of
      that service.  For example, the file:

          hosts     dns files nis
          aliases   files nis
        ...
--
If you feel the urgent wish to send me a courtesy copy of a Usenet
posting, then make sure it's recognizable as such!
The FAQ: http://www.sendmail.org/faq/              Before you ask.

 
 
 

1. Domain of sender address sender@domain.com does not resolve

Hi!

I have a Problem with sendmail 8.11.2:
Some mails can not be accepted, in /var/log/mail I receive the message

Oct  1 13:13:00 sgnet sendmail[2559]: f91BD0t02559:



Oct  1 13:13:00 sgnet sendmail[2559]: f91BD0t02559:

daemon=MTA, relay=mx0.gmx.net [213.165.64.100]

This does NOT happen from all sender domains; some can be delivered.

I tried to solve this by editing sendmail.cf :

# timeouts (many of these)
#O Timeout.initial=5m
#O Timeout.connect=5m
O Timeout.iconnect=30s
#O Timeout.helo=5m
#O Timeout.mail=10m
#O Timeout.rcpt=1h
#O Timeout.datainit=5m
#O Timeout.datablock=1h
#O Timeout.datafinal=1h
#O Timeout.rset=5m
#O Timeout.quit=2m
#O Timeout.misc=2m
#O Timeout.command=1h
O Timeout.ident=1m     #<- I've changed this from 0s to 1m
#O Timeout.fileopen=60s
#O Timeout.control=2m
O Timeout.queuereturn=5d
#O Timeout.queuereturn.normal=5d
#O Timeout.queuereturn.urgent=2d
#O Timeout.queuereturn.non-urgent=7d
O Timeout.queuewarn=4h
#O Timeout.queuewarn.normal=4h
#O Timeout.queuewarn.urgent=1h
#O Timeout.queuewarn.non-urgent=12h
#O Timeout.hoststatus=30m
O Timeout.resolver.retrans=10s
O Timeout.resolver.retrans.first=10s
O Timeout.resolver.retrans.normal=10s
O Timeout.resolver.retry=8
O Timeout.resolver.retry.first=8
O Timeout.resolver.retry.normal=8        
====================================
The last 6 values (every Timeout.resolver...) have been doubled since
I expect my Problem to be a DNS-Timeout Prob.

Any solutions???

Thanks in advance,

Marcus Hock

2. missing login / logon prompt when starting windows 95 / 98

3. check_mail cannot resolve hostnames, but they resolve

4. Cisco connection

5. Local sender's "Domain of sender address does not resolve"

6. variance,entrop ?

7. check_mail ruleset blocking of numerical username/domain?

8. IP Over PPP

9. check_mail ruleset to REJECT unresolved domain

10. rulesets after resolved in ruleset 0

11. Fehler 451 - delivery problems - Sender domain must resolve

12. Sender domain does not resolve

13. sender domain must resolve error, but nslookup found it