Hi All

I have set up a server for our local network. Server offers mail, dhcp and DNS services. All have been configured and work correctly. Network users can successfully send and recieve local network mail. The server is not connected to the internet directly. The network gateway is a dedicated router device. All computers on the network can connect and resolve names external to our network. So as far as I can tell there are no obvious DNS issues with our network.

PROBLEM: I want to let local network users send outward bound mail via the mail server (remember up until now the server only sends and recieves local mail). I added the network subnet address to the '/etc/mail/access' file. The mail server now accepts mail for relaying. However, a problem is that after the message is accepted by the server, it just sits in the mail queue. The messages that sit in the queue all say 'lookup (name.com): deferred'.

There is a list of the things I have done to try and solve this problem:

1. I ran 'sendmail -v -q' and got the following message:

yahoo.com: Nameserver timeout
<name@name.com>...Transient parse error -- message queueed for future delivery.

2. If I use the IP address instead of 'name.com' and run 'sendmail -v -q' I get the following error:

<name@[64.58.79.230]>... connecting to [64.58.79.230] via esmtp...
<name@[64.58.79.230]>... deferred: [64.58.79.230]: No route to host

3. If I use 'nslookup -type=MX -timeout=60 yahoo.com' I get the following:

Server: 192.168.1.1
Address: 192.168.1.1#53

I have read a good portion of the batbook, look at the sendmail site, read many sendmail tutorials, but am still baffled by this one. I know it is possible, as our old linux server (which we retired recently) did everything just fine (no I didn't set that one up). It would also relay mail to yahoo.com and anyother address one cared to use.

I really hope someone can help me out with this one.

Kind regards,

Ben

Almost sounds like your gateway is bad, or you have a bad subnet.

Can you traceroute to yahoo?

Check your internet IP address side settings and your default gateway and your subnet mask.

Worked out what the problem was. The gateway address wasn't entered correctly. Didn't notice it before as up until now all of the server functions are all within the LAN. I kind of feel a bit stupid, don't know why I didn't look at this one earlier.

Thanks for your help anyway,

Ben

Hi everybody

I have the same problem too. I upgraded to RedHat 8 a Redhat 7.3 box,
which was a client of the enterprise mail-hub whith sendmail-8.11.6-15.

This box IS NOT CONNECTED TO THE NET (no route),
THEREFORE has no DNS resolving.

So it is usually configured to send ALL the mail to the mailhub (which can , in turn resolve domain names, and send to my ISP smtp server.

But now with Red Hat 8 and sendmail-8.12.8-5.80 I have :

# echo aaa| mail -v -s tyty4 jerome@mydomain
mydomain: Name server timeout
jerome@mydomain... Transient parse error -- message queued for future delivery

and that , too :

# echo aaaa | mail -v -s trial this-could-be-a-user
this-could-be-a-user... Connecting to [127.0.0.1] via relay...
220 panthere.netinternal. ESMTP Sendmail 8.12.8/8.12.8; Wed, 16 Jul 2003 00:24:28 +
0200
>>> EHLO panthere.netinternal
250-panthere.netinternal Hello localhost.localdomain [127.0.0.1], pleased to meet
you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-DELIVERBY
250 HELP
>>> MAIL From:<root@panthere.netinternal> SIZE=46
250 2.1.0 <root@panthere.netinternal>... Sender ok
>>> RCPT To:<this-could-be-a-user@panthere.netinternal>
>>> DATA
250 2.1.5 <this-could-be-a-user@panthere.netinternal>... Recipient ok
354 Enter mail, end with "." on a line by itself
>>> .
250 2.0.0 h6FMOSZu003608 Message accepted for delivery
this-could-be-a-user... Sent (h6FMOSZu003608 Message accepted for delivery)
Closing connection to [127.0.0.1]
>>> QUIT
221 2.0.0 panthere.netinternal closing connection

So it means that on my mail client "panthere" for any recipient
without @, the mail is forwarded throw the mailhub
and with a @, it searches to resolve the hostname to reach itself
instead of the mail hub !


How can I tell this new sendmail packahe THAT IT MUST NOT RESOLVE HOSTNAMEs!
just forward all the mail to the mailhub!

I tried : service.switch,
FEATURE(`accept_unresolvable_domains'),


Anybody has any idea

Thanks
Jerome

Hi (newbie on sendmail here)

I've this problem, I'm testing my sendmail.cf configuration using sendmail -bt and I'm able to send mails to our company's mail accounts. (our mail server is on another machine), but when i try an outside account what i get is

canonify input: ricardo_sada @ yahoo . com . mx
Canonify2 input: ricardo_sada < @ yahoo . com . mx >
yahoo.com.mx: Name server timeout
Canonify2 returns: ricardo_sada < @ yahoo . com . mx >
canonify returns: ricardo_sada < @ yahoo . com . mx >
== Ruleset 3,0 (3) status 75
blablabla

messages are left in /var/spool/clientmqueue

I cannot traceroute to yahoo.com.mx but I definitly can ping and even browse from the internal linux server Im trying to setup...

How can I configure the DNS sendmail uses to resolve outside names..

any help is appreciated

ricardo sada