Hi everyone,
Paul Boven wrote:
One of my users just spotted a FN that had managed to slip trough.
They're abusing 70_sare_whitelist.cf, specifically:
whitelist_from_rcvd [EMAIL PROTECTED] vonage.com
# Vonage voice mail notification
I'm now catching these on several
Hi Justin, everyone,
Justin Mason wrote:
It's worth checking this; that rule should fire only if the
mail really *did* come from Vonage. I suspect a bug in how your
mailserver's Received headers are parsed.
Could you post:
- a sample of a spam that passed this, with all headers
- output
ok -- there's the bug ;) SpamAssassin is misinterpreting your
MX's Received headers.
Received: from vm.vonage.com ([220.166.39.177]) by amsfep14-int.chello.nl
(InterMail vM.6.01.04.04 201-2131-118-104-20050224) with SMTP
id [EMAIL PROTECTED]
for [EMAIL PROTECTED];
On Thu, Jul 13, 2006 at 11:21:09AM +0100, Justin Mason wrote:
ok -- there's the bug ;) SpamAssassin is misinterpreting your
MX's Received headers.
[...]
Could you open a bug on the SpamAssassin bugzilla about that? Attach
the debug output and sample again (it can be tricky to find posts to
Hi everyone,
One of my users just spotted a FN that had managed to slip trough.
They're abusing 70_sare_whitelist.cf, specifically:
whitelist_from_rcvd [EMAIL PROTECTED] vonage.com
# Vonage voice mail notification
Headers in question:
Received: from mta.example.com
-Original Message-
From: Paul Boven [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 06, 2006 8:17 AM
To: users@spamassassin.apache.org
Subject: Abuse of SARE whitelist
Hi everyone,
One of my users just spotted a FN that had managed to slip trough.
They're abusing
