similar to: SpamAssassin and Maildir with Dovecot

How do I get this set up? spamassassin -D --lint shows me an error... debug: bayes: no dbs present, cannot tie DB R/O: /root/.spamassassin/bayes_toks and with no db present, it doesn't learn. Is there something simple that I'm missing? Craig

--On Saturday, September 21, 2019 9:59 PM +1200 Peter <peter at pajamian.dhs.org> wrote: >> I use spamassassin via amavisd-new, with messages going postfix -> >> amavisd -> second postfix (all via SMTP). > > This is a good setup, but you may find that you can eliminate the second > postfix step there and go postfix -> amavisd-new -> dovecot lmtp. Unless

pulling my hair out... If I rm -fr /root/.spamassassin/* then sa-learn a bunch of messages, it works... ]# sa-learn --dump magic 0.000 0 3 0 non-token data: bayes db version 0.000 0 3997 0 non-token data: nspam 0.000 0 0 0 non-token data: nham 0.000 0 202022 0 non-token data: ntokens 0.000

Hey all, I am getting a number of incoming emails flagged as spam this morning. Here's why: X-Spam-Level: ***** X-Spam-Status: Yes, score=5.2 required=5.0 tests=FH_DATE_PAST_20XX, SUBJ_ALL_CAPS autolearn=no version=3.2.5 X-Spam-Report: * 3.4 FH_DATE_PAST_20XX The date is grossly in the future. The date of 2010 in the emails is correct. I have typed "sa-update" and

Once upon a time, Kenneth Porter <shiva at sewingwitch.com> said: > Perfect. I think the only other significant customizations I have > are lines to use the MIMEDefang and OpenDKIM milters. When last I > looked into migrating, I recall that Postfix handled milters just > fine. Milters work a little different under postfix IIRC... I haven't tried them (which is a little sad,

Spamassassin seems to have become more-or-less non-functional in use with KMail on my server. It appears to be running OK, but only catches about 20% of my spam. I wonder if others have experienced this decline? I suspect that sa-learn is not performing properly. (I run sa-learn nightly on my spam, which is saved in ~/Maildir/.Spam/cur/ , through the default spamassassin installation.) Eg I

--On Thursday, January 29, 2004 11:16 PM +0200 Timo Sirainen <tss at iki.fi> wrote: > I don't yet really even want Dovecot to be too well known, it's not > ready yet. When 1.0 comes (this spring I hope) I'll start publicizing it > more. After that I should only need to add new features - existing ones > should be perfect and better than anyone else's ;) Just a

Hi I know i might get flamed for asking this in the dovecot mailing list instead of the spamassassin one but i thought someone might be kind enough to help anyway. TIA I'm trying to do site-wide spam filtering with a public namespace but it's not reading the folder i have in the public namespace This is the public namespace set in my dovecot.conf #public spam folder namespace public

On 3/31/2017 2:15 PM, Valeri Galtsev wrote: > Well, it sounds like you are one of the companies with whose effort I have > to fight constantly in my own effort to protect our users from spam... What makes Postfix superior in fighting spam? How do I integrate MIMEDefang, SpamAssassin, and ClamAV with Postfix? Are there migration guides for moving one's Sendmail anti-spam and AV

I would like to have the ability to execute a command on a folder based on a user doing something like copying a message to that folder. This could be accomplished with a config file directive. For example, this would be EXTREMEMLY useful as a spam learning hook. Take a scenario where each user has their own spamassassin bayes database, and you want to give the users the ability to train their

Hi all, I am trying to setup a mail server using postfix (virtual_mailboxes), spamassassin and dovecot, along with SQL where appropriate. From my research so far I realized that, for several reasons, it is required for me to use dovecot LDA instead of maildrop, local, procmail or other alternatives. My configuration was working flawlessly, until spamassassin per-user configuration came to

Hi, Spamassassin has been working nicely on my main server running CentOS 7 and Postfix. SELinux is activated (Enforcing). Since the most recent update (don't know if it's related to it though) I'm getting the following SELinux error. --8<----------------------------------------------------------------- SELinux is preventing /usr/bin/perl from 'read, write' accesses on

greetings, have been google foo for week or so. used to be super easy to upgrade spamassassin on CentOS dist. just grab the tarball and put in right spot and rpmbuild -tb spamassassin-3.somethingsomething.tar.gz then rpm or yum install and done would take just a few minutes. Yet... in regards to EL4 / CentOS 4 and spamassassin, it appears the end of the road for .spec in SA tarball

Once upon a time, Kenneth Porter <shiva at sewingwitch.com> said: > How would you implement the section here titled "Sendmail > workaround" using Postfix? http://www.postfix.org/postconf.5.html#recipient_delimiter -- Chris Adams <linux at cmadams.net>

I wonder if anyone is actually running SpamAssassin with Postfix/Amavisd-new under CentOS-6.4 . I have followed the instructions in <http://wiki.centos.org/HowTos/Amavisd> but as far as I can see SpamAssassin is not working. I should say that I do not understand from this document what is meant to happen to spam. I understand that a Spam header is added, but what actually happens to email

Hello, I run CentOS 3.4 on 3 machines (i386). Original yum.conf If I do a yum update: No actions to take If I do a yum upgrade a machine that has no spamassassin: No actions to take If I do a yum upgrade on 2 machines that have perl-Mail-SpamAssassin-3.0.1-1 installed (3rd party rpm, more recent than the CentOS/RHEL one): I will do the following: [update: spamassassin 2.55-3.4.i386] I will

I have installed spamassassin, per the instructions on Scalix's wiki, and it is working, with some important caviats. So I asked for help on the spamassassin user list, and got some, but I think I am butting up against some Centos specific issues... This is what I am seeing in the maillog: Aug 17 14:39:59 z9m9z sendmail[13082]: l7HIdvGf013082: Milter add: header: X-Spam-Checker-Version:

Hello, I'd like to figure out how to set up a site running dovecot on multiple computers for load balancing reasons. I'm currently running dovecot-1.0.14 on a 8GB RAM, 2 quad-core 2.66Ghz Xeon single server which runs FreeBSD 6.2-STABLE SMP. . the mailbox format was mbox and I successfully migrated to Maildir only . mailboxes are on an NFS NetApp server, attribute caching is off .

Postfix 2.5.5 SpamAssassin 3.2.5 (under Perl 5.10.0) ClamAV 0.95.1 Dovecot 1.2.rc2 works fine on Fedora 10. Installed Dovecot and ClamAV from source and everything else using yum. I'm using the ClamAV plugin for Spamassassin: http://wiki.apache.org/spamassassin/ClamAVPlugin I'm calling Spamassassin with: /etc/postfix/main.cf: mailbox_command = /usr/bin/spamc -f -e

Hi, I recently saw this a branch [1] of your git repository when dovecot-antispam has support of spamassassin. Is it intentional to not add it to the official release? Are there any plan to officially support spamassassin? [1] http://www.freenux.org/cgi-bin/gitweb.cgi?p=dovecot-antispam.git;a=shortlog;h=refs/heads/spamassassin Thanks -- Yann