Re: [Declude.JunkMail] SMTP_DELIV_FAILED

[Kevin Rogers]

Just as a quick follow up: I spoke with Ipswitch support and we seem to have things working a little better. I can now send to those trouble domains (at least most of the time).  The tech said to change the 127.0.0.1 IP from Imail's DNS server field back to 192.168.0.4, which seemed to help. But I did a quick test at dnsstuff.com and it looks like I am failing one of their tests: FAIL Mismatched glue ERROR: Your nameservers report glue that is different from what the parent servers report. This will cause DNS servers to get confused; some may go to the IP provided by the parent servers, while others may get to the ones provided by your authoritative DNS servers. Problem record(s) are: NS1.WORLDNIC.com.: Parent server (d.gtld-servers.net) says A record is 205.178.190.1, but authoritative DNS server (205.178.190.1) says it is 209.62.20.186 NS2.WORLDNIC.com.: Parent server (d.gtld-servers.net) says A record is 205.178.189.1, but authoritative DNS server (205.178.190.1) says it is 209.62.20.186 NS1.WORLDNIC.com.: Parent server (d.gtld-servers.net) says A record is 205.178.190.1, but authoritative DNS server (205.178.189.1) says it is 209.62.20.186 NS2.WORLDNIC.com.: Parent server (d.gtld-servers.net) says A record is 205.178.189.1, but authoritative DNS server (205.178.189.1) says it is 209.62.20.186 We use Myriad Network as a backup MX record in case our server is down.  The 209.62.20.186 IP is their IP.  I don't know how their IP got into my DNS records, except as a backup MX record (not for the A record).  I am waiting on hearing back from them.  Could this have been part of the problem before?  We host our DNS records at Network Solutions (that's the 205.178.190.1 IP) - I'm not really understanding what's going on here.  Sorry for being a pain - I appreciate your help. Kevin Kevin Rogers wrote: I appear to be able to telnet to that address - it says 220 mailgate02.healthnet.com ESMTP ***** SMTP Ready ***** Darrell ([EMAIL PROTECTED]) wrote: Matt wrote: I haven't followed this thread much, but it seems fairly obvious what the the problem is related to. When your server is connecting to the recipient's server, it fails to establish a connection with that server.  This log line indicates the likely source of the problem:    10:08 20:18 SMTP-(f300018900000106) [x] using source IP for Rogersbenefit.com [192.168.0.4] While you might be doing NAT on your network, it doesn't appear that this is the case here, and the failure is probably being caused by your If he was not doing NAT he would not be able to send mail to anyone since his server is on private ip.  No ISP will route RFC1918 addresses across the public internet.  So it's doubtful its a NAT issue. Kevin - are you able to telnet to their mailserver from any other machines on your network? telnet 204.107.47.187 25 Darrell --- This E-mail came from the Declude.JunkMail mailing list.  To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail".  The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list.  To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail".  The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.