Solved

Receive Connector on Exchange 2010 Std.

Posted on 2012-03-18
7
578 Views
Last Modified: 2012-03-21
Hi Folks,

I have an Exchange Server 2010 std. edition. It was all working fine for almost 10 months and suddenly what happened is, any mails coming from outside was rejected

The sender receives the following message:
Delivery has failed to these recipients or groups:
'User Name (user@xyz.com)'
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.
The following organization rejected your message: receivingservername@xyz.com.
Diagnostic information for administrators:
Generating server: servername.abc.com
user@xyz.com
receivingservername.domain.com #550 5.7.1 Recipient not authorized, your IP has been found on a block list ##
======================================================================================

No changes been made to the receive connector except for the permission groups which has all the options checked except Partners. This change was done after the installation of the exchange on the default receive connectors.

Since I was not receiving emails, I did checked my firewall, spam suite and nothing seems to have problem, as I continue to have the problem even after disabling the spam suite.
Finally, I created a new custom receive connector, set the IP address as local IP with port 25. Checked only the Externally Secured (IPSec) option under the authentication and permission group as default, by this I started getting emails, but the sad part is, I get to lots of spammers in the mail queue and looks really ugly. When the newly created connector is disabled, removing the spam domains in the queue, it looks fine but unable to receive mails and again when enabled, all goes for six...

I have another domain in my office with exchange 2010, I copied the same settings for the receive connectors (on the default ones created during exchange installation), but doesn't work. Works only when I enable the new connector.

Your resolution is highly appreciated.

Thanks,
Anand
0
Comment
Question by:jaiho
  • 3
  • 2
  • 2
7 Comments
 
LVL 17

Accepted Solution

by:
Suraj earned 250 total points
ID: 37736537
Instead of using a relay connector. try adding the IP in the IP allow list. once done restart transport and then test.
0
 
LVL 19

Expert Comment

by:compdigit44
ID: 37738376
Have you installed any Windows OS or Exchange updates recently?
0
 

Author Comment

by:jaiho
ID: 37745855
@x-sam: Tried that, no mails coming + no bounce error mail coming for the sender

@compdigit44: It happened on 8th March 2012, during that time, there was no windows / Exchange updates except for Windows Defender.
0
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 19

Assisted Solution

by:compdigit44
compdigit44 earned 250 total points
ID: 37747118
I like to work with the mind set what changed from the time something work until it stopped working. You stated nothing has changed hardware wise and not Windows OS or Exchange updates were installed. Did you try to removed the latest Windows Deferener updates or disable windows defender as a test?
0
 
LVL 17

Expert Comment

by:Suraj
ID: 37747954
Please upload the agent.log. for me.
Also please tell me what have you configured on ip block list provider agent?

I suspect some thing miss-configured on BlockListProvider Agent.
Meanwhile, as for a quick troubleshooting step try  to disable IP block list providers , restart transport and then test.
0
 
LVL 19

Expert Comment

by:compdigit44
ID: 37748299
Have you checked the following:

-Open the Exchange Management Console.
  -Expand Server Configuration and select Hub Transport.
  -Right click on Default <Server Name> and select Properties.
-Click on Permission Groups.
 -Ensure Anonymous Users is checked and click Apply and then OK.
- Restart the Microsoft Exchange Transport service.
0
 

Author Closing Comment

by:jaiho
ID: 37750938
@x-sam: Added the neccessary IP address in the IP allow list for spam

@compdigit44: Disabled the Win Defender

- Worked like charm... Thanks so much techies. Happy to learn a lot on this... :)
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

790 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question