I think I found the reason.
using 'co.delaware.pa.us'
us - TLD
pa.us - TLD
delaware.pa.us - invalid !!!
co.delaware.pa.us - valid
pa.us is a TLD - but there are also sub domains registered as TLD like
cc.pa.us or lib.pa.us (and others) - BUT not delaware.pa.us
The really strange thing is, that
I hear yah loud and clear on the nxdomain for the stupid Navy subdomains.
I'm sure it's a valid subdomain internally and they just aren't thinking
when emailing out Forget about that one, it's clearly a
misconfiguration on their end.
But the multiple co.county.status.us domain problem is
ASSP does nothing else than ask YOUR DNS-server for 'ANY' DNS-entry. If
the DNS-server answers with 'NXDOMAIN' , there is no doubt for assp, that
this domain/host does'nt exist. This is NOT allowed in SMTP
>I know that submail.navy.mil isn't valid
So - using 'submail.navy.mil' in SMTP IS A
Terminology mixed me up I guess. Was thinking as the "domain name" as
what's registered with the registrar. What's being checked, I'd call the
"hostname" <-- but I'm wrong according to the RFC. Sorry for that.
I know that submail.navy.mil isn't valid, but navy.mil certainly is.
Shouldn't ASSP
Hi all,
fixed in assp 2.5.2 build 16096:
- improved performance for high workload systems
- better garbage detection for the HMM and Bayesian engine
changed:
- if a message is scored in SMTP-handshake and/or header and noprocessing
and/or whitelisting is detected
in the body check, the
On 05/04/16 16:00, K Post wrote:
> And
> submail.navy.mil
>
if that is domain in the address then that is what should be checked.
If you look at the code -
if (exists($RFC822dom{lc $dom}) || (${defined
*{'yield'}} && defined($ns = getRRData(${defined *{'yield'}}, (defined
This problem hasn't gone away and it only seems to be with hostnames that
have more than 2 parts -
For example:
co.delaware.pa.us
resolves just fine on the dns servers
co.delaware.pa.us MX preference = 10, mail exchanger =
co-delaware-pa-us.mail.protection.outlook.com
