Delivery Failure to FederatedEmail.4c1f4..... and DiscoverySearchMailbox

Users are getting a delivery failure message to these 2 system mailboxes (Exchange 2010) when they email a large distribution group. As far as I can tell these do not seem to be part of the said distribution group

 - FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@.......
 - DiscoverySearchMailbox{D919BA05-46A6-415f-80AD-7E09334BB852}@.....
sydlegAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Jon BrelieSystem ArchitectCommented:
Is this distribution group query based?  Was it possibly created under an earlier version of Exchange?

Try removing the group and recreating it.
sydlegAuthor Commented:
As I said they are not part of any group.
Jon BrelieSystem ArchitectCommented:
Right.  I'm talking about the distribution group that you specifically mentioned in your original question.  

Sending email to that group is what triggers the delivery failures to the other mailboxes, is it not?

Is that group query based, or possibly created on an earlier version of exchange?  Have you tried removing and recreating the distribution group?
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

sydlegAuthor Commented:
One of the groups is Dynamic but I did run the upgrade scripts for all the groups, contacts etc...they seem ok
Jon BrelieSystem ArchitectCommented:
Delete and recreate the group using the 2010 tools and see if the problem persists.

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
Jon BrelieSystem ArchitectCommented:
Wait, so do you get this error when you send email to a specific large distribution group, or when you use any large distribution group?

sydlegAuthor Commented:
Part of the issue was that when you create a Dynamic distribution group it automatically adds the omissions for these system mailboxes in the filter. When I converted these groups from Exchange 2003 server, the omissions were not added automatically as part of the conversion process
Jon BrelieSystem ArchitectCommented:
So what did you ultimately do to fix the issue?
sydlegAuthor Commented:
Your suggestion was a solution to the matter.

However, the point of my comment was to supply extra information for the cause of the issue, therefore providing others with another possible solution, which would be to alter the filter and not do a wholesale delete and recreate.
Jon BrelieSystem ArchitectCommented:
Gotcha.  Just curious.  Thank you for the clarification.
sydlegAuthor Commented:
No problemo matey :)
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
Exchange

From novice to tech pro — start learning today.