>Could someone explain exactly why IMAIL has trouble sending email to
>major mail providers at times. My smtp fails all the time and must
>resort to sending through my default mail host.
>
>I just set up my IMAIL server about 12 hours ago and my reverse DNS lookup
>has not yet propagated to all DNS servers.
there's no such thing as "propagation".
>Is this why? Should I be patient and wait for reverse DNS to propagate?
It ain't going to happen. If a DNS client queries your DNS, it
queries your DNS NOW! there's no propagation delay.
>Is there a setting I can check to make sure this is my problem? Many
>domains work, but the big ones seem to reject the most:
>
>i.e. @home.com, @yahoo.com, etc..
>
>When I do an nslookup for my ip from the @home DNS servers, they are still
>showing the old entry.
that's not propagation, that's TTL delay where your old records in
their caches have not yet expired. if you're talking about futuretrade:
# dig futuretrade.com mx
; <<>> DiG 8.2 <<>> futuretrade.com mx
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 4
;; QUERY SECTION:
;; futuretrade.com, type = MX, class = IN
;; ANSWER SECTION:
futuretrade.com. 1D IN MX 60 mh2.cts.com.
futuretrade.com. 1D IN MX 50 mail.futuretrade.com.
;; AUTHORITY SECTION:
futuretrade.com. 1D IN NS ns.cts.com.
futuretrade.com. 1D IN NS news.cts.com.
there is currently a 1Day TTL. So if caching is your pb, then 1Day
is the max it will require before all the old records expire.
Use dig to query the other NS's and see how much is left. My
nameserver shows this now based on the query I made about 3 minutes
ago to your NS:
# dig futuretrade.com mx
; <<>> DiG 8.2 <<>> futuretrade.com mx
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 3
;; QUERY SECTION:
;; futuretrade.com, type = MX, class = IN
;; ANSWER SECTION:
futuretrade.com. 23h57m28s IN MX 50 mail.futuretrade.com.
futuretrade.com. 23h57m28s IN MX 60 mh2.cts.com.
see, no more 1Day, but "23h57m28s".
look here:
# dig +norec @ns1.home.net futuretrade.com any
; <<>> DiG 8.2 <<>> +norec @ns1.home.net futuretrade.com any
; (1 server found)
;; res options: init defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28831
;; flags: qr ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; QUERY SECTION:
;; futuretrade.com, type = ANY, class = IN
;; ANSWER SECTION:
futuretrade.com. 5h31m8s IN NS NEWS.CTS.COM.
futuretrade.com. 5h31m8s IN NS NS.CTS.COM.
;; AUTHORITY SECTION:
futuretrade.com. 5h31m8s IN NS NEWS.CTS.COM.
futuretrade.com. 5h31m8s IN NS NS.CTS.COM.
;; ADDITIONAL SECTION:
NEWS.CTS.COM. 2h20m36s IN A 192.188.72.21
NS.CTS.COM. 1h34m43s IN A 192.188.72.18
See the TTL times being less than 1Day ? That's how much longer your
records will live in the ns1.home.net cache.
btw, I doubt this has anyting to do with "MX connect fail". Have you
tried to telnet to those ip's that your Imail can't connnect to?
Len
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
