Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Sendmail/MX/DNS problem

Posted on 1997-06-06
Medium Priority
Last Modified: 2010-03-18
I've been using my Linux machine as an SMTP/POP3 server for some time now with no problem.  Recently I started using it as a name server for my company's domain.

I can't receive mail now for accounts on this machine, mail destined for other places works fine (ie, someone@linuxbox.mydomain.com can't get mail, but someone@mydomain.com can..I'm using another mail server for mydomain.com mail).

I get the following in the returned message if I send mail to root@linuxbox.mydomain.com:

   ----- Transcript of session follows -----
553 linuxbox.mydomain.com. config error: mail loops back to me (MX problem?)
554 <root@linuxbox.mydomain.com>... Local configuration error

Here's my domain file:

@               IN      SOA     linuxbox.mydomain.com. hostmaster.mydomain.com. (
                                1       ; Serial
                                28800   ; Refresh
                                7200    ; Retry
                                604800  ; Expire
                                86400)  ; Minimum TTL
                        NS      linuxbox.mydomain.com.
                        MX      10 proxy.mydomain.com.

router                  A
linuxbox               A
proxy                   A
                        MX      10 proxy.mydomain.com.

And here's an excerpt from /var/log/messages:

Jun  6 08:56:59 linuxbox sendmail[1964]: IAA01964: from=<root@linuxbox.mydomain.com.>, size=293, class=0, pri=30293, nrcpts=1, msgid=<Pine.LNX.3.96.97060608565
2.1962A-100000@linuxbox.mydomain.com.>, proto=SMTP, relay=root@localhost

Jun  6 08:56:59 linuxbox named[1945]:XX /

Jun  6 08:56:59 linuxbox named[1945]: XX /

Jun  6 08:56:59 linuxbox identd[1969]: from: ( linuxbox.mydomain.com. ) for: 1306, 25

Jun  6 08:56:59 linuxbox identd[1969]: Successful lookup: 1306 , 25 : root.root

Jun  6 08:56:59 linuxbox sendmail[1966]: IAA01964: to=<mike@linuxbox.mydomain.com.>,ctladdr=<root@linuxbox.mydomain.com.> (0/0), delay=00:00:00,xdelay=00:00:00, mailer=esmtp, relay=linuxbox.mydomain.com. [], stat=Local configuration error

Jun  6 08:57:00 linuxbox sendmail[1966]: IAA01964: IAA01966: DSN: Local configuration error

I've tried with and without an MX record for linuxbox.mydomain.com..both results are the same.

Again, right now all mail to mydomain.com goes to another server..only mail to linuxbox.mydomain.com is being bounced.

Any help would be appreciated..thanks.
Question by:t-bone
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Author Comment

ID: 1584810
Edited text of question

Author Comment

ID: 1584811
Edited text of question

Author Comment

ID: 1584812
Edited text of question
Fill in the form and get your FREE NFR key NOW!

Veeam® is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.


Expert Comment

ID: 1584813
Run the following command, and post the result here:
/usr/lib/sendmail -bt
3,0 xx@linuxbox.mydomain.com


Expert Comment

ID: 1584814
Do you have mydomain.com and linuxbox.mydomain.com in your
sendmail.cw ?

Expert Comment

ID: 1584815
What domain did you set up your sendmail.cf for to be "local"?
If it just is "mydomain.com", your mailer will think of "linuxbox.mydomain.com" as a remote system.

Also check this stuff:

  domain mydomain.com

LVL 19

Accepted Solution

xterm earned 800 total points
ID: 1584816
Make sure you have an entry like this in /etc/sendmail.cf:

# file containing names of hosts for which we receive email

$ echo linux.mydomain.com >> /etc/sendmail.cw

then kill sendmail:
$ kill `ps -ax | grep -v grep | grep sendmail | awk 'print $1'`

...and finally restart sendmail:
$ sendmail -bd

voila.. try sending mail to yourself now

Featured Post

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I have seen several blogs and forum entries elsewhere state that because NTFS volumes do not support linux ownership or permissions, they cannot be used for anonymous ftp upload through the vsftpd program.   IT can be done and here's how to get i…
Note: for this to work properly you need to use a Cross-Over network cable. 1. Connect both servers S1 and S2 on the second network slots respectively. Note that you can use the 1st slots but usually these would be occupied by the Service Provide…
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
Suggested Courses

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question