Hi Www_w_,
There are several causes why users receive NDR when sending emails. NDRs include a code that indicates why your email isn’t delivered, you can refer to the list in this article.
In your case, the emails you send have an invalid sender address (null sender), so it would be rejected by Office 365. Sometimes a rejected message will appear as “550 5.7.512 Access denied, message must be RFC 5322 section 3.6.2 compliant and include a valid From address”. This is an expected behavior, as the NDR cannot be sent back to the sender whose address is invalid. Therefore, NDR will not be sent and it will be “discarded”
We appreciate your understanding and patience.
Best Regards,
Ruel
Any idea why some users that send internal mail from Exchange online has their "from" address being seen as a null sender.
A simple test mail with a subject "Test Mail" from some users will show in the logs as a null sender, thus failing any authentication methods with 3rd party SMTP services.
Hi Www_w_,
There are several causes why users receive NDR when sending emails. NDRs include a code that indicates why your email isn’t delivered, you can refer to the list in this article.
In your case, the emails you send have an invalid sender address (null sender), so it would be rejected by Office 365. Sometimes a rejected message will appear as “550 5.7.512 Access denied, message must be RFC 5322 section 3.6.2 compliant and include a valid From address”. This is an expected behavior, as the NDR cannot be sent back to the sender whose address is invalid. Therefore, NDR will not be sent and it will be “discarded”
We appreciate your understanding and patience.
Best Regards,
Ruel
Thank you very much.
Please teach me.
>NDR will not be sent and it will be “discarded”
Exchange server have undeliverable queue and later, the NDR threw away?
Or when the message is null sender, Exchange server discard soon?
Well, and please teach me.
When my tenant's exchange server makes the NDR, exchange server send external smtp server the exchange online's NDR.
And exchange server discards the original message of external smtp server.
Is my understanding correct?
Please teach me.
The original message discard soon? Or is there the original message in exchange server's queue?
This URL is Exchange 2010.
https://technet.microsoft.com/en-US/library/bb232161%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396
This URL is Exchange 2013
https://technet.microsoft.com/en-US/library/bb125022(v=exchg.150).aspx
Well.....So, I think. Maybe, exchange online stores the discard message in "Unreachable queue" too**.**
Undeliverable
NULL alongside my email address
NULL alongside my email address
Anyone else using exchange online seeing emails with null in the body?
c# - Outlook.MailItem.Sender is null- to fetch From email address - Stack Overflow
Hi Admins,
Today from around 11.05 GMT we're intermittently receiving external email to outlook client/outlook online with the body stripped and replaced with null.
Checking Mimecast I can see the body content. Is anyone else seeing this behavior?
Cheers,
Joe
P.S We've turned off CyberGraph in mimecast as per advice from 5tubbo in other post. So far so good. May help some of you out. :)
Sender related properties are only set after the message is actually sent. Try to use the Items.ItemAdd event on the Sent Items folder (retrieved using Namespace.GetDefaultFolder).
If SendUsingAccount property is not set, you can assume the default account is being used - use the first account from the Namespace.Accounts collection and retrieve the Account.SmtpAddress property.
http://social.msdn.microsoft.com/Forums/vstudio/en-US/38d7b25a-8762-40c6-9e0a-903549462c0b/outlookmailitemsendername-always-null-under-outlook-2007-wvsto?forum=vsto
Short answer: those items aren't populated until it's actually sent (this hook is when you are just about to send the command to the exchange server to send the email). Use the "SendUsingAccount" field instead, as it will have all that information (in addition to the information you can find in the user's mailbox/account objects).
I'm pretty sure the reason why is that those field are not filled in until dynamic rules and policies are applied server-side.
for the last hour we have been receiving emails with null in the email body text
searching mimecast for these emails shows the full correct body text and forwarding them back to the original destination works.
is anyone aware of why this is happening? its not just one mailbox within our tenant and it is not happening to just one sender or mail system/tenant