https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8280
Bill Cole <billc...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |billc...@apache.org
--- Comment #2 from Bill Cole <billc...@apache.org> ---
The sample message passes for me:
Content preview: NecroTek Jonathan Maberry Go to your Holds in the app or on
our OverDrive site to borrow this title. DON'T WANT THIS TITLE YET? You can
suspend the hold to stay on the wait list without the title becoming
available
for you. When the suspension ends, your hold will be active and you'll be
notified whe [...]
Content analysis details: (-0.2 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from
envelope-from domain
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's
domain
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
valid
0.0 HTML_MESSAGE BODY: HTML included in message
0.0 MIME_BASE64_TEXT RAW: Message text disguised using base64 encoding
0.0 MSGID_FROM_MTA_HEADER Message-Id was added by a relay
-0.0 T_SCC_BODY_TEXT_LINE No description available.
This sounds like a problem with UDP truncation and TCP fallback. If your
resolver fails to do TCP fallback or is firewall-blocked, very large TXT
responses will break SPF.
--
You are receiving this mail because:
You are the assignee for the bug.
