Adam's got the answer Sam. :) Joe Heaton ________________________________
From: Adam Hitchcock [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 01, 2008 1:09 PM To: MS-Exchange Admin Issues Subject: Re: Help: Can't send to Comcast.net?!? .net is the customers address while .com is the corporate address. On Tue, Apr 1, 2008 at 1:05 PM, Sam Cayze <[EMAIL PROTECTED]> wrote: Ah, cool, thanks :) Curious, is your home address comcast.net or .com? Oddly enough, I can send to comcast.com address just fine... -----Original Message----- From: Joe Heaton [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 01, 2008 2:57 PM To: MS-Exchange Admin Issues Subject: RE: Help: Can't send to Comcast.net?!? I understood that part Sam. Just meant that I tested it by sending an e-mail from my work address ([EMAIL PROTECTED]) and it went through. Your reply also mentioned that it could be specific outside domains (your ISP being one of them). Hope you get it sorted... Joe Heaton -----Original Message----- From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 01, 2008 12:23 PM To: MS-Exchange Admin Issues Subject: RE: Help: Can't send to Comcast.net?!? Yeah, it's kinda related to NON Comcast customers FYI. And it's ISP specific. I had a bunch of people do a 'telnet mx1.comcast.net 25' for me, and it worked for them. But for many of us who are SunGard customers, and have them as our ISP, it's not working... -----Original Message----- From: Joe Heaton [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 01, 2008 2:13 PM To: MS-Exchange Admin Issues Subject: RE: Help: Can't send to Comcast.net?!? I'm a Comcast customer, and have now successfully sent a message from my work address to my home address, and replied back out. Guess it's not all e-mail to Comcast, or they've fixed it. Joe Heaton -----Original Message----- From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 01, 2008 11:34 AM To: MS-Exchange Admin Issues Subject: RE: Help: Can't send to Comcast.net?!? So I got a hold of someone at Comcast, I guess that are getting flooded with calls about this, and they are telling people that we should use SMTP port 587 and authenticate before we can send email? I'm confused? I know that if you are a [EMAIL PROTECTED] customer, you need to configure your mail client to use these settings. But can they require outside organizations to do this? Aren't they bound by some RFC rules to allow unauthenticated smtp traffic on port 25? Plus, how in the heck would I even authenticate with them? Do I need to open an account? Wft? This can't be right... -Sam -----Original Message----- From: Sam Cayze [mailto:[EMAIL PROTECTED] Sent: Saturday, March 29, 2008 12:41 PM To: MS-Exchange Admin Issues Subject: RE: Help: Can't send to Comcast.net?!? FYI, it appears a few of the customers at our ISP have reported this same issue. Our ISP confirmed that the packets are being sent out from the ISP's internet Routers, but being dropped on the Comcast end. So now the pointing fingers game begins. -----Original Message----- From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED] Sent: Friday, March 28, 2008 4:05 PM To: MS-Exchange Admin Issues Subject: Re: Help: Can't send to Comcast.net?!? Oh no's! If this is accurate, Comcast's anti-spam is done by Symantec! http://www.comcastblacklist.com/?page_id=6 On Fri, Mar 28, 2008 at 3:17 PM, Micheal Espinola Jr <[EMAIL PROTECTED]> wrote: > Someone posted a very good question to that 'A, MX, PTR' blog article > since I posted the link. For those that are unfamiliar with PTR and > HELO filtering by anti-spam filters, you might want to check out the > question and my response(s). > > On Fri, Mar 28, 2008 at 1:37 PM, Micheal Espinola Jr > <[EMAIL PROTECTED]> wrote: > > > Oh how I wish I had the time to be a "blogger", but I did make time to > > comment on DNS issues with anti-spam products: > > > > http://www.espinola.net/blog/archives/5 > > > > Summary: Make sure you have accurate A, MX, and PTR records for your > > outbound server. > > > > > > On Fri, Mar 28, 2008 at 10:10 AM, Sam Cayze <[EMAIL PROTECTED]> wrote: > > > > > So, do mean like having your PTR and reverse DNS setup correctly, or > > > something related to the nameservers? > > > > > > I will relay that info back to my provider. It seems another one of our > > > ISP's customer has also reported the same issue. > > > Good to know John, thanks. > > > -Sam > > > > > > -----Original Message----- > > > From: Matteson, John H Jr USA Mr USA 25th SigBN (ITT) > > > [mailto:[EMAIL PROTECTED] > > > Sent: Friday, March 28, 2008 1:58 AM > > > To: MS-Exchange Admin Issues > > > > > > Subject: RE: Help: Can't send to Comcast.net?!? > > > > > > Make sure that you have all the appropriate DNS entries on the external > > > DNS server. Comcast is getting twitchy about accepting mail form certain > > > netblocks and domains. My home is wired to Comcast and they sometimes > > > reject mail from my domain here. > > > > > > If you need to, contact Comcast's corporate headquarters and have them > > > help in resolving the problem. > > > > > > > > > John H. Matteson, Jr. > > > Systems Administrator/ITT Systems > > > FOB Orgun-E > > > Afghanistan > > > DSN - 318 431 8001 > > > VoSIP - (308) 431 - 0000 > > > Iridium - 717.633.3823 > > > Roshain - 079 - 736 - 3832 > > > > > > "A man who thinks of himself as belonging to a particular national group > > > in America has not yet become an American. And the man who goes among > > > you to trade upon your nationality is no worthy son to live under the > > > Stars and Stripes." Woodrow Wilson > > > > > > > > > -----Original Message----- > > > From: Sam Cayze [mailto:[EMAIL PROTECTED] > > > Sent: Friday, March 28, 2008 1:53 AM > > > To: MS-Exchange Admin Issues > > > Subject: Help: Can't send to Comcast.net?!? > > > > > > 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 ~ > > > > > > ~ 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 ~ > > > > > > -- > ME2 > > ~ 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 ~ ~ 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 ~ ~ 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 ~ ~ 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 ~
