RE: xobni invites
As do I thanks to Bob's generosity. Email off-list of you need one. Jonathan Gruber Network Administrator J.B. Long Inc. 610-944-8840 x.213 484-637-1978 direct -Original Message- From: Andrew Greene [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 2:06 PM To: MS-Exchange Admin Issues Subject: RE: xobni invites Same here, also have 6 invites. E-mail me off list. -Original Message- From: James Kerr [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 11:34 AM To: MS-Exchange Admin Issues Subject: Re: xobni invites I thought everyone would be xobnied up by now but I have 6 invites folks can have. James - Original Message - From: "Micheal Espinola Jr" <[EMAIL PROTECTED]> To: "MS-Exchange Admin Issues" Sent: Thursday, April 24, 2008 11:27 AM Subject: Re: xobni invites > All my invites are gone. Thanks for playing! :-) > > > -- > 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~
Setting up Email to allow web forms
I've tried googling this but I'm not even sure what to search for. Several web sites we host are wanting to use PHP forms on their sites. So far I've been unable to get the forms to work as I get a "relaying is prohibited" response on the page. By relaxing the settings on the exchange server I can get the form to work but I'm basically an open relay which I can't allow. Can I setup the server to allow these forms and not be an open relay or should the php code be written differently to be able to authenticate? Jonathan Gruber Network Administrator J.B. Long Inc. 610-944-8840 x.213 484-637-1978 direct ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
Hosting Multiple domains in Exchange 2003
We are currently hosting multiple domains on an exchange 2003 box and have run into an issue. We set up the box using domain a, and the fqdn listed in the virtual smtp server is mail.domaina.com. 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. When a test is sent from domain to the bellsouth.net address it goes through, so I assume that the reverse dns lookup bellsouth is doing is failing. My question is, what is the best way to resolve this, multiple virtual servers, configure external dns servers? I haven't had an issue sending mail to any other domains except bellsouth.net. Jonathan Gruber Network Administrator J.B. Long Inc. 610-944-8840 x.213 484-637-1978 direct ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Hosting Multiple domains in Exchange 2003
DomainB is shirevalleydesign.com DNS entries are correct as far as I can tell. ESM error message is "An SMTP protocol error occurred." I get a delay message and then a failure message "Could not deliver the message in the time limit specified." I can't telnet into mail.bellsouth.net from that server, but I also tried to telnet from a different location and couldn't there either. Jonathan Gruber Network Administrator J.B. Long Inc. 610-944-8840 x.213 484-637-1978 direct -Original Message- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 11:18 AM To: MS-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 error message? Have you checked Event Viewer for more info? Have you tried using Exchange SMTP diagnostic logging? Have you tried doing the SMTP dialog manually with the TELNET command? > When a test is sent from domain to the bellsouth.net > address it goes through, so I assume that the reverse dns lookup bellsouth > is doing is failing. That doesn't sound like a reverse lookup issue. Reverse lookup is done against the IP address of your mail server. If the problem was with that, it would affect all mail sent from your mail server, regardless of the sender domain name. It might be that the forward lookup of your "domainb.com" is slow or faulty. Many SMTP servers check the name submitted in MAIL FROM for validity, so a DNS problem there can cause trouble. If you let us know the actual "domainb.com", we could check it. -- Ben ~ 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~
RE: Hosting Multiple domains in Exchange 2003
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. In addition I've just learned that email from our main company is failing to reach 2 other domains that are hosted on this exchange server. I am getting "unable to bind to the destination server in DNS" at our main companies exchange server when trying send mail to the affected exchange box. 12 domains hosted on this box and I'm only having trouble with 3 and not even the same problem. DNS entries are correct for all of the domains. Jonathan Gruber Network Administrator J.B. Long Inc. 610-944-8840 x.213 484-637-1978 direct -Original Message- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 10:44 PM To: MS-Exchange Admin Issues Subject: Re: Hosting Multiple domains in Exchange 2003 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 temporary one, and thus queues the mail for retry later. The timeout message you're getting is Exchange saying, "I've tried several times now, and it still won't go through; I'm giving up". It might be useful to see a transcript of the SMTP session, but before you go to the trouble: > DomainB is shirevalleydesign.com It appears you have some lame delegations (that's the actual technical term) in your DNS zone. When a DNS resolver encounters a lame delegation, it usually fails the lookup (returns SERVFAIL). Any MX that gets that result will consider the domain non-existent and reject it. Good money says that's your problem. The GTLD SOA nameserver shows the following delegations for your domain: $ dig +noall +ans NS shirevalleydesign.com. @a.gtld-servers.net shirevalleydesign.com. 172800 IN NS dns3.ptd.net. shirevalleydesign.com. 172800 IN NS dns4.ptd.net. shirevalleydesign.com. 172800 IN NS ns3.zoneedit.com. shirevalleydesign.com. 172800 IN NS ns7.zoneedit.com. $ The two ZoneEdit servers respond with zone information, but the ptd.net servers respond with a referral back to the root. That means those servers believe they are not authoritative for the domain. (Hence "lame delegation"; you've delegated authority to servers which do not believe they are authoritative.) $ dig +noall +ans +auth ANY shirevalleydesign.com. @dns3.ptd.net com.116724 IN NS i.gtld-servers.net. com.116724 IN NS j.gtld-servers.net. com.116724 IN NS k.gtld-servers.net. com.116724 IN NS l.gtld-servers.net. com.116724 IN NS m.gtld-servers.net. com.116724 IN NS a.gtld-servers.net. com.116724 IN NS b.gtld-servers.net. com.116724 IN NS c.gtld-servers.net. com.116724 IN NS d.gtld-servers.net. com.116724 IN NS e.gtld-servers.net. com.116724 IN NS f.gtld-servers.net. com.116724 IN NS g.gtld-servers.net. com.116724 IN NS h.gtld-servers.net. $ Fix your DNS and try again. Either configure the two ptd.net nameservers with zone information, or remove them as registered nameservers for your domain. -- Ben ~ 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~
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, we can't access the web sites internally either. Jonathan Gruber Network Administrator J.B. Long Inc. 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 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. For a change of registered name servers, you have to wait for: 1. The registrar reseller to process the change (if you're using a reseller (but many registration services are really just resllers)) 2. The registrar to process the change 3. The registry to process the change 4. TTL to expire on any cached records The TTL on the GTLD zones is 48 hours, so you're generally waiting at least two days. Some resellers/registrars can be slow, so 70 or 80 hours is not unheard of. In any event, the domain looks like it's okay right now. Both registered nameservers are responding properly, and both return the same zone information. Are you still having trouble sending mail to/from them? > In addition I've just learned that email from our main company is failing to > reach 2 other domains that are hosted on this exchange server. [...] > DNS entries are correct for all of the domains. No offense, but you said that before and you were wrong then. :-) Post the domain names, and I or others can investigate. The more information you give people, the more likely someone will be able to help you. -- Ben ~ 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~
RE: Hosting Multiple domains in Exchange 2003
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
- - 550-67.91.139.138+blocked+by+ldap:ou=rblmx,dc=bellsouth,dc=net 0 0 62 0 260
SMTP - - - -
For the other 2 sites I am immediately kicked to a google search which lists
the site as the only result. Clicking on the link gives me a page can not be
displayed messagehowever just now when I tried to verify the errors I had
no trouble accessing the site if I use www. If I just type in
sealcoatmydrive.com it gives me the google run around, but both are in the host
header value in IIS.
Jonathan Gruber
Network Administrator
J.B. Long Inc.
610-944-8840 x.213
484-637-1978 direct
-Original Message-
From: Ben Scott [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2008 10:26 PM
To: MS-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 the MXes for
. From a "real" ISP feed, I connected no problem, and
got immediate "OK" responses to MAIL
FROM:<[EMAIL PROTECTED]>. I tried multiple probes
against both listed MXes.
However, from my home Comcast feed, I get a hangup before HELO, with
the message that I'm blacklisted. It's a 550 code. I'm not sure if
Exchange will consider that a permanent failure or not. If not, and
you're blacklisted by them, that would explain the delay-then-failure
you're seeing. Try turning on SMTP protocol logging to record a
transcript of the SMTP session, and see if bellsouth is rejecting you.
If you're not familiar with SMTP protocol logging, this article
explains it pretty well:
http://www.msexchange.org/tutorials/Exchange-Server-2003-Mailflow-Part-2.html
You may want to check the IP address your mail server will be
sending from to see if it is on any blacklists. I like the site
http://www.mxtoolbox.com/blacklists.aspx for doing that. FWIW, I did
run the address your list post came from (24.229.89.2) and the one
returned for mail.{shirevalleydesign,moyersconstruction,sealcoatmydrive}.com
(67.91.139.138), and both came out clean. Valid PTR records also
exist for both.
> The other 2 domains are moyersconstruction.com and sealcoatmydrive.com .
DNS looks good to me. The delegation chain is valid, and I get
consistent answers from all nameservers. I also ran ZoneCheck
(http://www.zonecheck.fr) against them and it didn't find anything
serious. It warned that postmaster@ the domains isn't working, which
isn't good, but if BellSouth was rejecting on that they would
presumably do so all the time. (Still, you should probably fix your
postmaster mailbox.)
> Turns out in doing some more looking, we can't access the
> web sites internally either.
Not being able to access the web sites probably isn't good, but may
or may not be related to your mail problems. What happens when you
try the web sites? Name resolution fails, connection times out, HTTP
server error, something else...?
-- Ben
~ 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~
RE: Hosting Multiple domains in Exchange 2003
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 these 2 sites I get "could not find host" Nslookup hits our DNS server and returns a "non-existent domain" even after clearing the cache. I can telnet to the hosting system on port 80 no problem, in addition this same system is hosting other sites which I can access without any trouble. I really think it's a DNS issue and I'm beginning to think it's with our ISP. I use the same ISP for my cable modem at home and have the same issues accessing the sites, however the coffee shop I visit in the morning uses Verizon DSL and I never have an issue getting to any of the sites we host. Turns out something is hosed with our ISP's DNS server. They are currently looking into it. Jonathan Gruber Network Administrator J.B. Long Inc. 610-944-8840 x.213 484-637-1978 direct As I recall, last night, a lookup for vs returned two different A records. Likewise for . It might have been a mistake on the part of whoever you have doing your hosting. Right now, I get the same A record for both of them, so perhaps it has been fixed. Try again. If it still does it: 1. Clear your browser cache. 2. Use PING to compare the IP addresses the various different domain names are resolving too. 3. If you find a discrepency in step 1, use NSLOOKUP to chase the DNS resolution chain back to where the problem is, and clear the DNS resolver cache of the offending system. 4. Try using TELNET to make a manual TCP connection on port 80, and see if you can get through that way. For step 4, if you're not familiar with the procedure, read <http://usertools.plus.net/tutorials/id/21>, section entitled "Checking a web server". -- Ben ~ 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~
