Re: [Declude.JunkMail] SMTP_DELIV_FAILED
We're not using any Windows-based NAT service that I'm aware of - we're just using the NAT capabilities of our humble Linksys BEFSX41 router. Which is how we had the old server setup (192.168.0.3). And so I just switched the Port Forwarding to the new server (192.168.0.4) and kept the rest the same. The old server didn't have the Routing and Remote Access service running at all (which is the service for setting up Windows-based NAT, right?) And the new one has that disabled as well. Seems like there's something really simple that I've completely forgotten to do and hopefully you guys will clue in on it. Matt wrote: Kevin, 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-(f30001890106) [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 server thinking that it needs to send E-mail for rogersbenefit.com from a private IP, and it is unable to make a connection since that IP isn't routable across the Internet, and you are either not NATing and IMail is misconfigured for this domain, or your NATing is not set up properly. You need to check the configuration for this domain and make sure that it is bound to a public IP or if a virtual domain, that the server's primary domain is bound to a public IP address...or if you are NATing, you need to check this configuration in your router. I suppose that IMail might be screwy, but you should start with those choices. Note that your first log sample shows that you were properly resolving the recipient's MX records, and at least in my test from a second ago, their primary MX server is answering just fine. Matt Kevin Rogers wrote: OK - I turned that off and restarted the SMTP and QManager services. I then tried to send an email to healthnet.com again (one of about 15 domains that I've noticed this problem with) and it still did not go through. (By the way, why is it displaying the AUTH three times like that?) My SMTP settings are: Default Mail Host: localhost Domain Name Server address: 207.47.4.2 207.47.2.178 (these are 2 provided by my connection provider - I am not attempting to use my local DNS yet) Enable TLS is checked (nothing else is on the main screen) Security Tab: No mail relay Allow remote mail to local groups Allow remote view of local groups Auto-deny possible hack attempts are all checked - nothing else Advanced Tab: Delivery App: d:\imail\Declude.exe Enable SMTP TO Listen On All IPs is checked. the rest is pretty standard. QManager settings: DNS Cache is now disabled. I have enabled Failed Domain Skipping (Max entries 500 - skip time 30) Log snippet 10:08 20:18 SMTPD(f30001890106) [192.168.0.4] connect 64.121.33.15 port 6609 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] EHLO [192.168.1.110] 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] AUTH 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] AUTH 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] AUTH 10:08 20:18 SMTPD(f30001890106) Authenticated [EMAIL PROTECTED], session treated as local. 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] MAIL FROM:[EMAIL PROTECTED] 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] RCPT TO:[EMAIL PROTECTED] 10:08 20:18 SMTPD(f30001890106) [x] looking up healthnet.com in HOSTS 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] DATA 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] d:\imail\spool\Df30001890106.SMD 759 10:08 20:18 SMTP-(f30001890106) processing d:\imail\spool\qf30001890106.smd 10:08 20:18 SMTP-(f30001890106) [x] looking up healthnet.com in HOSTS and MX 10:08 20:18 SMTP-(f30001890106) [Att-Blk] Got Attachment Blocking Host Info for Rogersbenefit.com 10:08 20:18 SMTP-(f30001890106) Trying healthnet.com (0) 10:08 20:18 SMTP-(f30001890106) [x] Connecting socket to service SMTP on host healthnet.com using protocol tcp 10:08 20:18 SMTP-(f30001890106) [x] using source IP for Rogersbenefit.com [192.168.0.4] 10:08 20:18 SMTP-(f30001890106) Connect healthnet.com [204.107.47.187:25] (1) 10:08 20:18 SMTP-(f30001890106) 421 Service not available, closing transmission channel 10:08 20:18 SMTP-(f30001890106) SMTP_DELIV_FAILED 10:08 20:18 SMTP-(f30001890106) QUIT 10:08 20:18 SMTP-(f30001890106) 10:08 20:18 SMTP-(f30001890106) [u] closing socket (u) 10:08 20:18 SMTP-(f30001890106) requeuing d:\imail\spool\qf30001890106.smd R0 T1 10:08 20:18 SMTP-(f30001890106) finished d:\imail\spool\qf30001890106.smd status=3 Thanks for your help. John T (lists) wrote: Are you using DNS caching, turn that off. It
Re: [Declude.JunkMail] SMTP_DELIV_FAILED
Your router may NAT the old IP (192.168.0.3) to a public IP address, but it may not NAT the new IP (192.168.0.4) to a public IP address. Can you disable the old box and change the new box to use the old IP (192.168.0.3) or verify in your router that the new IP (...4) is properly NAT'ed to a public IP address? Tuesday, October 9, 2007, 3:05:59 AM, Kevin Rogers [EMAIL PROTECTED] wrote: KR We're not using any Windows-based NAT service that I'm aware of - we're KR just using the NAT capabilities of our humble Linksys BEFSX41 router. KR Which is how we had the old server setup (192.168.0.3). And so I just KR switched the Port Forwarding to the new server (192.168.0.4) and kept KR the rest the same. The old server didn't have the Routing and Remote KR Access service running at all (which is the service for setting up KR Windows-based NAT, right?) And the new one has that disabled as well. KR Seems like there's something really simple that I've completely KR forgotten to do and hopefully you guys will clue in on it. KR Matt wrote: Kevin, 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-(f30001890106) [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 server thinking that it needs to send E-mail for rogersbenefit.com from a private IP, and it is unable to make a connection since that IP isn't routable across the Internet, and you are either not NATing and IMail is misconfigured for this domain, or your NATing is not set up properly. You need to check the configuration for this domain and make sure that it is bound to a public IP or if a virtual domain, that the server's primary domain is bound to a public IP address...or if you are NATing, you need to check this configuration in your router. I suppose that IMail might be screwy, but you should start with those choices. Note that your first log sample shows that you were properly resolving the recipient's MX records, and at least in my test from a second ago, their primary MX server is answering just fine. Matt Kevin Rogers wrote: OK - I turned that off and restarted the SMTP and QManager services. I then tried to send an email to healthnet.com again (one of about 15 domains that I've noticed this problem with) and it still did not go through. (By the way, why is it displaying the AUTH three times like that?) My SMTP settings are: Default Mail Host: localhost Domain Name Server address: 207.47.4.2 207.47.2.178 (these are 2 provided by my connection provider - I am not attempting to use my local DNS yet) Enable TLS is checked (nothing else is on the main screen) Security Tab: No mail relay Allow remote mail to local groups Allow remote view of local groups Auto-deny possible hack attempts are all checked - nothing else Advanced Tab: Delivery App: d:\imail\Declude.exe Enable SMTP TO Listen On All IPs is checked. the rest is pretty standard. QManager settings: DNS Cache is now disabled. I have enabled Failed Domain Skipping (Max entries 500 - skip time 30) Log snippet 10:08 20:18 SMTPD(f30001890106) [192.168.0.4] connect 64.121.33.15 port 6609 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] EHLO [192.168.1.110] 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] AUTH 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] AUTH 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] AUTH 10:08 20:18 SMTPD(f30001890106) Authenticated [EMAIL PROTECTED], session treated as local. 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] MAIL FROM:[EMAIL PROTECTED] 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] RCPT TO:[EMAIL PROTECTED] 10:08 20:18 SMTPD(f30001890106) [x] looking up healthnet.com in HOSTS 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] DATA 10:08 20:18 SMTPD(f30001890106) [64.121.33.15] d:\imail\spool\Df30001890106.SMD 759 10:08 20:18 SMTP-(f30001890106) processing d:\imail\spool\qf30001890106.smd 10:08 20:18 SMTP-(f30001890106) [x] looking up healthnet.com in HOSTS and MX 10:08 20:18 SMTP-(f30001890106) [Att-Blk] Got Attachment Blocking Host Info for Rogersbenefit.com 10:08 20:18 SMTP-(f30001890106) Trying healthnet.com (0) 10:08 20:18 SMTP-(f30001890106) [x] Connecting socket to service SMTP on host healthnet.com using protocol tcp 10:08 20:18 SMTP-(f30001890106) [x] using source IP for Rogersbenefit.com [192.168.0.4] 10:08 20:18 SMTP-(f30001890106) Connect healthnet.com [204.107.47.187:25] (1) 10:08 20:18 SMTP-(f30001890106) 421 Service not available, closing
Re: [Declude.JunkMail] SMTP_DELIV_FAILED
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-(f30001890106) [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.
Re: [Declude.JunkMail] SMTP_DELIV_FAILED
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-(f30001890106) [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.
