spamc syslog loglevel for "skipped message, greater than max message size"

Hi why does spamc[28825]: [ID 702911 mail.error] skipped message, greater than max message size (512000 bytes) have to be log level error? Instead of error would "warn" not be enough? thanks, Philipp

Re: no sa-update since jan 20

Matt Kettler a écrit : mailinglists wrote: Hello, I'm sorry if my question is not in the right place here, but I have searched on the net, without finding any answer So, here is my question : is it normal that I see not update of the rules since 2008 January 20th ? It used

no sa-update since jan 20

Hello, I'm sorry if my question is not in the right place here, but I have searched on the net, without finding any answer So, here is my question : is it normal that I see not update of the rules  since 2008 January 20th ? It used to be updated every week and I get a lot of spam wit

Re: spamd bayes error

Hi you seem to run global bayes. Try to use a database such as mysql or pgsql for bayes. you can make the db larger using the bayes_expiry_max_db_size parameter. See perldoc Mail::SpamAssassin::Conf Philipp > Hello guys, > > Why after a period of time, after spamassassin keeps learning ham and

Re: per user bayes db: auto_expiry problem --->> SOLVED

Hi Folks, it's been a while I asked here how to solve bayes timeout and spamd child timeout problems. Well, at least for our environment I have found a solution that seems to work. Also, I have a theory about the reason for this bayes timeout and spamd child timeout problems and I'd like to know w

Re: What broke FuzzyOcr?

> I'm seeing the below logs in my mail.log for every piece of e-mail. > Not sure what I did that started this, FuzzyOcr WAS working fine.. > > Mar 1 23:33:27 espphotography spamd[335]: (Can't locate object > method "dummy_check" via package "Mail::SpamAssassin::PerMsgStatus" > at > /opt/local/lib

Re: per user bayes db: auto_expiry problem, spamd child timeout, very long scantimes

> On Tue, 27 Feb 2007 [EMAIL PROTECTED] wrote: > >> Some emails have a scantime of more than 900 seconds. >> >> I do not see a relation to a huge load on the SpamAssassin Servers >> (I have 2 of them). The timeout problems happen when there is >> small load (10 out of 20 spamds marked Busy) as well

per user bayes db: auto_expiry problem, spamd child timeout, very long scantimes

Hi all I run a site for more than 2000 mailboxes with Postfix, SA 3.1.8 and procmail. Every user has his own bayes db. Allow_user_rules is deactivated. I have a number of problems: A number of emails passes spamd unfiltered due to spamd child timeout. Looking at the scantime it often is far more

force bayes expiry for all users in a bayes db per user scenario

Hi I have a problem with timeouts on the bayes expiry on SpamAssassin 3.1.7. These log messages look like this: spamd[5148]: bayes: expire_old_tokens: child processing timeout at spamd line 1083, line 369. spamd[22114]: bayes: child processing timeout at spamd line 1083. Because of these timeou

tell postfix to not use amavisd/spamassasin for sasl authenticaed mails

how to tell postfix to NOT check mails from sasl authenticated users: use no content_filter in your main.cf: content_filter = use a amavisd filter after sasl authentication main.cf: smtpd_sender_restrictions = permit_sasl_authenticated, check_sender_access regexp:/etc/postfix/amavisd.regexp amavisd

Spamassassin 3 and postfix

hi, i use postfix and amavisd-new/spamassassin to fight our spam. We are very happy with this setup. It works great. We only have one problem. Sending mail with a Emailclient from our dialup account at home to another mailbox hosted by our server causes Spmassassin to mark that email as spam