You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Greg Kopp <gk...@gregkopp.com> on 2004/06/07 18:15:16 UTC

report_safe not working?

I have added this line to my local.cf file:

# Encapsulate spam in an attachment
report_safe             2

But it doesn't seem to be encapsulating the offending message into an 
attachment. What am I doing wrong?

Greg

Re: report_safe not working?

Posted by Greg Kopp <gk...@gregkopp.com>.
OK. I think I know the difference of what is going on with these two 
systems. On the one side, I am invoking spamc from a .qmail file. On the 
new system, I am using qmail-scanner. I assumed that SA would work the 
same with both.

I will move this question now to a different list.

Thank you very much for the help.

Greg

Matt Kettler wrote:

> Under qmail-scanner ALL message mangling is handled by qmail-scanner 
> itself, not SA.
>
> Header rewrites, body rewrites and subject tags added by SA will be 
> ignored.
>
> At 01:55 PM 6/7/2004, Greg Kopp wrote:
>
>> qmail-scanner.
>>
>> Matt Kettler wrote:
>>
>> > At 12:15 PM 6/7/2004, Greg Kopp wrote:
>> >
>> >> I have added this line to my local.cf file:
>> >>
>> >> # Encapsulate spam in an attachment
>> >> report_safe             2
>> >>
>> >> But it doesn't seem to be encapsulating the offending message into 
>> an attachment. What am I doing wrong?
>> >
>> > How do you integrate SA? Just via procmail, or are you using 
>> qmail-scanner, mailscanner, mimedefang or other integration tool 
>> which does it's own markups?
>> >
>> >
>
>


Re: report_safe not working?

Posted by Matt Kettler <mk...@evi-inc.com>.
Under qmail-scanner ALL message mangling is handled by qmail-scanner 
itself, not SA.

Header rewrites, body rewrites and subject tags added by SA will be ignored.

At 01:55 PM 6/7/2004, Greg Kopp wrote:
>qmail-scanner.
>
>Matt Kettler wrote:
>
> > At 12:15 PM 6/7/2004, Greg Kopp wrote:
> >
> >> I have added this line to my local.cf file:
> >>
> >> # Encapsulate spam in an attachment
> >> report_safe             2
> >>
> >> But it doesn't seem to be encapsulating the offending message into an 
> attachment. What am I doing wrong?
> >
> > How do you integrate SA? Just via procmail, or are you using 
> qmail-scanner, mailscanner, mimedefang or other integration tool which 
> does it's own markups?
> >
> >


Re: report_safe not working?

Posted by Greg Kopp <gk...@gregkopp.com>.
qmail-scanner.

Matt Kettler wrote:

> At 12:15 PM 6/7/2004, Greg Kopp wrote:
> 
>> I have added this line to my local.cf file:
>>
>> # Encapsulate spam in an attachment
>> report_safe             2
>>
>> But it doesn't seem to be encapsulating the offending message into an 
>> attachment. What am I doing wrong?
> 
> 
> How do you integrate SA? Just via procmail, or are you using 
> qmail-scanner, mailscanner, mimedefang or other integration tool which 
> does it's own markups?
> 
> 
> 

Re: report_safe not working?

Posted by Matt Kettler <mk...@evi-inc.com>.
At 12:15 PM 6/7/2004, Greg Kopp wrote:
>I have added this line to my local.cf file:
>
># Encapsulate spam in an attachment
>report_safe             2
>
>But it doesn't seem to be encapsulating the offending message into an 
>attachment. What am I doing wrong?

How do you integrate SA? Just via procmail, or are you using qmail-scanner, 
mailscanner, mimedefang or other integration tool which does it's own markups?




Re: report_safe not working?

Posted by Markus Welsch <ma...@suk.de>.
> Sorry.
> 
> 2.63 and I haven't tried 1. A friend suggested 2. To be honest, I never 
> looked up what the differences were.

2 attaches it as text/plain.

> I followd qmailrocks.org for the most part interjecting my own tweaks 
> here and there.
> 
> I have a similar setup on a test mail server and it encapsulates OK.

To be honest I do not use qmail, I use Postfix (2.1.1) and everything 
works so far. Do the other things you specify in your local.cf work? You 
could try with setting required_hits to 0.0, etc


Re: report_safe not working?

Posted by Greg Kopp <gk...@gregkopp.com>.
Sorry.

2.63 and I haven't tried 1. A friend suggested 2. To be honest, I never 
looked up what the differences were.

I followd qmailrocks.org for the most part interjecting my own tweaks 
here and there.

I have a similar setup on a test mail server and it encapsulates OK.

Markus Welsch wrote:

>  > I have added this line to my local.cf file:
>  >
>  > # Encapsulate spam in an attachment
>  > report_safe             2
>  >
>  > But it doesn't seem to be encapsulating the offending message into an
>  > attachment. What am I doing wrong?
> 
> Which SpamAssassin version are you using and does report_safe 1 work ?
> 

Re: report_safe not working?

Posted by Markus Welsch <ma...@suk.de>.
 > I have added this line to my local.cf file:
 >
 > # Encapsulate spam in an attachment
 > report_safe             2
 >
 > But it doesn't seem to be encapsulating the offending message into an
 > attachment. What am I doing wrong?

Which SpamAssassin version are you using and does report_safe 1 work ?


Re: report_safe not working?

Posted by Markus Welsch <ma...@suk.de>.
>>The proper values are 0 for off and 1 for on.
> 
> 
> Actually, I think I got those numbers reversed, as I have "0" in my 
> persomal user_prefs file.
> 
> Of course, if I'm wrong, and 2 is a valid option, please feel free to 
> ignore me.

Excerpt from 
http://www.spamassassin.org/doc/Mail_SpamAssassin_Conf.html#item_report_safe_%7B_0_%7C_1_%7C_2_%7D_%28default%3A_1%

report_safe { 0 | 1 | 2 } (default: 1)

If this option is set to 1, if an incoming message is tagged as spam, 
instead of modifying the original message, SpamAssassin will create a 
new report message and attach the original message as a message/rfc822 
MIME part (ensuring the original message is completely preserved, not 
easily opened, and easier to recover).

If this option is set to 2, then original messages will be attached with 
a content type of text/plain instead of message/rfc822. This setting may 
be required for safety reasons on certain broken mail clients that 
automatically load attachments without any action by the user. This 
setting may also make it somewhat more difficult to extract or view the 
original message.

If this option is set to 0, incoming spam is only modified by adding 
some X-Spam- headers and no changes will be made to the body. In 
addition, a header named X-Spam-Report will be added to spam. You can 
use the remove_header option to remove that header after setting 
report_safe to 0.


Re: report_safe not working?

Posted by Mike Burger <mb...@bubbanfriends.org>.
On Mon, 7 Jun 2004, Mike Burger wrote:

> On Mon, 7 Jun 2004, Greg Kopp wrote:
> 
> > I have added this line to my local.cf file:
> > 
> > # Encapsulate spam in an attachment
> > report_safe             2
> > 
> > But it doesn't seem to be encapsulating the offending message into an 
> > attachment. What am I doing wrong?
> 
> The proper values are 0 for off and 1 for on.

Actually, I think I got those numbers reversed, as I have "0" in my 
persomal user_prefs file.

Of course, if I'm wrong, and 2 is a valid option, please feel free to 
ignore me.
-- 
Mike Burger
http://www.bubbanfriends.org

Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000

To be notified of updates to the web site, visit 
http://www.bubbanfriends.org/mailman/listinfo/site-update, or send a 
message to:

site-update-request@bubbanfriends.org

with a message of: 

subscribe

Re: report_safe not working?

Posted by Mike Burger <mb...@bubbanfriends.org>.
On Mon, 7 Jun 2004, Greg Kopp wrote:

> I have added this line to my local.cf file:
> 
> # Encapsulate spam in an attachment
> report_safe             2
> 
> But it doesn't seem to be encapsulating the offending message into an 
> attachment. What am I doing wrong?

The proper values are 0 for off and 1 for on.
-- 
Mike Burger
http://www.bubbanfriends.org

Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000

To be notified of updates to the web site, visit 
http://www.bubbanfriends.org/mailman/listinfo/site-update, or send a 
message to:

site-update-request@bubbanfriends.org

with a message of: 

subscribe