mailenable DNS resolution test fails - and the meatball rolls down the mountain

after 3 weeks (did I break a record?) of not being able to get apache to work I think it does now... (well all godaddy registered sites work and mydomain doesn't so we wait a few dayzzzzzzzz for a bit more prop-o-gate) and now the mail enable questions start... all tests are good except this one... it says ...


...to verify the settings of the SMTP connector using the mmc admin - or -

...the DNS server I requested does not have an MX CNAME or a DNS record for the local host -or-


Network connectivity reliability (use ping to determine etc.)

I did set godaddy A CNAME and MX records to...

A record @ and my IP address

CNAME - mail and mail.bigdrivehosting.com

CNAME - www and @

CNAME - smtp and smtp.bigdrivehosting.com

mx0 @ and mail.bigdrivehosting.com

and the smtp log shows


[01/25/04 01:49:37]****************** LOG FILE STARTED *******************
01/25/04 01:55:21 SMTP-IN 432 127.0.0.1 220 mail.bigdrivehosting.com ESMTP MailEnable Service, Version: 1.71-- ready at 01/25/04 01:55:21 0 0
01/25/04 08:06:04 SMTP-IN 444 127.0.0.1 220 mail.bigdrivehosting.com ESMTP MailEnable Service, Version: 1.71-- ready at 01/25/04 08:06:04 0 0

is it possible that apache running as a server is 'intercepting' port 25 and mail enable wants that cleared?

wha wha wha settings do the mx and cname need? am I close on these?

anyone use this little utility mailenable? for NT I have to say it did install and seemed to work almost dead out of the box....

 

 

 

 

Top