I am getting hundreds of the Stack connect fail errors, so I cannot ignore it ;)

Here's a couple of them.


SMTP (4700) Stack connect fail "129.33.65.138"
SMTP (4700) requeuing d:\IMail\spool\QHE02220.VAP R0 T1
SMTP (4700) finished d:\IMail\spool\QHE02220.VAP status=3
----------------------------------------------------------------------------
SMTP (3656) Stack connect fail "157.174.228.214"
SMTP (3656) requeuing d:\IMail\spool\Q21110c8.SMP R0 T1
SMTP (3656) finished d:\IMail\spool\Q21110c8.SMP status=3
----------------------------------------------------------------------------
SMTPD (17C30104) [192.168.1.2] connect 156.21.1.21 port 1675
SMTPD (17C30104) [156.21.1.21] EHLO list.ipswitch.com
SMTPD (17C30104) [156.21.1.21] MAIL FROM:<[EMAIL PROTECTED]>
SMTPD (17C30104) [156.21.1.21] RCPT To:<[EMAIL PROTECTED]>
SMTPD (17C30104) [156.21.1.21] d:\IMail\spool\D1ece104.SMD 1525
SMTP (4316) processing d:\IMail\spool\Q1ece104.SMD
SMTP (4316) ldeliver rootdesign.com kevin-main (1) <[EMAIL PROTECTED]> 1525
SMTP (4316) finished d:\IMail\spool\Q1ece104.SMD status=1
SMTP (4560) processing d:\IMail\spool\Q184fd2a.GSC
SMTP (4560) ldeliver rogersbenefit.com scline-Sent (1) <[EMAIL PROTECTED]> 1624
SMTP (4560) Trying nmfn.com (0)
SMTP (4560) MX connect fail "63.76.139.136"
SMTPD (0A480106) [192.168.0.2] connect 64.220.99.252 port 37965


<---NOTE: should the IP address (192.168.0.2) be an external or internal IP????? -->

SMTPD (17C50104) [192.168.0.2] connect 192.168.0.2 port 2252
SMTPD (0A480106) [64.220.99.252] EHLO mail.cbsstl.com
SMTPD (0A480106) [64.220.99.252] MAIL FROM:<[EMAIL PROTECTED]>
SMTPD (0A480106) [64.220.99.252] RCPT TO:<[EMAIL PROTECTED]>
SMTPD (0A480106) [64.220.99.252] d:\IMail\spool\D1ee0106.SMD 43259
SMTP (4688) processing d:\IMail\spool\Q1ee0106.SMD
SMTP (4688) ldeliver rogersbenefit.com dsmith-main (1) <[EMAIL PROTECTED]> 43259
SMTP (4688) finished d:\IMail\spool\Q1ee0106.SMD status=1
SMTP (4560) Stack connect fail "129.33.65.138"
SMTP (4560) requeuing d:\IMail\spool\Q184fd2a.GSP R0 T1
SMTP (4560) finished d:\IMail\spool\Q184fd2a.GSP status=3
----------------------------------------------------------------------------
SMTP (4172) Stack connect fail "206.195.193.120"
SMTP (4172) requeuing d:\IMail\spool\Q15f85c2.GSP R0 T2
SMTP (4172) finished d:\IMail\spool\Q15f85c2.GSP status=3
SMTP (4172) d:\IMail\spool\Q1655188.GSP
SMTP (4172) processing d:\IMail\spool\Q1655188.GSP
SMTPD (08AA0108) [192.168.0.2] connect 208.221.241.51 port 58791
SMTPD (08AA0108) [208.221.241.51] HELO noticehost.abcdistributing.com
SMTPD (08AA0108) [208.221.241.51] MAIL FROM:<[EMAIL PROTECTED]>
SMTPD (08AA0108) [208.221.241.51] RCPT TO:<[EMAIL PROTECTED]>
SMTPD (08AA0108) [208.221.241.51] d:\IMail\spool\D195f108.SMD 17572
SMTP (316) processing d:\IMail\spool\Q195f108.SMD
SMTP (316) ldeliver rogersbenefit.com USER-main (1) <[EMAIL PROTECTED]> 17572
SMTP (316) finished d:\IMail\spool\Q195f108.SMD status=1
SMTP (4172) Trying principal.com (0)
SMTP (316) processing d:\IMail\spool\Q1981108.SMD
SMTP (316) ldeliver rogersbenefit.com lcarleton-main (1) <[EMAIL PROTECTED]> 5745
SMTP (316) finished d:\IMail\spool\Q1981108.SMD status=1
SMTP (4172) Stack connect fail "206.195.193.120"
SMTP (4172) requeuing d:\IMail\spool\Q1655188.GSP R0 T2
SMTP (4172) finished d:\IMail\spool\Q1655188.GSP status=3
SMTP (4172) d:\IMail\spool\Q169f14e.GSP
SMTP (4172) processing d:\IMail\spool\Q169f14e.GSP



Hope this helps.


Thanks again.


R. Scott Perry wrote:



I'm getting several different types of errors for our domain rogersbenefit.com

Stack Connect Fail
MX Connect Fail


These will occur if IMail can't connect to a remote mailserver ("MX Connect Fail" meaning that it can't connect to one of the MX records, "Stack Connect Fail" meaning that it can't connect to any of the mailservers).

In most cases, these are due to problems on the remote end. But if you see them a lot, there could be a DNS issue on your end.

550 relaying to <[EMAIL PROTECTED]> prohibited by administrator
550 5.7.1 Unable to relay for [EMAIL PROTECTED]


This is most likely due to either [1] The IMail "Using-the-A-record-instead-of-MX-record" bug, or [2] ValidDomain.com has a bogus backup mailserver that rejects mail (which is all too common).

I think this is the MX / A record bug (like people in here suggested), but aside from upgrading, what else can I do.


If it is the "Using-the-A-record-instead-of-MX-record" bug, your options are to accept the problem or upgrade. There aren't any known workarounds to this problem. If it was just happening for one domain, you could add an entry to your HOSTS file -- but it seems to happen randomly.

However, the first thing to check is the log file entries, to see if IMail connected to an IP in the MX record (in which case the problem is at the remote end), or whether it connected to an IP in the A record (in which case it is the IMail bug, assuming that an MX record does indeed exist).

-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask about our free 30-day evaluation.


---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]



To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/


.




To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/

Reply via email to