eric007
asked on
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.domai
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.
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.domai
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.
Thx