Receive Connector on Exchange 2010 Std.

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
jaihoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SurajCommented:
Instead of using a relay connector. try adding the IP in the IP allow list. once done restart transport and then test.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
compdigit44Commented:
Have you installed any Windows OS or Exchange updates recently?
0
jaihoAuthor Commented:
@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
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

compdigit44Commented:
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
SurajCommented:
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
compdigit44Commented:
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
jaihoAuthor Commented:
@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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.