Backup Exec To Exchange 2010 - Email Notification

Got a strange one.  I have a client with Backup Exec 2012.  I setup email notification so when a job fails, it will notify a user at the client site by email.

So I have a 2008 R2 server Running Exchange 2010, at a different location.
I can directly email them from my server no problem.
I setup Backup Exec with my exchange server settings, port 25, and the username and password of an email/AD account called backup.  I added myself as a recipient and did a test and I got it right away.  When I add the client user's email as a recipient and hit test, I see Backup Exec send it, see it flush through my Exchange server in the Message Queue but it never makes it to their inbox.  No error.

I must note that when I send all emails they seem to flush through a queue called SUBMISSION.  For this client they go through a queue called DNSCONNECTORDELIVERY for some reason.

Please suggest a solution..
PlatinumInfoAsked:
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.

AmitIT ArchitectCommented:
Where is client mailbox located. If it is an external user, then create a contact for client email address and send the email.
0
Hypercat (Deb)Commented:
You need to create a separate Receive connector on the Exchange server for the Backup Exec server.  The connector needs to use port 25 and allow connections from the IP address of the BE server.  Here's an example:

Exchange Receive connector for internal server relay
Use Basic Authentication and set the Permission groups to Exchange users.
0
Simon Butler (Sembee)ConsultantCommented:
If you are sending to an internal user, then you don't need a relay connector, because you aren't relaying.
You also don't need to authenticate to send the email.

As you are seeing the message in the queue, that says that Exchange is accepting the email, so the problem is further down. If you use message tracking, do you see the email there?

My instinct is that it is being blocked/dropped by a spam filter. I have seen that happen loads of times with backup applications.

Simon.
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
PlatinumInfoAuthor Commented:
Simon might be right.  To make things easy, I used the client's internal exchange server which worked just fine.
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
Windows Server 2008

From novice to tech pro — start learning today.