Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Operating System - Tru64 Unix
Showing results for 
Search instead for 
Did you mean: 

sendmail with new MS exchange relay

sendmail with new MS exchange relay

We have just upgraded our MS exchanmge env to 2007.
I am trying to get sendmail to use the new environment, but it insists on using the old relay info.
When I run mailsetup it tells me that it has checked DNS and found an MX record, but for the old relay server which is no longer in DNS.
Clearly it is NOT interrogating DNS.
Any ideas where this config info is being stored?

Thanks in advance.
PS this is a production server!!


Re: sendmail with new MS exchange relay

Additional info ;

Most sites should define a general relay. If your host cannot
resolve how to deliver a mail message, the mail is forwarded to
this general relay for processing.

Do you wish to add a general purpose relay ([y]/n) ? y

Mailsetup has queried DNS (BIND) and found that TCP/IP mail for the
domain `' is handled by the relay
If you wish to use TCP/IP and nhoexch4 as your general relay,
it is suggested that you enter the phrase `', and
let DNS (BIND) forward it to nhoexch4.

Enter the general purpose relay [ ]:

This is where my problem is. That exchange server no longer exists and is not in DNS let alone an MX record. clearly not accessing DNS.Where does it get this config from?
There is no mention of it in
Pieter 't Hart
Honored Contributor

Re: sendmail with new MS exchange relay

start "nslookup"
it should respond with the ip-address of the dns-server queried.
set type=mx
or set type=any
or !(beware the last dot)

check /etc/resolv.conf
it may be local files are first searched for name resolving

other possibility is dns-cache on the local host wich may timeout eventually but should be able to flush manually