I have some emails which are been deleted as spam and the AgentLog files contains the section
... Sender Id Agent,OnEndOfHeaders,DeleteMessage,,MissingPRA,No valid PRA,
I would like to configure Exchange 2007 not to reject emails from this particular domain.
I thought it was a matter of using the PowerShell command
Set-SenderIDConfig -BypassedSenderDomains domainname
but this does not seem to make any difference.
The domain in question does not have any SPF record set.
Any ideas?
For some multi-valued attributes, PowerShell does not have an "add" command that adds to the list.
For such attributes, use the following commands: $foo = get-contentfilterconfig
$foo.BypassedSenderDomains += somedomain.com
$foo | set-contentfilterconfig
To get a list of all bypassed domains: get-ContentFilterConfig | select BypassedSenderDomains
Hope this would help you
(I've dug up a few bookmarks for this, so I could be barking up the wrong tree)
The PRA is the 'Purported Responsbile Address' https://www.rfc-editor.org/rfc/rfc4407. It doesn't look for that until phase 5 of the message's run through the gauntlet of IMF http://technet.microsoft.com/en-us/library/aa997242(EXCHG.80).aspx; and it's a preulde to the SPF check.
I've never seen it listed as 'Missing' before, since it's Microsoft's own algorithm that's responsible for determining it. Perhaps an earlier phase has already rejected all of the recipients at the SMTP stage, leaving a directionless message that gets flagged for deletion. I don't think the sender domain whitelist applies at this point, though. If you can, try to catch a few messages from the sender as they come in and look at the SMTP conversations. Perhaps their MTA is mangling a standard header in a way that's causing this (unlikely, but it's where I'd look next).
I came across this old post while researching the same issue. Here's MS's answer: https://technet.microsoft.com/en-us/library/bb125259%28v=exchg.141%29.aspx
You may need to restart the transport service before the change takes effect.