You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2007/07/20 14:34:20 UTC
Re: Vbounce and Shortcircuit hitting read receipts ?
Yep, this is entirely possible; I don't think I tested with any
read receipts :(
--j.
neil writes:
> Hi;
> Any one else seeing random FPs with VBounce rules and short circuit
> as described here:
> http://wiki.apache.org/spamassassin/ShortcircuitingRuleset
>
> # bounce messages: always ignored if the vbounce plugin is active
> priority ANY_BOUNCE_MESSAGE -700
> shortcircuit ANY_BOUNCE_MESSAGE spam
> score ANY_BOUNCE_MESSAGE 20
>
> On another box without the short circuit rule, the message gets a low
> score as would be expected.
>
> I have whitelist_bounce_relays configured with my mail servers.
>
> (I have replaced the sender and recipients names and email addresses and
> removed a couple of others in the receipt list.)
>
> spamassassin -D < /tmp/recipt.txt1
> <snip>
> [7710] dbg: shortcircuit: s/c spam due to ANY_BOUNCE_MESSAGE, using
> score of 100
> [7710] dbg: check: is spam? score=20.1 required=15
> [7710] dbg: check: tests=ANY_BOUNCE_MESSAGE,BOUNCE_MESSAGE
> [7710] dbg: check: subtests=__BOUNCE_CTYPE,__HAVE_BOUNCE_RELAYS
> <snip>
>
> from 20_vbounce.cf
> body __HAVE_BOUNCE_RELAYS eval:have_any_bounce_relays()
> tflags __HAVE_BOUNCE_RELAYS nice
>
> header __BOUNCE_CTYPE Content-Type =~ /\bmultipart\/report\b/
>
>
>
> Content analysis details: (20.1 points, 15.0 required)
>
> pts rule name description
> ---- ----------------------
> --------------------------------------------------
> 0.1 BOUNCE_MESSAGE MTA bounce message
> 20 ANY_BOUNCE_MESSAGE Message is some kind of bounce message
>
>
>
> Received: from aamtaout01-winn.ispmail.ntl.com ([81.103.221.35])
> by mtaout03-winn.ispmail.ntl.com with ESMTP
> id
> <20...@aamtaout01-winn.ispmail.ntl.com>
> for <re...@example.com>; Fri, 20 Jul 2007 11:12:01 +0100
> Received: from sendershome ([82.19.189.159])
> by aamtaout01-winn.ispmail.ntl.com with SMTP
> id
> <20...@sendershome>
> for <re...@example.com>; Fri, 20 Jul 2007 11:12:01 +0100
> Message-ID: <00...@sendershome>
> From: "Some Sender" <se...@senderdomain.example.com>
> To: "Some Recipient" <re...@example.com>
> References: <00...@user8b4965acfc>
> Subject: Read: My e mail
> Date: Fri, 20 Jul 2007 11:11:59 +0100
> MIME-Version: 1.0
> Content-Type: multipart/report;
> boundary="----=_NextPart_000_003F_01C7CABE.CA6E6D20";
> report-type=disposition-notification
> X-Mailer: Microsoft Outlook Express 6.00.2900.3138
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_003F_01C7CABE.CA6E6D20
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> This is a receipt for the mail you sent to
> "Sender Sender" <se...@senderdomain.example.com> at 20/07/2007 10:55
>
>
> This receipt verifies that the message has been displayed on the =
> recipient's computer at 20/07/2007 11:11
> ------=_NextPart_000_003F_01C7CABE.CA6E6D20
> Content-Type: message/disposition-notification
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> Final-Recipient: rfc822;recipient@example.com
> Original-Message-ID: <00...@user8b4965acfc>
> Disposition: manual-action/MDN-sent-manually; displayed
>
> ------=_NextPart_000_003F_01C7CABE.CA6E6D20--
>
>
>
> ------=_NextPart_000_00C9_01C7CAC7.493F3410--
Re: Vbounce and Shortcircuit hitting read receipts ?
Posted by neil <ne...@supanet.net.uk>.
Hi;
Just commented out the short circuit vbounce rule on the box I did
the tests on and I get a low score (3.3). I dont know if you want to
test this and update the wiki or if I should raise it as a bug.
I'd better remove that rule from my production boxen. Changes to
live servers, on a Friday afternoon. What could possibly go wrong ;-)
Rgds
N.
Justin Mason wrote:
> Yep, this is entirely possible; I don't think I tested with any
> read receipts :(
>
> --j.
>
> neil writes:
>
>> Hi;
>> Any one else seeing random FPs with VBounce rules and short circuit
>> as described here:
>> http://wiki.apache.org/spamassassin/ShortcircuitingRuleset
>>
>> # bounce messages: always ignored if the vbounce plugin is active
>> priority ANY_BOUNCE_MESSAGE -700
>> shortcircuit ANY_BOUNCE_MESSAGE spam
>> score ANY_BOUNCE_MESSAGE 20
>>
>> On another box without the short circuit rule, the message gets a low
>> score as would be expected.
>>
>> I have whitelist_bounce_relays configured with my mail servers.
>>
>> (I have replaced the sender and recipients names and email addresses and
>> removed a couple of others in the receipt list.)
>>
>> spamassassin -D < /tmp/recipt.txt1
>> <snip>
>> [7710] dbg: shortcircuit: s/c spam due to ANY_BOUNCE_MESSAGE, using
>> score of 100
>> [7710] dbg: check: is spam? score=20.1 required=15
>> [7710] dbg: check: tests=ANY_BOUNCE_MESSAGE,BOUNCE_MESSAGE
>> [7710] dbg: check: subtests=__BOUNCE_CTYPE,__HAVE_BOUNCE_RELAYS
>> <snip>
>>
>> from 20_vbounce.cf
>> body __HAVE_BOUNCE_RELAYS eval:have_any_bounce_relays()
>> tflags __HAVE_BOUNCE_RELAYS nice
>>
>> header __BOUNCE_CTYPE Content-Type =~ /\bmultipart\/report\b/
>>
>>
>>
>> Content analysis details: (20.1 points, 15.0 required)
>>
>> pts rule name description
>> ---- ----------------------
>> --------------------------------------------------
>> 0.1 BOUNCE_MESSAGE MTA bounce message
>> 20 ANY_BOUNCE_MESSAGE Message is some kind of bounce message
>>
>>
>>
>> Received: from aamtaout01-winn.ispmail.ntl.com ([81.103.221.35])
>> by mtaout03-winn.ispmail.ntl.com with ESMTP
>> id
>> <20...@aamtaout01-winn.ispmail.ntl.com>
>> for <re...@example.com>; Fri, 20 Jul 2007 11:12:01 +0100
>> Received: from sendershome ([82.19.189.159])
>> by aamtaout01-winn.ispmail.ntl.com with SMTP
>> id
>> <20...@sendershome>
>> for <re...@example.com>; Fri, 20 Jul 2007 11:12:01 +0100
>> Message-ID: <00...@sendershome>
>> From: "Some Sender" <se...@senderdomain.example.com>
>> To: "Some Recipient" <re...@example.com>
>> References: <00...@user8b4965acfc>
>> Subject: Read: My e mail
>> Date: Fri, 20 Jul 2007 11:11:59 +0100
>> MIME-Version: 1.0
>> Content-Type: multipart/report;
>> boundary="----=_NextPart_000_003F_01C7CABE.CA6E6D20";
>> report-type=disposition-notification
>> X-Mailer: Microsoft Outlook Express 6.00.2900.3138
>> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
>>
>> This is a multi-part message in MIME format.
>>
>> ------=_NextPart_000_003F_01C7CABE.CA6E6D20
>> Content-Type: text/plain;
>> charset="iso-8859-1"
>> Content-Transfer-Encoding: quoted-printable
>>
>> This is a receipt for the mail you sent to
>> "Sender Sender" <se...@senderdomain.example.com> at 20/07/2007 10:55
>>
>>
>> This receipt verifies that the message has been displayed on the =
>> recipient's computer at 20/07/2007 11:11
>> ------=_NextPart_000_003F_01C7CABE.CA6E6D20
>> Content-Type: message/disposition-notification
>> Content-Transfer-Encoding: 7bit
>> Content-Disposition: inline
>>
>> Final-Recipient: rfc822;recipient@example.com
>> Original-Message-ID: <00...@user8b4965acfc>
>> Disposition: manual-action/MDN-sent-manually; displayed
>>
>> ------=_NextPart_000_003F_01C7CABE.CA6E6D20--
>>
>>
>>
>> ------=_NextPart_000_00C9_01C7CAC7.493F3410--
>>
>
>