Solved

Exchange 2010 now rejects any additional NEW mailboxes added

Posted on 2014-11-20
5
90 Views
Last Modified: 2014-11-25
We have a brand new SERVER install with Win 2008 R2 w/ Exchange 2010. The OS is activated, the Exchange is in trial mode right now. I can add users just fine in Active Directory and then subsequently add them to Exchange to create mailboxes successfully. Here is where I run into a roadblock.

The first 35 or so created work great. Now when I add additional, I can still authenticate with Outlook clients and even use mail2web.com to login to mailbox. However when I try to send an e-mail to it I get the ERROR below. The first 35 or so WORK fine still. So what has changed to cause this issue? Things I have tried I list below.

You do not have permission to send to this recipient.  For assistance, contact your system administrator.
    <mail.xxxxxxxxxxx.com #5.7.1 smtp;550 5.7.1 Recipient rejected (R4)>

1. I have rebooted server
2. I have deleted troublesome mailbox and added it back
3. I created a simple test@ account and it gives me same bounce message
0
Comment
Question by:interc3905
  • 3
  • 2
5 Comments
 
LVL 16

Expert Comment

by:Rajitha Chimmani
ID: 40455995
Do you have any antivirus installed, specifically AVG? If so, try disabling it.
0
 

Author Comment

by:interc3905
ID: 40456596
Virus protection is not the issue. As I said I am able to still send to first 35 accounts. Only the accounts I create going forward don't allow me to send to it now.
0
 

Accepted Solution

by:
interc3905 earned 0 total points
ID: 40456600
Duh! I finally figured out what the issue is. We use 3rd party GFI to filter all spam and viruses before it e-mails get delivered to the Exchange server. I had to add the SAME e-mail account in GFI to match the one on Exchange server - otherwise I get BOUNCE message. My mistake.
0
 

Author Comment

by:interc3905
ID: 40457436
I've requested that this question be closed as follows:

Accepted answer: 0 points for interc3905's comment #a40456600

for the following reason:

Found solution
0
 
LVL 16

Expert Comment

by:Rajitha Chimmani
ID: 40457437
This question cannot be closed with 0 points. Thought not exact answer, requester was pointed towards antivirus possibility.  Its not possible to provide realistic answers without knowledge of complete infrastructure.
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

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

Suggested Solutions

Read this checklist to learn more about the 15 things you should never include in an email signature.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create a Contact 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 Recipients >> Contact ta…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

828 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