--- Gary V <[EMAIL PROTECTED]> wrote:

> Peter wrote:
> 
> > --- Mark Martinec <[EMAIL PROTECTED]> wrote:
> 
> >> Peter,
> >> 
> >> > Should the subject line being edited be reflected in the logs then?
> >> > I just want to make sure it's being done.
> >> 
> >> At log level 5 you should see log entries like:
> >> 
> >> (55083-04) lookup (spam_subject_tag2) => true,  "..." matches,
> >>   result="***SPAM*** ", matching_key="(constant:***SPAM*** )"
> >> ...
> >> (55083-04) lookup (spam_modifies_subj) => true,  "..." matches,
> >>   result="1", matching_key="(constant:1)"
> >> 
> >> (55083-04) headers CLUSTERING: NEW CLUSTER <...>: score=6.685,
> >>   tag=1, tag2=1, subj=1, subj_u=0, local=1, bl=, s=***SPAM***
> >> 
> >> Subject is modified if local=1 and s=***(nonempty)
> >> 
> >> The most common reason for ***SPAM*** not being inserted
> >> is that recipient address does not match @local_domains_maps.
> >> 
> >> The ultimate proof is a message in recipient's mailbox.
> 
> > No, I do not see this type of logging.  There are no instances of the
> > string "spam_subject".  Yet my SQL policy is all set up.  I have one
> > domain user (@domain.com) and it is set as local in the user table. 
> Do I
> > also need to edit my amavisd.conf file in some way?
> > --
> > Peter
> 
> As a catchall, you can set:
> $sa_spam_subject_tag = '***SPAM*** ';
> if you have not already done so. In fact you may want to do this as an
> alternative to setting this in SQL because the trailing space will get
> trimmed from the SQL data (annoying).
> 
> If you have $log_level set to 5 and you are not seeing this, what do
> you have $DO_SYSLOG and $SYSLOG_LEVEL set to?
> 
> If you are using syslog (you have set $DO_SYSLOG = 1;),
> try setting: $SYSLOG_LEVEL = 'mail.info'; (instead of 'mail.debug'
> if that is what you currently have.)
> 
> This may (or may not) give you more detail. If it does you may want to
> leave it that way (but of course set $log_level back to something less
> verbose after testing). As I'm sure you know, unlike making changes in
> SQL which take effect immediately, any changes to amavisd.conf require
> an amavisd stop/start or reload.

I put $DO_SYSLOG = 1 and now I see a lot more logging including the
subject editing stuff.  However, at the same time I added

$sa_spam_modifies_subj = 1;
$sa_spam_subject_tag = '*** SPAM *** ';

to my config file so I'm not sure what made the difference although for
sure those two lines did not create all the extra SQL logging I'm now
seeing.  Just to be sure I went back and took the two lines out again. 
Anyway, I noticed that my log messages were showing the tag without the
whitespace so it appears to be strictly a matter of the DO_SYSLOG
variable.  Isn't there any way to achieve the same logging with its value
being '0'?  I didn't have any explicit line for syslog log level but I
explicitly set it at 'mail.info' with no change.

--
Peter


        

        
                
__________________________________________________________ 
Find your next car at http://autos.yahoo.ca


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to