On 01/15/2019 09:36 AM, Bill Cole wrote:
Check both the contents and documentation of trusted_networks, msa_networks, and internal_networks.
Will do.
If SA thinks a prior hop is through a machine that writes trustworthy Received headers and is a normal part of your relay path, it will check SPF there.
SA is running at the inbound Internet edge. There are no other hosts that are part of my organization.
There MAY be a design bug there. I'm not sure how SA deals with a machine you trust and which is a normal inbound relay that also is SPF-approved for mail it gets from other places. Maybe msa_networks can solve this.
I don't think this is applicable when SA is at the inbound Internet edge. I'll check the referenced documentation as soon as time permits. Thank you Bill. -- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
