>I am experiencing a critical problem.
>All outgoing mail fails to deliver.
so now, what's your problem?? vbg
>The best I can make out is that IMail has decided to use port 0 to contact
>other SMTP servers. Here's a log clip:
nope
>06:23 21:45 SMTPD(00140076) [226.66.29.56] connect 218.191.39.65 port 1079
>06:23 21:45 SMTPD(00140076) [218.191.39.65] HELO thor
>06:23 21:45 SMTPD(00140076) [218.191.39.65] MAIL FROM: <[EMAIL PROTECTED]>
>06:23 21:45 SMTPD(00140076) [218.191.39.65] RCPT TO: <[EMAIL PROTECTED]>
>06:23 21:45 SMTPD(00140076) [218.191.39.65] D:\IMail\spool\D20d8076.SMD 861
FYI, up to here it's incoming: SMTPD is the "D"aemon, SMTPD Server.
>06:23 21:45 SMTP-(00000394) processing D:\IMail\spool\Q20d8076.SMD
>06:23 21:45 SMTP-(00000394) Trying ghammer.net (0)
0 is the zero-th retry, ie, the first attempt.
>06:23 21:46 SMTP-(00000394) MX connect fail "192.41.15.67"
>06:23 21:46 SMTP-(00000394) requeuing D:\IMail\spool\Q20d8076.SMP R0 T1
>06:23 21:46 SMTP-(00000394) finished D:\IMail\spool\Q20d8076.SMP status=3
>If that is correct, why would IMail decide to use 0 instead of 25, and more
>importantly, where can I set the port manually?
You're totally off base, but we'll call time out and you can walk back.
My guess is your DNS is screwed, but it's at least responding:
# dig @NS1.fravistat.com fravistat.com ns
; <<>> DiG 8.2 <<>> @NS1.fravistat.com fravistat.com ns
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUERY SECTION:
;; fravistat.com, type = NS, class = IN
;; ANSWER SECTION:
fravistat.com. 1H IN NS ns1.fravistat.com.
fravistat.com. 1H IN NS ns1.ttiweb.com.
;; ADDITIONAL SECTION:
ns1.fravistat.com. 1H IN A 216.144.135.194
ns1.ttiweb.com. 1H IN A 216.86.19.2
but neither of your DNS's is responding authoritatively. afaics, you've got
syntax errors in the fravistat SOA of both NS's. Syntax errors will make
the DNS refuse to go authoritative for the zone. Fix that, at least.
Which NS have you told Imail to use? If your NS's are BIND8, turn on full
logging and see if there are errors when your mail ip, .222, queries.
searching for
mx connect fail
in the ipswith KB returns some suggestions.
Len
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
