Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 265
  • Last Modified:

Mail server spitting back Email

I am running Slackware with sendmail running as pop3 and smtp server

When people try to send mail to the server

someone@mydomain.com

Mail servers are spitting it back saying that it is looping back to them, and maybe its an MX problem

This server was working fine and I don't know what happened to it??

Any help is greatly appreciated
0
eric007
Asked:
eric007
  • 2
1 Solution
 
RobWMartinCommented:
Do you administrate the DNS that advertises your mail server?  If so, can you post the relevant parts of your zone file, esp. the MX record and anything mentioning mydomain.com.  Also, can we see the exact error message?

Thx
0
 
jlevieCommented:
There could be a DNS problem, but more likely the problem is the sendmail config. The Sendmail FAQ says:

I'm getting these error messages:

        553 MX list for domain.net points back to relay.domain.net
        554 <user@domain.net>... Local configuration error

How can I solve this problem?

You have asked mail to the domain (e.g., domain.net) to be forwarded to a specific host (in this case, relay.domain.net) by using an MX record, but
the relay machine doesn't recognize itself as domain.net. Add domain.net to /etc/sendmail.cw (if you are using FEATURE(use_cw_file)) or add "Cw
domain.net" to your configuration file.

IMPORTANT: When making changes to your configuration file, be sure you kill and restart the sendmail daemon (for ANY change in the
configuration, not just this one):
0
 
jlevieCommented:
Oh yeah, if it's a DNS problem the usual cause, per the sendmail FAQ (http://www.sendmail.org/faq/), is:

Wildcard MX records have lots of semantic "gotcha"s. For example, they will match a host "unknown.your.domain" -- if you don't explicitly test for
unknown hosts in your domain, you will get "MX list for hostname points back to hostname" or "config error: mail loops back to myself".

See RFCs 1535, 1536, and 1912 (updates RFC 1537) for more detail and other related (or common) problems. See also _DNS and BIND_ by
Albitz and Liu.

They can also cause your system to add your domain to outgoing FQDNs in a desperate attempt to get the mail to where it's supposed to go, but
because *.your.domain is valid due to the wildcard MX, delivery to not.real.domain.your.domain will get dumped on you, and you may even find
yourself in a loop as the domain keeps getting tacked on time after time after time (the "config error: mail loops back to myself" problem).

Wildcard MX records are just a bad idea, plain and simple. They don't work the way you'd expect, and virtually no one gets them right. Avoid them
at all costs.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now