At 10:14 PM 7/19/2002 -0500, David Lucas wrote:
Ok, I accept your answer. BUT...I was not talking about checking mail, I
was talking about sending without checking first.
I think the problem is the DNS or server set up. I querried
www.huntingleasesonline.com and got no return. I checked
huntingleasesonline.com and the first MX record was pointing
huntingleasesonline.com to www.huntingleasesonline.com. There is a
second MX record pointing at mx1.realtime.net and a third pointing at
mx2.realtime.net
There is an additional A record for www.huntingleaseonline.com.
I think the mail gets real confused as where to deliver to.
His own nameservers don't return an answer for MX record. It is the same
with other name servers.
The DNS is not set up correctly!!!
I'm reasonably positive that this isn't a DNS issue. I've seen it
discussed here before and someone posted a link to the solution (which I
didn't save because I wasn't experiencing the problem at the time, and now
am unable to find). The client is NOT trying to send mail through the box,
he is sending mail from his swt.edu account TO his domain on the box.
Just in case it is a DNS issue, here's my zone file:
@ IN SOA ns.realtime.net. hostmaster.realtime.net. (
2000110901 ; Serial number (change me!)
21600 ; Refresh every 6 hours
3600 ; Retry every hour
604800 ; Expire zone after 2 weeks
21600 ) ; Cache for minimum 6 hours
IN NS ns.realtime.net.
IN NS ns2.realtime.net.
;
; MX forwarding
@ A 205.238.184.3
IN MX 5 www
IN MX 10 mx1.realtime.net.
IN MX 50 mx2.realtime.net.
;
mail A 205.238.184.3
smtp A 205.238.184.3
pop3 A 205.238.184.3
www A 205.238.184.3
ftp A 205.238.184.3