I posted this previously, but was hoping someone else might have run into it by now. I have two users who can't receive the email reports from Xeams. I even tried deleting the accounts in xeams and re-pulling them from Active Directory. What I don't understand is, it's only two users and based on the info I get from the bounce email from xeams(I monitor the admin email account for xeams), it's typically a dns failure. I can see that the messages hang in the outboundmailqueue before they fail. Here's the message I get to the admin account for xeams:

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

user email account .

Unable to send email to the server. 554 5.1.0 Sender denied

Remote host said: 221  landisoffice.com Service closing transmission channel

--- Below this line is a copy of the message.

 Date: Mon, 9 May 2016 07:01:44 -0400 (EDT)

 From: Xeams Admin Console <xeams admin email account>

 To: user email account

 Subject: Summary Email Report for May 9, 2016

I did find this information and by checking using powershell, the two users did have the account blacklisted. I did remove the entry at the exchange server and update the safelist at the server. I can even check the junklist and the entry for my xeams admin account has been removed. Is there something in xeams that may have picked up the setting? I see no blacklists under either user.

I'd post the link to the exchange article, but the forum wouldn't let me post the link or the article.

Since I made the changes to exchange, which was simply removing the xeams admin email address from the blocked senders for the affected users, now the emails do not fail at all, they stay in the outboundmailqueue forever. Would deleting the users in xeams and then re-importing them from active directory help? What log can I see why they are hanging in the outboundmailqueue?

So, this ended up being two problems. First, the two affected users had added my xeams admin address to their blocked senders list(don't ask me why). In the old days, this wouldn't matter, but the newer flavors of exchange actually track this and the info is stored on the server. This is why I was getting the bounce emails. I was able to use powershell to update the lists for both users. That stopped the ndr's. However, at that point the emails were staying in the outboundmailqueue forever. There was no mention of xeams trying to send the emails to the exchange server in the smtpoutboundconversation log. This was because I had deleted the two users accounts and re-imported them from active directory and instead of being sent to .com users, they were being sent to .local users. Once I updated the the users(manage users/associations) the reports were once again flowing. Hope this helps anyone having similar issues.