NMS 6 won't start smtp

[AHinMaine]

This is really stumping me... I'm too embarrassed to ask my coworkers about it.

I've been trying to install nms 6.1 (and 6) on a test bench machine for my own experimentation. I've installed nms a few times and have had a class on it and everything. I even have some canned directions which I have followed successfully in the past. But for some reason, on this box (SunOS <hostname w/h> 5.8 Generic_108528-16 sun4u sparc SUNW,Ultra-2), it absolutely refuses to start smtp. It starts everything else, but not smtp. There are no errors, related or unrelated, in the log when I issue './start-msg smtp'.

Does this look right too?

# ./configutil | egrep '(imta|smtp)'
local.imta.imta_tailor = /usr/netscape/servers/msg-<hostname w/h>/imta/config/imta_tailor
local.imta.ssrenabled = yes
logfile.imta.buffersize = 0
logfile.imta.createtimestamp = 20021127145909Z
logfile.imta.creatorsname = &quot;uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot&quot;
logfile.imta.expirytime = 604800
logfile.imta.flushinterval = 60
logfile.imta.logdir = /usr/netscape/servers/msg-<hostname w/h>/log/imta
logfile.imta.loglevel = Notice
logfile.imta.logtype = NscpLog
logfile.imta.maxlogfiles = 10
logfile.imta.maxlogfilesize = 2097152
logfile.imta.maxlogsize = 20971520
logfile.imta.minfreediskspace = 5242880
logfile.imta.modifiersname = &quot;uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot&quot;
logfile.imta.modifytimestamp = 20021127145909Z
logfile.imta.objectclass = nsmsgCfgLog
logfile.imta.rollovertime = 86400
logfiles.imta.alias = |logfile|imta
logfiles.imta.createtimestamp = 20021127145909Z
logfiles.imta.creatorsname = &quot;uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot&quot;
logfiles.imta.modifiersname = &quot;uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot&quot;
logfiles.imta.modifytimestamp = 20021127145909Z
logfiles.imta.objectclass = nsmsgCfgAlias
service.http.smtpport = 25

One thing I'm wondering and tried to find in the docs, does the hostname of the server need a valid MX? It does not have one and wasn't intending for it to receive mail for that domain at all. I have a couple of other domains that I was going to try to set up.

Any clues?

-Andy

 

[AHinMaine]

Nevermind. I appear to have been correct about the MX thing. I changed the hostname to one that had an mx and it seems fine. DOH

I hate it when I blow like 5 hours of time over something stupid.