Setup: Microsoft Exchange Server 2007 running on Windows Server 2003 x64 (member server). Network solutions hosts the web and email accounts. Email is downloaded to the Exchange server using a POP3 connector. Email is sent from the exchange server using a smart host setting. Messages are relayed to Network Solutions to be sent to external domains.
We are currently having trouble sending to one email address. This problem only started when i moved them to the exchange server - previously they had POP accounts setup in Outlook and used Network Solutions for email and had no trouble sending to the one address.
I have listed the details of the error message below:
Diagnostic information for administrators:
Generating server: omr2.networksolutionsemail
user@OUTSIDEDOMAIN.com
#< #4.4.7 SMTP; 450 Service temporarily unavailable for xxx.xxx.xxx.xxx (the IP address is for our domain hosted by network solutions) Please try again later.> #SMTP#
Original message headers:
Return-Path: <user@mydomain.com>
Received: from mail.networksolutionsemail
[10.49.6.65]) by omr2.networksolutionsemail
m1IK1KdC013084 for <user@OUTSIDEDOMAIN.com>; Mon, 18 Feb 2008 15:01:21
-0500
Received: (qmail 27942 invoked by uid 78); 18 Feb 2008 20:01:19 -0000
Received: from unknown (HELO Exchange01.FUEL.local) (admin@mydomain.com@x.x.x.
by ns-omr2.lb.hosting.dc2.net
Received: from Exchange01.FUEL.local ([192.168.10.30]) by
Exchange01.FUEL.local ([192.168.10.30]) with mapi; Mon, 18 Feb 2008 14:59:44
-0500
From: user <user@mydomain.com>
To: "'user'" <
user@OUTSIDEDOMAIN.com>
Date: Mon, 18 Feb 2008 14:59:44 -0500
Subject: RE:
Thread-Index: AchyT8vV1PMB2MHDQ4WMsaAM/E
Message-ID: <1CB6782E475F344BA349B6A25
In-Reply-To: <6E78EDD88F86C44BB9F0831CB
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative;
boundary="_000_1CB6782E475
MIME-Version: 1.0
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Could you suggest another domain register that I should use? I have several small clients who use exchange and who relay email through their hosting provider. I would LOVE to come up with a long term solution that is practically fool-proof.
I have also started using Auth SMTP to relay email, but that does not solve the SPF problem.
THANKS
Business Accounts
Answer for Membership
by: Syngin9Posted on 2008-02-20 at 05:53:12ID: 20937711
There are any number of reasons this could be happening (i'm going to assume that the problem isn't just with one email account but either the full domain in question or the entire server)
1) Greylisting - This message is generally something greylisting would respond with. Generally, greylisting just delays reception of an email from a server it hasn't seen before. Its a relatively effective additional spam defense and a number of spamming server don't try again after the first failure. I think the standard wait time is usually around 2 minutes but it can be set to anything by the admin.
Bear in mind that many error messages can be defined by the admin so it may also be one of the following resulting in this message:
- Blacklisting - if the external ip is listed in a public blacklist that the server in question accesses, this could be the reason for the drop. Go to http://www.senderbase.org and run a check on your external ip to see.
- SPF (and DomainKeys) - The server might be rejecting email because your server is failing SPF checks. Netsol doesn't allow TXT records in the DNS entries so you wouldn't even be able to designate an SPF (or DomainKeys) record. This was the reason I moved all of my domains away from Netsol a few months ago. Both are very necessary if you ever send email out to Yahoo, Gmail or AOL and don't want to end up in the bulk folder.
- standard MF check - A very basic check that ensures that there is an MX record for the domain in the MAIL FROM address.
I've even had email originating from a new serverI built denied based on Senderbase's reputation score
Finally, it could be just as it says, perhaps they are doing a restructuring or were experiencing email problems. Are you able to give their admin a call?