RE: Hosting Multiple domains in Exchange 2003

2008-06-06 Thread Jonathan Gruber
I am using zoneedit.com to host the DNS for all of the sites, I made the changes to these 2 domains, along with 5 others over 3 weeks ago. I haven't changed any entries since then so it worries me that you saw different A records. We are doing the actual hosting of the sites. When pinging

RE: Hosting Multiple domains in Exchange 2003

2008-06-06 Thread Jason Gurtz
This is much more than rumor. In addition to regex style filters that look for generic/dynamic looking PTRs, more and more sites are also blocking if the PTR does not match the A. The later is nothing new -- it's called a double reverse lookup. That's been around since at least the

RE: Hosting Multiple domains in Exchange 2003

2008-06-05 Thread Jonathan Gruber
-Exchange Admin Issues Subject: Re: Hosting Multiple domains in Exchange 2003 On Wed, Jun 4, 2008 at 10:36 AM, Jonathan Gruber [EMAIL PROTECTED] wrote: Still having the same issue with shirevalleydesign.com and mail to bellsouth.net. Hmmm. I just tried running some test probes against

RE: Hosting Multiple domains in Exchange 2003

2008-06-05 Thread Jason Gurtz
Postscript: I do notice that 67.91.139.138 reverses to ip67-91-139-138.z139-91-67.customer.algx.net.. I've heard rumor that some spam filters will consider suspicious any IP address with a reverse DNS that looks like that. This is much more than rumor. In addition to regex style filters

Re: Hosting Multiple domains in Exchange 2003

2008-06-05 Thread Micheal Espinola Jr
+1 to everything that Jason wrote. These conditions are only going to become worse. It behooves you to get with the program sooner than later. Put your DNS ducks in a line. On Thu, Jun 5, 2008 at 11:34 AM, Jason Gurtz [EMAIL PROTECTED] wrote: Postscript: I do notice that 67.91.139.138

Re: Hosting Multiple domains in Exchange 2003

2008-06-05 Thread Ben Scott
On Thu, Jun 5, 2008 at 11:34 AM, Jason Gurtz [EMAIL PROTECTED] wrote: This is much more than rumor. In addition to regex style filters that look for generic/dynamic looking PTRs, more and more sites are also blocking if the PTR does not match the A. The later is nothing new -- it's called a

Re: Hosting Multiple domains in Exchange 2003

2008-06-05 Thread Ben Scott
On Thu, Jun 5, 2008 at 12:17 PM, Jonathan Gruber [EMAIL PROTECTED] wrote: Here is the log entry, seems like it might be blacklisted, but I can't find any blacklist that lists us. 2008-06-05 14:02:15 207.115.11.16 OutboundConnectionResponse SMTPSVC1 VM2 - 25 - -

RE: Hosting Multiple domains in Exchange 2003

2008-06-04 Thread Jonathan Gruber
. 610-944-8840  x.213 484-637-1978  direct -Original Message- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 03, 2008 11:18 AM To: MS-Exchange Admin Issues Subject: Re: Hosting Multiple domains in Exchange 2003 On Fri, May 30, 2008 at 8:33 AM, Jonathan Gruber [EMAIL

RE: Hosting Multiple domains in Exchange 2003

2008-06-04 Thread Andy Shook
04, 2008 10:36 AM To: MS-Exchange Admin Issues Subject: RE: Hosting Multiple domains in Exchange 2003 Still having the same issue with shirevalleydesign.com and mail to bellsouth.net. The other 2 domains are moyersconstruction.com and sealcoatmydrive.com . Turns out in doing some more looking

Re: Hosting Multiple domains in Exchange 2003

2008-06-04 Thread Ben Scott
On Wed, Jun 4, 2008 at 10:36 AM, Jonathan Gruber [EMAIL PROTECTED] wrote: Still having the same issue with shirevalleydesign.com and mail to bellsouth.net. Hmmm. I just tried running some test probes against the MXes for bellsouth.net. From a real ISP feed, I connected no problem, and got

Re: Hosting Multiple domains in Exchange 2003

2008-06-04 Thread Ben Scott
On Wed, Jun 4, 2008 at 10:26 PM, Ben Scott [EMAIL PROTECTED] wrote: ... mail.{shirevalleydesign,moyersconstruction,sealcoatmydrive}.com (67.91.139.138), and both came out clean. Valid PTR records also exist ... Postscript: I do notice that 67.91.139.138 reverses to

Re: Hosting Multiple domains in Exchange 2003

2008-06-03 Thread Ben Scott
On Fri, May 30, 2008 at 8:33 AM, Jonathan Gruber [EMAIL PROTECTED] wrote: Ok I've removed the 2 PTD DNS servers, but my DNS checks still show them listed and mail is still failing. I removed them Wednesday 5/28, I figured 24 hours the propagate but this morning their still showing up for me.

Re: Hosting Multiple domains in Exchange 2003

2008-05-27 Thread Ben Scott
On Fri, May 23, 2008 at 11:20 AM, Jonathan Gruber [EMAIL PROTECTED] wrote: A user has sent an email to a bellsouth account using domainb which is also hosted on this server and the mail is timing out. What's the exact error message? Have you checked Event Viewer for more info? Have you

RE: Hosting Multiple domains in Exchange 2003

2008-05-27 Thread Jonathan Gruber
-Exchange Admin Issues Subject: Re: Hosting Multiple domains in Exchange 2003 On Fri, May 23, 2008 at 11:20 AM, Jonathan Gruber [EMAIL PROTECTED] wrote: A user has sent an email to a bellsouth account using domainb which is also hosted on this server and the mail is timing out. What's the exact

RE: Hosting Multiple domains in Exchange 2003

2008-05-27 Thread Don Andrews
.us.messagelabs.com not sure where you got mail.bellsouth.com -Original Message- From: Jonathan Gruber [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 2:18 PM To: MS-Exchange Admin Issues Subject: RE: Hosting Multiple domains in Exchange 2003 DomainB is shirevalleydesign.com DNS entries are correct

RE: Hosting Multiple domains in Exchange 2003

2008-05-27 Thread Don Andrews
[mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 2:39 PM To: MS-Exchange Admin Issues Subject: RE: Hosting Multiple domains in Exchange 2003 It looks to me like bellsouth.com uses messagelabs. bellsouth.com MX preference = 20, mail exchanger = cluster7a.us.messagelabs.com bellsouth.com

Re: Hosting Multiple domains in Exchange 2003

2008-05-27 Thread Ben Scott
On Tue, May 27, 2008 at 5:17 PM, Jonathan Gruber [EMAIL PROTECTED] wrote: ESM error message is An SMTP protocol error occurred. That's closer to a real cause. The server you're trying to send to is replying with something your server doesn't like. I'm guessing Exchange thinks the error is a

RE: Hosting Multiple domains in Exchange 2003

2008-05-23 Thread Michael B. Smith
You just need to verify that reverse DNS for all the domains is correct. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Jonathan Gruber [mailto:[EMAIL PROTECTED] Sent: Friday, May 23, 2008 11:20 AM To: MS-Exchange Admin Issues Subject: Hosting

RE: Hosting Multiple domains in Exchange 2003

2008-05-23 Thread Don Andrews
I think the reverse dns only needs to point to a host record - not aware of any requirement that it contains the sending domain. You might want to ensure your MX for domainb points to the correct host. From: Jonathan Gruber [mailto:[EMAIL PROTECTED] Sent: