From field in Exchange 2007 Queue viewer showing up as <>

Hello,

To understand my problem, I must first describe my setup and intentions.

I'm currently trying to setup journaling to a cloud based archive vendor. In order to do this, I must use a mail enabled contact for my journaling rule journaling@journal.contoso.com (My normal mail domain is contoso.com, and journal.contoso.com is a non-routable domain).

In conjunction with the mail enabled contact, I have a send connector setup to route any mail destined for *@journal.contoso.com to our smarthost, archiving.smarthost.com.

Currently, we are sending journaled mail to the smarthost just fine. The problem is, some of these messages don't display the From Address correctly, they just show up as <>.

Upon further inspection, I determined that this is occurring in our queue viewer, and is not on the smarthosts end.

Here's where it gets weird. Exchange only does this with external email addresses, not internal, and it doesn't do it to all external address either; some of them show up just fine. On the messages missing the from field, I have verified that they are legit messages, not SPAM. I can see no difference between the messages where Exchange strips the From Address, and the ones where Exchange leaves it alone.

Currently, I have two servers running HT & CAS roles, two Edge servers, and a mailbox cluster.


Any ideas at all? It is greatly appreciated.
txgoalieAsked:
Who is Participating?
Advertise Here
 
txgoalieConnect With a Mentor Author Commented:
Scratch that, it is normal behavior. Everything sent to the journaling@journal.contoso.com address is sent via postmaster.

So, everything is sent to my cloud archive with a from address of <>, because it's not forwarding or relaying a message, it's actually a new message; the journal report. The postmaster sends the journal report, with the original message attached.

The issue is on my cloud archiving solution's end. They're not resolving all of the From Addresses.

Thanks for the feedback.
0
 
agonza07Commented:
0
 
AkhaterCommented:
These are DSN (Delivery Status Notification) messages -mostly NDRs and rejection messages etc...- there is nothing to worry about
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Put the Hammer Down
 
txgoalieAuthor Commented:
I can guarantee with 100% certainty that these are not NDR's, at least not all of them. I've verified the emails are good, from known good senders, and have checked with my users to verify the legitimacy of the mail.

What I've noticed is, when Exchange forwards the message to journaling@journal.contoso.com , it changes the sender address from the original sender, to a very long Exchange email address. The problem is, it does this for all journaled messages, good and bad.


Also, I appreciate the replies, sorry for not mentioning that already.
0
 
AkhaterCommented:
I didn't say they are all NDR's i told you these are DSN, if someone is sending an email and it was queued for a period of time for any reason it will also get a DSN.

Also you could see somtimes duplicates. i.e. the same email one with the correct sender showing and the other with just <> 

again, if we are not talking about 100's of them, i wouldn't worry about it
0
 
txgoalieAuthor Commented:
Fair enough, then by your explanation, what is happening seems to be that Exchange is using the DSN from address to send mail out of my send connector for journaling. I know this because my cloud archiving service is getting the <> messages with no duplicates with a good From Address.

For instance, under your theory, for every <> in my cloud archive, I should also be seeing a positive duplicate entry with a good From Address, but I don't. Only the <> messages appear.

So, is it normal for Exchange to use the DSN address to send the journal report?
0
 
txgoalieAuthor Commented:
This was the correct answer.
0
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.