You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Ron McKeating <R....@lboro.ac.uk> on 2005/06/20 15:06:11 UTC
report settings
Is it possible to have a standard setting that does not put a full
report in the header for normal users, but does for one or 2 selected
users?
Ron
--
Ron McKeating
Senior IT Services Specialist
Computing Services
Loughborough University
01509 222329
Re: report settings
Posted by Ron McKeating <R....@lboro.ac.uk>.
On Mon, 2005-06-20 at 18:51 +0530, Rakesh wrote:
> Ron McKeating wrote:
>
> >Is it possible to have a standard setting that does not put a full
> >report in the header for normal users, but does for one or 2 selected
> >users?
> >
> >Ron
> >
> >
> >
> Are you directly using Spamc or using Amavis or MailScanner or something
> else as a wrapper. If you are using MailScanner then you can do it, I
> don't know abt Amavis.
>
We run spamd and call it from exim.
Ron
> Rakesh
>
> ----------------------------------------------------------
> Netcore Solutions Pvt. Ltd.
> Website: http://www.netcore.co.in
> Spamtraps: http://cleanmail.netcore.co.in/directory.html
> ----------------------------------------------------------
--
Ron McKeating
Senior IT Services Specialist
Computing Services
Loughborough University
01509 222329
Re: report settings
Posted by Rakesh <ra...@netcore.co.in>.
Ron McKeating wrote:
>Is it possible to have a standard setting that does not put a full
>report in the header for normal users, but does for one or 2 selected
>users?
>
>Ron
>
>
>
Are you directly using Spamc or using Amavis or MailScanner or something
else as a wrapper. If you are using MailScanner then you can do it, I
don't know abt Amavis.
Rakesh
----------------------------------------------------------
Netcore Solutions Pvt. Ltd.
Website: http://www.netcore.co.in
Spamtraps: http://cleanmail.netcore.co.in/directory.html
----------------------------------------------------------
Re: report settings
Posted by Ron McKeating <R....@lboro.ac.uk>.
On Mon, 2005-06-20 at 16:55 +0100, Matthew Newton wrote:
> On Mon, Jun 20, 2005 at 02:06:11PM +0100, Ron McKeating wrote:
> > Is it possible to have a standard setting that does not put a full
> > report in the header for normal users, but does for one or 2 selected
> > users?
>
> If it is exiscan you are currently using, then I guess you currently
> have something like...?
>
> # reject messages over score 10 (don't check if size is too big though)
> deny message = Sorry, that looks like spam.
> condition = ${if <{$message_size}{1048576}{1}{0}}
> spam = nobody:true
> condition = ${if >= {$spam_score_int}{100}{1}{0}}
>
> # add headers to messages that got through the last one
> warn message = X-Spam-Score: ($spam_bar) $spam_score\n
> X-Spam-Report: $spam_report
> condition = ${if <{$message_size}{1048576}{1}{0}}
>
> accept
>
I tried this but when I put in the line X-Spam-Report exim refuses to
start and complains it does on recognise the acl.
>
> In which case you could add conditions on the "warn" statement, i.e.
>
> warn message = X-Spam-Score: ($spam_bar) $spam_score\n
> X-Spam-Report: $spam_report
> condition = ${if <{$message_size}{1048576}{1}{0}}
> condition = ${if eq {$sender_address_local_part}{postmaster} \
> {yes}{no}}
>
> warn message = X-Spam-Score: ($spam_bar) $spam_score
> condition = ${if <{$message_size}{1048576}{1}{0}}
> condition = ${if ! eq {$sender_address_local_part}{postmaster} \
> {yes}{no}}
>
> (untested) which would add the full report to the postmaster@ address,
> but not for everyone else. You could use a file lookup as the condition,
> of course.
>
> Matthew
>
>
--
Ron McKeating
Senior IT Services Specialist
Computing Services
Loughborough University
01509 222329
Re: report settings
Posted by Matthew Newton <mc...@leicester.ac.uk>.
On Mon, Jun 20, 2005 at 02:06:11PM +0100, Ron McKeating wrote:
> Is it possible to have a standard setting that does not put a full
> report in the header for normal users, but does for one or 2 selected
> users?
If it is exiscan you are currently using, then I guess you currently
have something like...?
# reject messages over score 10 (don't check if size is too big though)
deny message = Sorry, that looks like spam.
condition = ${if <{$message_size}{1048576}{1}{0}}
spam = nobody:true
condition = ${if >= {$spam_score_int}{100}{1}{0}}
# add headers to messages that got through the last one
warn message = X-Spam-Score: ($spam_bar) $spam_score\n
X-Spam-Report: $spam_report
condition = ${if <{$message_size}{1048576}{1}{0}}
accept
In which case you could add conditions on the "warn" statement, i.e.
warn message = X-Spam-Score: ($spam_bar) $spam_score\n
X-Spam-Report: $spam_report
condition = ${if <{$message_size}{1048576}{1}{0}}
condition = ${if eq {$sender_address_local_part}{postmaster} \
{yes}{no}}
warn message = X-Spam-Score: ($spam_bar) $spam_score
condition = ${if <{$message_size}{1048576}{1}{0}}
condition = ${if ! eq {$sender_address_local_part}{postmaster} \
{yes}{no}}
(untested) which would add the full report to the postmaster@ address,
but not for everyone else. You could use a file lookup as the condition,
of course.
Matthew
--
Matthew Newton <mc...@le.ac.uk>
UNIX and e-mail Systems Administrator, Network Support Section,
Computer Centre, University of Leicester,
Leicester LE1 7RH, United Kingdom