ja ja, I missed that bit for some reason. You're of course right that the problem is before that.
You proved already that DNS resolution and using the IP directly have no effect, so there is some sort of stoppage or filtering. that is taking place before thier mail server. I'd do some networking tracing to see if I couldnt target a specific network segment. On Thu, Mar 27, 2008 at 5:48 PM, Sam Cayze <[EMAIL PROTECTED]> wrote: > Can I send commands if the connection is never made? > > I assume the people in the nt-list that replied to my "telnet > mx1.comcast.net 25" favor did just that, and told me if they got a > response. > > I am by no means that familiar with telnet and smtp handshakes FYI. But > it seems to me that I am not even reaching them... > > > > > -----Original Message----- > From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED] > > Sent: Thursday, March 27, 2008 4:42 PM > To: MS-Exchange Admin Issues > Subject: Re: Help: Can't send to Comcast.net?!? > > When you telnet, are you sending out any verbs (commands) as a test? > Start with "HELO server.domain.org". Some filters wont give an > intitial server response until you have sent a verb. > > Comcast has such a filter. > > > On Thu, Mar 27, 2008 at 5:32 PM, Sam Cayze <[EMAIL PROTECTED]> > wrote: > > Well right now my mail server is the only system behind our firewall > > that allows SMTP traffic. > > So I tested it from our mail server... > > > > " Look at your queue. Find the msg thats at the top of it (the first > > that should go out), and freeze or delete it." > > > > Not sure what that will do yet if I can't talk to Comcast yet... But > > good trick to know. > > > > > > > > > > > > > > > > -----Original Message----- > > From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED] > > Sent: Thursday, March 27, 2008 4:26 PM > > To: MS-Exchange Admin Issues > > Subject: Re: Help: Can't send to Comcast.net?!? > > > > Did you perform your telnet tests from your mail server or a different > > system? > > > > Look at your queue. Find the msg thats at the top of it (the first > > that should go out), and freeze or delete it. > > > > > > > > On Thu, Mar 27, 2008 at 5:23 PM, Sam Cayze <[EMAIL PROTECTED]> > > wrote: > > > All emails to Comcast are building up in our Queues and triggering > > delay > > > notifications. > > > > > > This is what I have tried: > > > DNS Flush > > > Verify our dns cache for Comcast.net matches that reported on > > > dnsstuff.com. > > > > > > A telnet connection to Comcast MX servers times out/no response. > (And > > a > > > few find folks on the nt-list verified for me that mx1.comcast.net > is > > > indeed 'putting out'). > > > I tried a telnet right to the IPs too. > > > > > > I kind of figured we are blacklisted, but from what I have heard > > Comcast > > > will actually send you an NDR back with an abuse message. > > > Update: Just heard back from their abuse dept (in like 5 minutes - > > > damn!) - we are NOT blacklisted. > > > > > > > > > Ideas?!? ISP Problem? > > > > > > -Sam > > > > > > > > > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > > > ~ http://www.sunbeltsoftware.com/Ninja ~ > > > > > > > > > > > -- > > ME2 > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > > ~ http://www.sunbeltsoftware.com/Ninja ~ > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > > ~ http://www.sunbeltsoftware.com/Ninja ~ > > > > > > -- > ME2 > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > ~ http://www.sunbeltsoftware.com/Ninja ~ > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > ~ http://www.sunbeltsoftware.com/Ninja ~ > -- ME2 ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
