Scalix Forums

Whenever I send mail outside our domain, I get the following error

553 5.1.8 <hardip@pipeman.com>... Domain of sender address hardip@pipeman.com does not exist

Why is this ?? Is there a problem with my smtpd.cf file ??
AUTH_SUCCESS accept ALL
RELAY accept 127.0.0.1
RELAY accept .pipeman.com
RELAY Log_Reject ALL

# extra rules added to prevent open relay usage
RECIPIENT Log_Reject *@*@*
RECIPIENT Log_Reject *%*
RECIPIENT Log_Reject *!*
RECIPIENT Log_Reject *#*@*
RECIPIENT Log_Reject *#*@*

I am now at a situation where I knock my head on the wall. PLS HELP

This is an error being returned by sendmail if the domain cannot be resolved in DNS by the receiving MTA.

As you haven't posted the whole non-delivery message, there are two places where this can happen.

The first is when sendmail submits the message using its MSA to 127.0.0.1. This means that your own DNS is incorrect and the domain cannot be resolved.

The second is when sendmail acts as the MTA and submits to a remote server. In that case, the remote server needs to be able to resolve the domain correctly. Typically, this happens when somone is using a test domain that would never exist in public DNS.

For that reason, I would probably go with the fact that you do not have pipeman.com in your local DNS.

Cheers

Dave

Dear Dave, thanks for your reply. The complete error message is as follows

hardip@mac.com

because: A mail transport failure occurred


Supplementary Information:


553 5.1.8 <hardip@pipeman.com>... Domain of sender address hardip@pipeman.com does not exist

Reporting-MTA: smtp; .mail.pipeman.com
DSN-Gateway: dns; .mail.pipeman.com

Final-Recipient: rfc822;hardip@mac.com
Action: failed
Status: 5.3.0
x-scalix-Reason-Code: 5


Any ideas ??

That means that your local DNS cannot resolve pipeman.com

Cheers

Dave

Thanks Dave,

How can I check and rectify my local DNS. I do not have a seperate DNS server and I have installed scalix on a Redhat Enterprise 3 box. Is there something I am missing ??

A few things you can try to do as far as troubleshooting DNS.

1. Try to see if your domain has the correct entries. 'dig' is a tool that comes with bind that you can use to query DNS records. Example:



The above output gives us important information. It tells us what does the computer thinks that example.com points to -- in this case, its 192.0.34.166. It also tells us the nameservers listed for that domain (a.iana-servers.net and b.iana-servers.net) and most importantly, which server it queried for the information. This is the the line after Query time:

SERVER: 192.168.1.10 <-- this is the IP address of the server that this particular workstation is using for DNS. As you can see, this is an internal IP address (I have my own DNS server running on the local network).

If you issue the same command, you will get similar output, but the information to check is what server is it resolving it from. You might want to try this for your own server's fqdn to see if it resolves correctly or not.

2. Another command that you can use, that gives similar output but is not that detailed is nslookup:



Here you get the server queried, and the answer recieved. Try the above with your fqdn to see if its resolving correctly.

Hope this helps you get started.