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/02/13 14:34:38 UTC
Re: Vbounce ruleset whitelist_bounce_relays
Steve [Spamassassin] writes:
> I've been trying to use the Vbounce ruleset
> [http://wiki.apache.org/spamassassin/VBounceRuleset] on spamassassin 3.1.4.
>
> I'm unable to get whitelist_bounce_relays to work... When I
> intentionally send an email to a non-existent remote address I get a
> bounce message marked exactly as if it had been a bogus bounce.
>
> Does anyone have whitelisted bounces working with vbounce?
could you post an example of your config and the message you're testing
with, in full?
--j.
Re: Vbounce ruleset whitelist_bounce_relays
Posted by Jeremy Fairbrass <jf...@hotmail.com>.
Hi Justin,
What exactly is the fix, and where do I find it?
I just installed the VBounce plugin on my server this weekend (for the first time), and have the same probs described here - ie.
although I've added my server to whitelist_bounce_relays in local.cf, I'm not getting the MY_SERVERS_FOUND rule firing when I
deliberately cause my server to generate a bounce message back to me.
One question I do have: does MY_SERVERS_FOUND look for the existance of my server's name within the headers of the bounce message
itself, or only within the body of the bounce message (ie. where the original message might be)? In my case, the bounce message body
does NOT contain the original message nor any reference to my server name, however my server name is obviously mentioned in the
headers of the bounce message itself, and I'd have hoped that this would cause MY_SERVERS_FOUND to fire.
Anything I can do to correct this?
Cheers,
Jeremy
"Justin Mason" <jm...@jmason.org> wrote in message news:20070214130650.BB66232CD9@radish.jmason.org...
>
> Matt Kettler writes:
>> Steve [Spamassassin] wrote:
>> > Justin Mason wrote:
>> >> could you post an example of your config and the message you're testing
>> >> with, in full?
>> > OK.... in /etc/mail/spamassassin/local.cf
>>
>> > Received: by mail.mydomain.com (Postfix) id EFBE62E48F; Wed, 7 Feb
>> > 2007 12:57:43 +0000 (GMT)
>>
>> Nice.. A Received: header with no from clause.
>>
>> My guess is that the whitelist isn't working because it thinks this
>> message came from nowhere at all. In an environment where your outbound
>> SMTP server is also your MX, all bounce messages you get will be
>> received by mail.mydomain.com, but only locally generated bounces will
>> come from it.
>
> Actually, this is definitely a bug :(
> http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5331
> I've added a fix to work around it in SVN.
>
> --j.
>
Re: Vbounce ruleset whitelist_bounce_relays
Posted by "Steve [Spamassassin]" <sp...@shic.co.uk>.
Matt Kettler wrote:
>> Received: by mail.mydomain.com (Postfix) id EFBE62E48F; Wed, 7 Feb
>> 2007 12:57:43 +0000 (GMT)
>>
>
> Nice.. A Received: header with no from clause.
>
I'm glad you like it, though I don't think I can take all the credit...
this is generated by an almost vanilla (Gentoo) Postfix install. :-)
> My guess is that the whitelist isn't working because it thinks this
> message came from nowhere at all. In an environment where your outbound
> SMTP server is also your MX, all bounce messages you get will be
> received by mail.mydomain.com, but only locally generated bounces will
> come from it.
I think I follow that logic. The _vast_ majority of my bounces are
expected to be locally generated. I suppose for those I could just
alter the standard text to include some random string then match that
with a body rule... but it seems an extremely ugly way of going about
things... and I can't be 100% sure that all of my bounces will be
locally generated. For example, someone I email may have configured
catch-all addresses on their backup mail-server... and only generate
bounces when the main mail-server fetches mail from the backup
mail-server - say - during office hours. I'd not want to miss a bounce
message under those circumstances.
Would I be right in thinking that you're suggesting that this is a
shortcoming of the vbounce ruleset... or... is this a glitch in my
configuration? If the latter, can you offer any pointer as to how I
should have set things up? You are right to assume that I've a single
postfix mail-server which is both referenced by my MX record for mail to
the domain and the same server is used to send all outgoing mail from
the domain.
Re: Vbounce ruleset whitelist_bounce_relays
Posted by Matt Kettler <mk...@verizon.net>.
Steve [Spamassassin] wrote:
> Justin Mason wrote:
>> could you post an example of your config and the message you're testing
>> with, in full?
> OK.... in /etc/mail/spamassassin/local.cf
> Received: by mail.mydomain.com (Postfix) id EFBE62E48F; Wed, 7 Feb
> 2007 12:57:43 +0000 (GMT)
Nice.. A Received: header with no from clause.
My guess is that the whitelist isn't working because it thinks this
message came from nowhere at all. In an environment where your outbound
SMTP server is also your MX, all bounce messages you get will be
received by mail.mydomain.com, but only locally generated bounces will
come from it.
Re: Vbounce ruleset whitelist_bounce_relays
Posted by "Steve [Spamassassin]" <sp...@shic.co.uk>.
Justin Mason wrote:
> could you post an example of your config and the message you're testing
> with, in full?
OK.... in /etc/mail/spamassassin/local.cf
--
allow_user_rules 1
bayes_auto_expire 0
whitelist_bounce_relays mail.mydomain.com
--
A bounce message which should have been whitelisted:
----cut----
Return-Path: <>
X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on
server.mydomain.com
X-Spam-Level: ***
X-Spam-Status: No, score=3.7 required=5.0 tests=ANY_BOUNCE_MESSAGE,AWL,
BAYES_99,BOUNCE_MESSAGE autolearn=no version=3.1.4
X-Original-To: steve@mydomain.com
Delivered-To: steve@mydomain.com
Received: by mail.mydomain.com (Postfix) id EFBE62E48F; Wed, 7 Feb 2007
12:57:43 +0000 (GMT)
Date: Wed, 7 Feb 2007 12:57:43 +0000 (GMT)
From: MAILER-DAEMON@mydomain.com (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: myuser@mydomain.com
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="6DFA62E3AF.1170853063/mail.mydomain.com"
Message-Id: <20...@mail.mydomain.com>
This is a MIME-encapsulated message.
--6DFA62E3AF.1170853063/mail.mydomain.com
Content-Description: Notification
Content-Type: text/plain
This is the Postfix program at host mail.mydomain.com.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to <postmaster>
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The Postfix program
<th...@lineone.net>:
host mx1.uk.tiscali.com[212.74.100.152] said: 550 RCPT
TO:<th...@lineone.net>
User unknown (in reply to RCPT TO command)
--6DFA62E3AF.1170853063/mail.mydomain.com
Content-Description: Delivery report
Content-Type: message/delivery-status
Reporting-MTA: dns; mail.mydomain.com
X-Postfix-Queue-ID: 6DFA62E3AF
X-Postfix-Sender: rfc822; steve@mydomain.com
Arrival-Date: Wed, 7 Feb 2007 12:57:38 +0000 (GMT)
Final-Recipient: rfc822;
this_account_really_doesnt_exist_I_hope_bounce_test_64837368593897376383@lineone.net
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; host mx1.uk.tiscali.com[212.74.100.152]
said: 550
RCPT
TO:<th...@lineone.net>
User unknown (in reply to RCPT TO command)
--6DFA62E3AF.1170853063/mail.mydomain.com
Content-Description: Undelivered Message
Content-Type: message/rfc822
Received: from [127.0.0.1] (localhost [127.0.0.1])
by mail.mydomain.com (Postfix) with ESMTP id 6DFA62E3AF
for
<th...@lineone.net>;
Wed, 7 Feb 2007 12:57:38 +0000 (GMT)
Message-ID: <45...@mydomain.com>
Date: Wed, 07 Feb 2007 12:57:36 +0000
From: Steve <st...@mydomain.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To:
this_account_really_doesnt_exist_I_hope_bounce_test_64837368593897376383@lineone.net
Subject: Test 6...
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Doah!
--6DFA62E3AF.1170853063/mail.mydomain.com--
----cut----