[NTLUG:Discuss] Sendmail config

Andrew Russell andrewr at dbu.edu
Thu Apr 10 15:09:35 CDT 2003


While we're on the topic of sendmail, has anyone upgraded to 8.12.9
yet?

Thanks,

Andrew Russell
Dallas Baptist University

>>> greg at nas-inet.com 04/10/03 02:34PM >>>
Richard Humphrey wrote:
> I have a small network consisting of about 6 Red Hat servers. I have
> installed Logwatch on each one and set it to email me with the logs.
One of
> these machines is our dedicated mail server for company email. After
> instructing Logwatch to email richard at xxxxxxx.com from each of the
servers
> in the network I only recieved the one from the mail server. The rest
did
> not get emailed to me for the following reason:
> 
>  ----- The following addresses had permanent fatal errors -----
> <richard at xxxxxxx.com>
>     (reason: 553 5.1.8 <richard at xxxxxxx.com>... Domain of sender
address
> root at rob.xxxxxx.com does not exist)
> 
>    ----- Transcript of session follows -----
> ... while talking to mail.xxxxxx.com.:
> 
>>>>RCPT To:<richard at xxxxxxx.com>
>>>
> <<< 553 5.1.8 <richard at xxxxxx.com>... Domain of sender address
> root at rob.xxxxxxx.com does not exist
> 550 5.1.1 <richard at xxxxxx.com>... User unknown
> 
> What do I need to do to fix this problem? Do I need to configure
sendmail
> locally to forward to the mail server?
> 
>  Richard Humphrey
> 

I just went through this same basic problem.  Did you start sendmail on

the sending servers?

It use to be that sendmail only needed to be on the machine for mail to

use it.  I did not research the why and when but it seems that if 
sendmail is not running it will not get the mail sent.

You do not need to change any config options in sendmail out of the
box. 
  Make sure sendmail and sendmail.cf are installed.  I setup aliases to

forward all root to webmaster at xxxx.com and ran "sendmail -bi" (it seems

that mandrake screwed up newaliases) to rebuild the mail aliases table.

  I left logwatch with default settings.  Start sendmail, do this in 
init so that you don't have to do it manually.

Make sure that xxxxx.com has an MX record that resolves correctly for 
the user.

Oops :)  I just reread your Transcript.  It says rob.xxxxxxx.com domain

does not exist!!!  Just add a DNS record for that domain (alias CN 
record should do it) that resolves internally.  This does not need to 
get out to the world, just internally.

-- 
Greg Edwards
New Age Software, Inc. - http://www.nas-inet.com 
======================================================
Galactic Outlaw        - http://goutlaw.nas-inet.com 
   The ultimate cyberspace adventure!


_______________________________________________
https://ntlug.org/mailman/listinfo/discuss



More information about the Discuss mailing list