https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805

hnsupport <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #5 from hnsupport <[email protected]> ---
(In reply to Giovanni Bechis from comment #1)
> I cannot reproduce it, the output of a spamassassin check for the attached
> message follows:
> -----------------------------------------------------------------------------
> -
> Content analysis details:   (1.4 points, 5.0 required)
> 
>  pts rule name              description
> ---- ----------------------
> --------------------------------------------------
>  0.1 TO_MALFORMED           To: has a malformed address
>  0.0 SPF_HELO_NONE          SPF: HELO does not publish an SPF Record
> -0.0 SPF_PASS               SPF: sender matches SPF record
>  0.0 HTML_MESSAGE           BODY: HTML included in message
>  1.1 KAM_REALLYHUGEIMGSRC   RAW: Spam with image tags with ridiculously
>                              huge http urls
>  0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not
> necessarily
>                             valid
>  0.1 DKIM_INVALID           DKIM or DK signature exists, but is not valid
>  0.0 UNPARSEABLE_RELAY      Informational: message has unparseable relay
>                             lines
>  0.0 KAM_DMARC_STATUS       Test Rule for DKIM or SPF Failure with Strict
>                             Alignment
> -----------------------------------------------------------------------------
> -
> Which Mail::SPF version are you using ?
> Other than that I think a there could be a dns-related problem in your setup.
> Please follow
> https://cwiki.apache.org/confluence/display/SPAMASSASSIN/DnsBlocklists#dnsbl-
> block to fix at least SURBL_BLOCKED warning.


spamassassin and spf module versions:

[root@spamd-node0 ~]# perl -MMail::SPF -e 'print $Mail::SPF::VERSION ."\n";'
v2.009
[root@spamd-node0 ~]# perl -MMail::SpamAssassin -e 'print
$Mail::SpamAssassin::VERSION ."\n";'
3.004004

I don't think the debug output I included is indicative of a DNS issue...
considering the header is selected before spamassassin called Mail::SPF to
evaluate that RFC1918 IP.

Will check out that wiki regardless.

Can you show me your debug output upon testing this message (-D flag) for my
own reference?  Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to