You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Jari Fredriksson <ja...@iki.fi> on 2009/05/19 20:59:16 UTC

BOUNCE_MESSAGE problem

 
I get lots of false  BOUNCE_MESSAGES from VBounce-plugin.

Sample: http://www.pastebin.ca/1427728

local.cf:

whitelist_bounce_relays wellington.fredriksson.dy.fi smtp.localnet.fi posti.saunalahti.fi

Those my local server and two smarthosts it uses.

What might be wrong here?



Re: BOUNCE_MESSAGE problem

Posted by Jari Fredriksson <ja...@iki.fi>.
> On Tue, May 19, 2009 22:28, Karsten Bräckelmann wrote:
> 
>> Sorry, but that's just utterly wrong. See my previous
>> post. 
> 
> List-Unsubscribe:
> <ma...@infoserver.investtech.com> 
> 
> is wroung too ? :)

I'm a subscriber of that list.

And the mail is not a BOUNCE or any kind.


Re: BOUNCE_MESSAGE problem

Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Tue, 2009-05-19 at 22:37 +0200, Benny Pedersen wrote:
> On Tue, May 19, 2009 22:28, Karsten Bräckelmann wrote:
> 
> > Sorry, but that's just utterly wrong. See my previous post.
> 
> List-Unsubscribe: <ma...@infoserver.investtech.com>
> 
> is wroung too ? :)

What's that got to do with it? Mind having a look at the To: and first
Delivered-To: headers?

Or, well, just for fun -- you also could have a look at 20_vbounce.cf
and VBounce.pm, like *I* did. Then you can verify my reasoning, why
VBounce jumped on the message.


Anyway, fetchmail does not rewrite List-Unsubscribe headers.  And I
don't feel like snapping at you again. So, please, just leave this
thread alone.


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}


Re: BOUNCE_MESSAGE problem

Posted by Benny Pedersen <me...@junc.org>.
On Tue, May 19, 2009 22:28, Karsten Bräckelmann wrote:

> Sorry, but that's just utterly wrong. See my previous post.

List-Unsubscribe: <ma...@infoserver.investtech.com>

is wroung too ? :)


-- 
http://localhost/ 100% uptime and 100% mirrored :)


Re: BOUNCE_MESSAGE problem

Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Tue, 2009-05-19 at 22:18 +0200, Benny Pedersen wrote:
> On Tue, May 19, 2009 21:40, Jari Fredriksson wrote:
> 
> > err.. So why does VBounce mark is as BOUNCE? It is not a bounce.
> 
> spamassassin see it as a mail sent localy if i remember how fetchmail
> headers confuse it

Bullshit!


OK, let me try this again, politely and politically correct... Benny,
you're remembering incorrectly.

Sorry, but that's just utterly wrong. See my previous post.


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}


Re: BOUNCE_MESSAGE problem

Posted by Benny Pedersen <me...@junc.org>.
On Tue, May 19, 2009 21:40, Jari Fredriksson wrote:

> err.. So why does VBounce mark is as BOUNCE? It is not a bounce.

spamassassin see it as a mail sent localy if i remember how fetchmail
headers confuse it

> Does it mark all fetchmailed mail as BOUNCE_MESSAGE?

yes its related

try debug it

spamassassin 2>&1 -D -t fetchmail.msg

-- 
http://localhost/ 100% uptime and 100% mirrored :)


Re: BOUNCE_MESSAGE problem

Posted by Michelle Konzack <li...@tamay-dogan.net>.
Am 2009-05-19 22:40:54, schrieb Jari Fredriksson:
> > On Tue, May 19, 2009 20:59, Jari Fredriksson wrote:
> > 
> >> What might be wrong here?
> > 
> > fetchmail
> > 
> > bounces do not make sense in rfc1918
> 
> err.. So why does VBounce mark is as BOUNCE? It is not a bounce.
> 
> Does it mark all fetchmailed mail as BOUNCE_MESSAGE?

I had the same problem when I had forgotten to use "set invisibel".

Thanks, Greetings and nice Day/Evening
    Michelle Konzack
    Systemadministrator
    25.9V Electronic Engineer
    Tamay Dogan Network
    Debian GNU/Linux Consultant

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
<http://www.tamay-dogan.net/>                 Michelle Konzack
<http://www.can4linux.org/>                   Apt. 917
<http://www.flexray4linux.org/>               50, rue de Soultz
Jabber linux4michelle@jabber.ccc.de           67100 Strasbourg/France
IRC #Debian (irc.icq.com)                     Tel. DE: +49 177 9351947
ICQ #328449886                                Tel. FR: +33  6  61925193

Re: BOUNCE_MESSAGE problem

Posted by Karsten Bräckelmann <gu...@rudersport.de>.
> > > What might be wrong here?
> > 
> > fetchmail

Please feel free to ignore Benny.

> Does it mark all fetchmailed mail as BOUNCE_MESSAGE?

No, it does not.

And unless your fetchmail is setting the Return-Path, it is not related
to fetchmail in any way. SA works just fine with fetchmail, and even
understands its specific markup for auto-detection of internal networks.


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}


Re: BOUNCE_MESSAGE problem

Posted by Jari Fredriksson <ja...@iki.fi>.
> On Tue, May 19, 2009 20:59, Jari Fredriksson wrote:
> 
>> What might be wrong here?
> 
> fetchmail
> 
> bounces do not make sense in rfc1918

err.. So why does VBounce mark is as BOUNCE? It is not a bounce.

Does it mark all fetchmailed mail as BOUNCE_MESSAGE?



Re: BOUNCE_MESSAGE problem

Posted by Benny Pedersen <me...@junc.org>.
On Tue, May 19, 2009 20:59, Jari Fredriksson wrote:

> What might be wrong here?

fetchmail

bounces do not make sense in rfc1918

-- 
http://localhost/ 100% uptime and 100% mirrored :)


Re: BOUNCE_MESSAGE problem

Posted by Jari Fredriksson <ja...@iki.fi>.
> On Wed, 2009-05-20 at 02:42 +0300, Jari Fredriksson wrote:
>> Another one. This is from Washington Post. Still with
>> fetchmail. http://wwww.pastebin.ca/1427982
>> 
>> Marked as BOUNCE.
>> 
>>     meta __BOUNCE_RPATH_NULL  0
>> 
>> should be working.
> 
> $ spamassassin --cf="meta __BOUNCE_RPATH_NULL 0" <
> 1427982 | grep BOUNCE 
> 
> Comes up empty. Without that custom rule, it does trigger
> VBounce. So, no -- that custom rule is not working. It
> *is* triggered by the null Return-Path. Did you restart
> the daemon, or just test it with 'spamassassin'?
> 

Yup, I forgot to restart spamd.. and tested with spamassassin.


> Anyway, that's another null Return-Path. Either you are
> just "lucky" to receive so much of that behavior, or
> something is invalidating the Return-Path in your mail
> processing chain. (No, it is not fetchmail by default.
> Custom setting. Or something else.) 
> 

Yes, I get lots of those. The first example came from hotmail-account via fetchmail calling hotwayd (HTTP->POP3 converter), but the second one plain IMAP/fetchmail.



Re: BOUNCE_MESSAGE problem

Posted by Henrik K <he...@hege.li>.
On Wed, May 20, 2009 at 02:21:42AM +0200, Karsten Bräckelmann wrote:
> On Wed, 2009-05-20 at 02:42 +0300, Jari Fredriksson wrote:
> > Another one. This is from Washington Post. Still with fetchmail.
> > http://wwww.pastebin.ca/1427982
> > 
> > Marked as BOUNCE.
> > 
> >     meta __BOUNCE_RPATH_NULL  0
> > 
> > should be working.
> 
> $ spamassassin --cf="meta __BOUNCE_RPATH_NULL 0" < 1427982 | grep BOUNCE
> 
> Comes up empty. Without that custom rule, it does trigger VBounce. So,
> no -- that custom rule is not working. It *is* triggered by the null
> Return-Path. Did you restart the daemon, or just test it with
> 'spamassassin'?
> 
> Anyway, that's another null Return-Path. Either you are just "lucky" to
> receive so much of that behavior, or something is invalidating the
> Return-Path in your mail processing chain. (No, it is not fetchmail by
> default. Custom setting. Or something else.)

Funnily this was just talked about in another thread..

IF for some reason people still want to see null hitting BOUNCE_MESSAGE,
shouldn't that be fixed to use "EnvelopeFrom" like it should? So it gets the
right header in all cases(?). Seems like a bug to me. Amavisd-new quarantine
files contain Return-Path: <> and original sender in X-Envelope-From etc.

I can assure you that if you have any decend amount of users, you will see
legimate null traffic.


Re: BOUNCE_MESSAGE problem

Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Wed, 2009-05-20 at 02:42 +0300, Jari Fredriksson wrote:
> Another one. This is from Washington Post. Still with fetchmail.
> http://wwww.pastebin.ca/1427982
> 
> Marked as BOUNCE.
> 
>     meta __BOUNCE_RPATH_NULL  0
> 
> should be working.

$ spamassassin --cf="meta __BOUNCE_RPATH_NULL 0" < 1427982 | grep BOUNCE

Comes up empty. Without that custom rule, it does trigger VBounce. So,
no -- that custom rule is not working. It *is* triggered by the null
Return-Path. Did you restart the daemon, or just test it with
'spamassassin'?

Anyway, that's another null Return-Path. Either you are just "lucky" to
receive so much of that behavior, or something is invalidating the
Return-Path in your mail processing chain. (No, it is not fetchmail by
default. Custom setting. Or something else.)

  guenther


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}


Re: BOUNCE_MESSAGE problem

Posted by Jari Fredriksson <ja...@iki.fi>.
>> On Tue, 2009-05-19 at 21:59 +0300, Jari Fredriksson
>> wrote: 
>> 
>> Try disabling the __BOUNCE_RPATH_NULL constraint, by
>> overriding it in local.cf:
>>  meta __BOUNCE_RPATH_NULL  0
> 

Another one. This is from Washington Post. Still with fetchmail.

http://wwww.pastebin.ca/1427982

Marked as BOUNCE.

    meta __BOUNCE_RPATH_NULL  0

should be working.



Re: BOUNCE_MESSAGE problem

Posted by Jari Fredriksson <ja...@iki.fi>.
> On Tue, May 19, 2009 22:34, Jari Fredriksson wrote:
>>> On Tue, 2009-05-19 at 21:59 +0300, Jari Fredriksson
>>> wrote: Try disabling the __BOUNCE_RPATH_NULL
>>> constraint, by overriding it in local.cf:
>>>  meta __BOUNCE_RPATH_NULL  0
>> Thanks! It works.
> 
> next question is why does maillist mails bounce to you ?

bounce? Are you drunk?

I'm a subscriber, and the mail is not a bounce, as You can see if you look at the pastebin.





Re: BOUNCE_MESSAGE problem

Posted by Benny Pedersen <me...@junc.org>.
On Tue, May 19, 2009 22:34, Jari Fredriksson wrote:
>> On Tue, 2009-05-19 at 21:59 +0300, Jari Fredriksson wrote:
>> Try disabling the __BOUNCE_RPATH_NULL constraint, by
>> overriding it in local.cf:
>>  meta __BOUNCE_RPATH_NULL  0
> Thanks! It works.

next question is why does maillist mails bounce to you ?


-- 
http://localhost/ 100% uptime and 100% mirrored :)


Re: BOUNCE_MESSAGE problem

Posted by Jari Fredriksson <ja...@iki.fi>.
> On Tue, 2009-05-19 at 21:59 +0300, Jari Fredriksson wrote:
> 
> Try disabling the __BOUNCE_RPATH_NULL constraint, by
> overriding it in local.cf:
>  meta __BOUNCE_RPATH_NULL  0

Thanks! It works.






Re: BOUNCE_MESSAGE problem

Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Tue, 2009-05-19 at 21:59 +0300, Jari Fredriksson wrote:
> I get lots of false  BOUNCE_MESSAGES from VBounce-plugin.
> 
> Sample: http://www.pastebin.ca/1427728

> What might be wrong here?

It triggers on the NULL Return-Path. With a somewhat fuzzy look at the
rule and some abstraction, BOUNCE_MESSAGE equals this:

__HAVE_BOUNCE_RELAYS && !__MY_SERVERS_FOUND && ( __BOUNCE_RPATH_NULL || ... )

That's "whitelist_bounce_relays are specified", and "those relays are
not found in any text or message/* MIME parts" (of course not, it's not
a bounce), and "has a null Return-Path".

In other words, it is not a valid bounce, but has a null Return-Path.
That's it.


Try disabling the __BOUNCE_RPATH_NULL constraint, by overriding it in
local.cf:
  meta __BOUNCE_RPATH_NULL  0


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}