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..
Who is Participating?
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.

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

All Courses

From novice to tech pro — start learning today.