Bill Cole <> changed:

           What    |Removed                     |Added
                 CC|                            |sa-bugz-20080315@billmail.s
                   |                            |

--- Comment #4 from Bill Cole <> ---
(In reply to Michaƫl from comment #0)
> We have email send by local exchange to an other local server (Zimbra)
> protected by SpamAssassin
> But these mails are tag as SPAM

This is almost certainly a configuration error, not a SpamAssassin bug.

> When we check header, we can see that rules RCVD_IN_BRBL_LASTEXT is matched
> On Wiki ( 

As the name suggests, that rule checks the last "external" Received header. The
parsing of Received to decide whether a they are internal or external and
whether a they can be trusted as accurate is governed by 3 configuration
options that you MUST set correctly to get correct characterization of Received
headers by SpamAssassin: 


To be certain of what address SpamAssassin is checking you need to check a
misidentified message using the SpamAssassin configuration which misidentified
it, with the option '-D metadata,received-header' so that you get
SpamAssassin's debug messages regarding its classification of Received headers.

The most likely problem is that the IP address of your Exchange server needs to
be included in *all three* of those network lists. If it is not, SpamAssassin
may detect the submission of mail to the Exchange server as an 'external'
transport step and check the address from that Received header against the BRBL
and other DNSBLs.

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

Reply via email to