Re: [AMaViS-user] Forged 'X-Virus-Scanned' header bypasses Amavis-new scanning

[Christopher J Shaker]

Mark Martinec wrote:
 Chris,

   
 Also, your hints about debugging info from amavisd-new got
 me reading about the auto whitelist. Used the following config
 commands:
 /etc/mail/spamassassin/local.cf:
 use_auto_whitelist  0

 /usr/local/sbin/amavisd.conf:
 $sa_auto_whitelist = 0;
 

 $sa_auto_whitelist has no effect since version 3.0.0 or SpamAssassin,
 the use_auto_whitelist (in local.cf) is the only control.
   

Mark:

My /usr/local/sbin/amavisd does not contain 'use_auto_whitelist'. 
Appears that
I am running amavisd-new-2.5.3, which explains that.

Which version do you recommend we use?

 Seems to have disabled the auto whitelist for me, so that I can
 run spamassassin on every email. I prefer that behavior.
 

 SpamAssassin AWL just adds score points.
 It does not control whether a message is to be checked or not.
 See Mail::SpamAssassin::Plugin::AWL man page.

   Mark
   


Yeah, but it adds so many points that some spam forged to appear as if I 
sent it
ended up with huge negative scores...

Thank you,
Chris Shaker


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Re: [AMaViS-user] SQL table wblist not used

[Stefan Palme]

Hi all,

  using amavisd-2.4.x I have setup usage of SQL for lookup and
  storage. Everything works fine. Only the wblist table of my
  database is never used.
 
  My /usr/sbin/amavisd contains the correct default setting for
  $sql_select_white_black_list, which is referenced by %sql_clause.
 
  In my /etc/amavisd.conf no SQL clause is changed, so the correct
  default settings should apply (all other SQL statements work as
  expected).
 
  But when I send a test mail to amavisd-new and log the executed
  SQL statements (checking this in the log files of postgresql), I
  see the SELECT FROM users statement, the INSERT INTO msgs
  statement and so on. But a statement involving wblist is never
  executed.
 
  Any hints where I have to take a look at?
 
 I could think of a couple of reasons, but the ultimate answer
 would be in the log-level 5 log.
 
 Reasons to skip wblist check: infected or banned message,
 or bypassing of spam checks active for this recipient,
 or no 'user' records matching a recipient,
 or $sql_clause{sel_wblist} disabled.

I have solved the issue - it was my fault. The amavisd.conf did
not overwrite anything SQL related (only the DSNs are set), but
there are some more config files included, one of which contained
$sql_select_white_black_list = undef;

Thanks a lot
Regards
-stefan-



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/