FAFCU
asked on
Exchange 2010 NDR Sender is Blank
Our mail filter is blocking outgoing messages that should be NDR b/c the sender is blank. We don't want to allow blank senders through so we've got to figure out how to fill in his field. We have one Exchange server, one domain and no Edge Transport Server. Here's the troubleshooting that I've done:
- The External Postmaster Address has been set to mailadmin@domainname in the EMC under Organization Configuration>Hub Transport>Global Settings
- The address has been verified using Get-TransportConfig | Format-List ExternalPostmasterAddress
- The mailadmin address is tied to a mailbox of the same name and user account in AD of the same name
Thanks for your time and assistance.
- The External Postmaster Address has been set to mailadmin@domainname in the EMC under Organization Configuration>Hub Transport>Global Settings
- The address has been verified using Get-TransportConfig | Format-List ExternalPostmasterAddress
- The mailadmin address is tied to a mailbox of the same name and user account in AD of the same name
Thanks for your time and assistance.
Step1: you can view the internet header files. so that you will know sending domain ip address. after that you can add the blocked ip address in your antispam agent
Step2: you can block the subject wise through transport rule, if subject is "XXXXXXXXXXXXXXXX" action should be delete or you can add the content filter.
Step2: you can block the subject wise through transport rule, if subject is "XXXXXXXXXXXXXXXX" action should be delete or you can add the content filter.
ASKER
@wsewasim & @vijayhackers
Thank-you for the information, but the information provided doesn't apply to what we're trying to accomplish. The problem isn't the mail filter, the problem is that the NDR messages being sent out have a blank Sender field when it shouldn't be.
Thank-you for the information, but the information provided doesn't apply to what we're trying to accomplish. The problem isn't the mail filter, the problem is that the NDR messages being sent out have a blank Sender field when it shouldn't be.
What NDRs are you sending out?
If the server is configured correctly you shouldn't be sending out ANY NDRs. That causes backscatter and can get you blacklisted.
You should be doing recipient filtering at the gateway. That is whatever answered email from the internet - it could be Exchange it could be something else.
Then the only other NDRs could be mailbox full. Again these should be happening at the point of delivery.
Simon.
If the server is configured correctly you shouldn't be sending out ANY NDRs. That causes backscatter and can get you blacklisted.
You should be doing recipient filtering at the gateway. That is whatever answered email from the internet - it could be Exchange it could be something else.
Then the only other NDRs could be mailbox full. Again these should be happening at the point of delivery.
Simon.
ASKER
Simon
The recent cases have been outside organizations attempting to send us e-mails but the attachments exceed the size of the allowed parameters on the Exchange server. In those cases, our employees were not receiving the messages but the sender didn't receive a bounce back message to let them know that their message was not delivered.
Eventually, we were able to track down the "missing" e-mails reported by our employees, but had the NDR gone out the way it was supposed to, we would have found the cause a lot sooner.
The recent cases have been outside organizations attempting to send us e-mails but the attachments exceed the size of the allowed parameters on the Exchange server. In those cases, our employees were not receiving the messages but the sender didn't receive a bounce back message to let them know that their message was not delivered.
Eventually, we were able to track down the "missing" e-mails reported by our employees, but had the NDR gone out the way it was supposed to, we would have found the cause a lot sooner.
If blank senders are being blocked, then the product blocking them is not following the relevant RFCs. NDRs always have blank senders, that is by design and they shouldn't be blocked.
Simon.
Simon.
ASKER
If NDRs always have blank senders than that's the piece of information I was missing. My understanding was that the NDR would use the External Postmaster Address, postmaster@domainname by default, unless you changed it to something else, which we did (mailadmin@domainname).
Internal NDRs are controlled by the postmaster setting. However external NDRs are not, because they are usually rejected at the point of delivery. If you have a size restriction then this should be controlled on the gateway, then you wouldn't have this problem.
Simon.
Simon.
ASKER
Simon
I just did an internal test and the NDR came from Microsoft Outlook, not the External Postmaster Address.
If I'm understanding this correctly, what I'm reading here: http://technet.microsoft.com/en-us/library/bb430765(v=exchg.141).aspx, is contradicting what you're saying.
"The external postmaster address is used as the sender for system-generated messages and notifications sent to message senders that exist outside the Microsoft Exchange Server 2010 organization. An external sender is any sender that has an e-mail address that contains a domain not defined in the list of accepted domains for the Exchange 2010 organization."
I apologize if I'm being dense, but it just doesn't seem logical for the NDRs to send external messages with a blank sender. My understanding is that NDRs fall under the "system-generated messages" category and they should be using the External Postmaster Address. If what you're saying is correct, that external NDRs are not controlled by the postmaster setting, then I don't understand what purpose the External Postmaster Address serves?
I just did an internal test and the NDR came from Microsoft Outlook, not the External Postmaster Address.
If I'm understanding this correctly, what I'm reading here: http://technet.microsoft.com/en-us/library/bb430765(v=exchg.141).aspx, is contradicting what you're saying.
"The external postmaster address is used as the sender for system-generated messages and notifications sent to message senders that exist outside the Microsoft Exchange Server 2010 organization. An external sender is any sender that has an e-mail address that contains a domain not defined in the list of accepted domains for the Exchange 2010 organization."
I apologize if I'm being dense, but it just doesn't seem logical for the NDRs to send external messages with a blank sender. My understanding is that NDRs fall under the "system-generated messages" category and they should be using the External Postmaster Address. If what you're saying is correct, that external NDRs are not controlled by the postmaster setting, then I don't understand what purpose the External Postmaster Address serves?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Simon
I've done a couple internal tests and the NDR comes from Microsoft Outlook, not the External Postmaster Address.
I've done a couple internal tests and the NDR comes from Microsoft Outlook, not the External Postmaster Address.
Block messages that don't have sender information To block messages that don't have sender information, select this check box.
http://technet.microsoft.com/en-us/library/bb125179(v=exchg.141).aspx