similar to: Spamassassin + Postfix : delete spam mail on the server ?

On 12/18/18 3:34 AM, Fabian Arrotin wrote: > On 18/12/2018 08:08, Nicolas Kovacs wrote: >> Hi, >> >> My mail server is running on CentOS 7 with Postfix, Dovecot and >> Spamassassin. I get quite a lot of spam on a few accounts, and >> Spamassassin does its job fine. Spam mail is identified correctly, and >> it looks like there are no false positives, e. g.

> Am 18.12.2018 um 08:08 schrieb Nicolas Kovacs: >> The problem with this setup is that spam mail is still delivered, and I >> need Thunderbird's filters to weed out incoming mail. And when I'm using >> my webmail (running SquirrelMail), my inbox is a tsunami of unread >> [SPAM] messages. >> >> So I'd like to go a step further and delete all

On 18/12/2018 08:08, Nicolas Kovacs wrote: > Hi, > > My mail server is running on CentOS 7 with Postfix, Dovecot and > Spamassassin. I get quite a lot of spam on a few accounts, and > Spamassassin does its job fine. Spam mail is identified correctly, and > it looks like there are no false positives, e. g. valid mail is never > identified as spam. > > When a message is

Hi, Procmail, it can move messages around based on many rules. Use something like this in postfix main.cf: mailbox_command = /usr/bin/procmail-wrapper -o -a $DOMAIN -d $LOGNAME And something like this in /etc/procmailrc or $HOME/.procmailrc SPAMDIR=$HOME/Maildir/.Spam/ :0fw | /usr/bin/spamc :0 * ^X-Spam-Status: Yes $SPAMDIR DEFAULT=$HOME/Maildir/ ORGMAIL=$HOME/Maildir/ DROPPRIVS=yes HTH --

Hello all, About a year ago I set up a mail server on CentOS using this howto: http://wanderingbarque.com/howtos/mailserver/mailserver.html I managed to add amavisd-new with clamav and spamassassin. It runs very well, but it runs on CentOS 5.2, and if I try to upgrade, amavisd-new and clamav break. we are now also at the point where a backup mx will need to be implemented. If necessary I am

Hi, I'm currently fine-tuning my mail server (Postfix and Dovecot on CentOS 7). SPF, DKIM and DMARC work fine, now I'd like to limit the spam tsunami. Besides the official Postfix documentation, I've read a few articles about Postfix spam restrictions, namely these : https://www.linuxbabe.com/mail-server/block-email-spam-postfix https://wiki.centos.org/HowTos/postfix_restrictions

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

Absolutely, never reject spam at MTA level! Usually I put it in a spam folder, then add a cronjob that deletes messages older than 6 months, ymmv. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "CentOS mailing list" <centos at centos.org> > To: "CentOS mailing list" <centos at centos.org> >

Am 18.12.2018 um 08:08 schrieb Nicolas Kovacs: > The problem with this setup is that spam mail is still delivered, and I > need Thunderbird's filters to weed out incoming mail. And when I'm using > my webmail (running SquirrelMail), my inbox is a tsunami of unread > [SPAM] messages. > > So I'd like to go a step further and delete all messages flagged [SPAM] >

hey friends, I am running my company's mail server on FC3 which comprises of Postfix + Dovecot + MailScanner + Clamav + Squirrelmail + MailWatch + Spamassassin. I am using Dovecot 0.99.13-3 version on FC3 and I want to implement Quota limits for the users. I am using userdatabase as /etc/passwd file (auth_userdb = passwd ) and password database as pam(auth_passdb = pam) for dovecot. I read

--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 just installed SpamAssassin on two servers running CentOS 7 and Postfix. One is my sandbox server for experimenting, the other one is the server that hosts my company's web site, blog, mail, etc. So far, SpamAssassin seems to work as expected. I sent a test mail, which was duly flagges as [SPAM], and I already see the odd incoming spam message correctly flagged as [SPAM]. For testing

Le 26/03/2018 ? 10:28, isdtor a ?crit : > In my opionion, there is a serious gap in this area. It's either NIS, > simple, easy to setup yet insecure, or LDAP/FreeIPA/RH Id management > server at a complexity at least one order of magnitude beyond NIS. I gave FreeIPA a spin a while back. I installed it on a sandbox server, and from what I recall, it pulled in a tsunami of

After trying several paths, some suggested on this list, here's my results. 1) Fixing a unbootable system wasn't practical in my case. Fortunately, all my systems can be rebuilt from scratch. 2) When I was lucky enough to catch an updated system before reboot, backing out the defective updates wasn't possible. Yum said there were no prior versions. 3) The most reliable method I

I'm trying to figure out which would the best implementation for my mail and web server. Any experiences? Caveats? I'm on CentOS 3. -- <<JAV>>

Le 23/05/2018 ? 16:58, m.roth at 5-cent.us a ?crit?: > A suggestion: once you've got the firewall issue dealt with, set selinux > into permissive mode; *then* you can figure out what it's complaining > about, while at the same time, your system will be available. Once you've > fixed those issues, then you can make it enforcing. This is always my approach. Turns out the

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

Robert's suggestion indeed fixed the problem. I kept thinking those entries were necessary in inetd.conf. Also, kind thanks to Fred Gilbert for his prompt responses.:-) John

Dear FreeBSD Friends, i have FreeBSD 9.0 Stable Running the following roles for past four months. Everything is functioning smooth alright. I read that system should be upgraded frequently. i am afraid that if i upgrade something can break. i am planing to run it like that until FreeBSD 9.2 is out, perhaps two years before upgrade. i am not sure if this is a good idea. i seek your advice about

Just out of curiosity, why are you not using something like Kolab or Zimbra? On 07/20/2018 02:44 AM, Nicolas Kovacs wrote: > Le 18/07/2018 ? 17:04, Turritopsis Dohrnii Teo En Ming a ?crit?: >> One of the features of Microsoft Exchange 2016 is that you can create >> additional folders on your Inbox in the server (server-side). Can >> Linux-based SMTP servers do that? >