It only effects incoming email.
You can get around it by using a smarthost. Your cable company probably
allows
you to use their server for such purpose. That's how I get around it.
________________________________
From: isalist-bounce@xxxxxxxxxxxxx on behalf of ISA
Sent: Thu 1/18/2007 7:22 PM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] SMTP Connection Closed
I thought that would affect my outgoing mail - not incoming!
<unfortunately I can't get a static IP for another few months, I will
then>
Joseph Danielsen, MCSA-Messaging, MCP
Network Blade Inc.
49 Marcy Street
Somerset, NJ 08873
732-213-0600
www.networkblade.com <http://www.networkblade.com/>
<https://harbor.bounceme.net/Exchange/amy/Drafts/RE:%20[isalist]%20SMTP%20Conn
ection%20Closed.EML/1_multipart/image001.jpg>
<https://harbor.bounceme.net/Exchange/amy/Drafts/RE:%20[isalist]%20SMTP%20Conn
ection%20Closed.EML/1_multipart/image002.jpg>
________________________________
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On
Behalf Of Amy Babinchak
Sent: Thursday, January 18, 2007 7:20 PM
To: isalist@xxxxxxxxxxxxx
Subject: RE: [isalist] SMTP Connection Closed
according to dsnstuff.com you are listed on 3 blacklists and have no
reverse
DNS entry. That's enough right there to cause you to have inconsistant
incoming email issues.
________________________________
From: isalist-bounce@xxxxxxxxxxxxx on behalf of ISA
Sent: Thu 1/18/2007 7:06 PM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] SMTP Connection Closed
Amy:
DNS seems to be working (mail.networkblade.com resolves to the correct
IP),
"I" am not blacklisting and I don't know how to Grey list.
The ISP (cable company) is always suspect of everything else.
Joseph Danielsen, MCSA-Messaging, MCP
Network Blade Inc.
49 Marcy Street
Somerset, NJ 08873
732-213-0600
________________________________
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On
Behalf Of Amy Babinchak
Sent: Thursday, January 18, 2007 7:02 PM
To: isalist@xxxxxxxxxxxxx
Subject: RE: [isalist] SMTP Connection Closed
So assuming that this used to work you've eliminated the other obvious
things
besides filtering like bad DNS, flakey ISP, blacklisting, grey listing,
etc?
________________________________
From: isalist-bounce@xxxxxxxxxxxxx on behalf of ISA
Sent: Thu 1/18/2007 6:46 PM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] SMTP Connection Closed
Good questions!
Thor: I was referring to Exchange filtering NOT ISA. I was not aware of
the
NOOP config in the SMTP filter properties.
Amy: By client I mean another account with a separate ISP and Exchange
server
somewhere else in the world. i.e. NJ.
Joseph Danielsen, MCSA-Messaging, MCP
Network Blade Inc.
49 Marcy Street
Somerset, NJ 08873
732-213-0600
www.networkblade.com <http://www.networkblade.com/>
<https://harbor.bounceme.net/Exchange/amy/Drafts/RE:%20[isalist]%20SMTP%20Conn
ection%20Closed.EML/1_multipart/%20>
<https://harbor.bounceme.net/Exchange/amy/Drafts/RE:%20[isalist]%20SMTP%20Conn
ection%20Closed.EML/1_multipart/%20>
________________________________
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
On
Behalf Of Thor (Hammer of God)
Posted At: Thursday, January 18, 2007 6:40 PM
Posted To: ISA
Conversation: [isalist] SMTP Connection Closed
Subject: [isalist] Re: SMTP Connection Closed
Just to make sure we're saying the same thing.. Not filtering via
Exchange and
3rd party- the ISA SMTP filter. You disabled that?
t
On 1/18/07 3:30 PM, "ISA" <ISA@xxxxxxxxxxxxxxxx> spoketh to all:
Thor - thanks but I've turned off ALL filtering via Exchange and 3rd
party
software.
I've tried connecting (via telnet) from multiple locations (ISP) and from
Exchange 2003 and SBS 2003. Some work and Some don't. When watching the
ISA
real-time logs, the connection is initiated then 5 seconds later it is
then
closed by the Exchange publishing rule.
A 12-pack for the one who gets this one!
<and this is on my own server/network>
Joseph Danielsen, MCSA-Messaging, MCP
Network Blade Inc.
49 Marcy Street
Somerset, NJ 08873
732-213-0600
www.networkblade.com <http://www.networkblade.com/>
<http://www.networkblade.com/>
<https://harbor.bounceme.net/Exchange/amy/Drafts/RE:%20[isalist]%20SMTP%20Conn
ection%20Closed.EML/1_multipart/%20>
<https://harbor.bounceme.net/Exchange/amy/Drafts/RE:%20[isalist]%20SMTP%20Conn
ection%20Closed.EML/1_multipart/%20>
________________________________
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]
<mailto:isalist-bounce@xxxxxxxxxxxxx%5d> On Behalf Of Thor (Hammer of
God)
Posted At: Thursday, January 18, 2007 6:22 PM
Posted To: ISA
Conversation: [isalist] SMTP Connection Closed
Subject: [isalist] Re: SMTP Connection Closed
Check your SMTP filter settings for command lengths... NOOP has been
problematic before at its default of 6 - I changed mine to 20 after
sniffing
traffic and determining some older Exchange boxes were padding NOOP with
spaces..
t
On 1/18/07 1:46 PM, "ISA" <ISA@xxxxxxxxxxxxxxxx> spoketh to all:
Hope someone can help!
I think this is an ISA 2004 (patched) issue.
From some clients I can send/receive email just fine (and telnet port
25). But
from other clients I can not. I monitored the ISA logs and observed the
connection initiated then being closed.
From Exchange 2003 box I shut of IMF and GFI services - still not luck
receiving email or telnet'ing from a particular client.
Any ideas would be greatly appreciated.
Respectfully
Joseph Danielsen, MCSA-Messaging, MCP
Network Blade Inc.
49 Marcy Street
Somerset, NJ 0887
732-213-0600
