Just installed SIMS for a client, been up and running for almost 24 hours. I've set it up for a couple clients in the past and never saw any problems. In this case, receiving mail works fine, but it has not been able to send anything. There were a number of errors in the log, including the following:
12:01:22 1 SMTP-001([192.168.1.6]) Return-Path-MX Search Error. Error Code=-3211
I assume this means SIMS was trying to verify the return path for a local user, which seemed kind of strange to me, but I turned off verify return paths and that seemed to stop it.
That's perfectly normal behavior. Just because a client is on a client address doesn't mean that the Return-Path is valid. If SIMS sees an unresolvable domain there, it should reject the mail unless there's some other factor that
12:11:21 3 SMTP-009(mail1.no-ip.com) cannot get relays for 'optionsbydesign.com'. Error Code=-3211
Zillions of these. Does that mean the DNS is not set up properly for optionsbydesign.com? Why would it need to "get relays" for itself?
That probably means exactly that.
If that's the main name of the SIMS machine, it should not need to find the MX records for it when accepting mail, but it might do so when accepting mail for [EMAIL PROTECTED] when its mail name is something like mail.optionsbydesign.com
And...
17:25:10 3 SMTP-102(amstd.com) Failed to get IP addresses. Error Code=-3162 17:36:09 3 SMTP-105(erols.com) Failed to get IP addresses. Error Code=-3162 17:36:24 3 SMTP-107(altimac.com) Failed to get IP addresses. Error Code=-3162
This makes me think the machine itself is not doing DNS lookups properly.
Definitely.
I am going to have the client restart it when he gets in this morning but I just wanted to make sure it was not indicative of anything else.
Finally, in General Settings, should the domain be, in my case, set to "optionsbydesign.com" or to "mail.optionsbydesign.com"?
That depends on the situation.
In nearly all cases, the domain name of the SIMS server should be a name that has an A record in DNS pointing to an IP address which the world uses to connect to that machine. In my case that means that sc1.scconsult.com is the SIMS domain name on a machine that my router NAT's SMTP connections to for that address, even though nothing else on that box would see itself as sc1.
In some very simple environments where you only really want the SIMS machine accepting mail for one simple domain and don't want to have to think about DNS too hard, you can tell SIMS to use a 'bare' domain name for which it needs to accept mail, and keep it ignorant of the real fully qualified domain name that maps to the IP address it talks on. Going that way gets messy pretty quick if you have a complex environment.
-- Bill Cole [EMAIL PROTECTED]
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
