similar to: sieve rule for "header don't exist"

On 2015-03-30 11:25, Reindl Harald wrote: > is there a way to expresse when the header "X-Spam-Status" *do not* > exist move the message to a different folder? > > :contains, :matches and :is are not helpful here > Have you tried using the "exist" test from the sieve rfc 5.5. Test exists Usage: exists <header-names: string-list> The

I've just set up a new mailserver using Centos5.2 (sendmail+clamav-milter+spamass-milter). I'm using the spamass-milter package from rpmforge (spamass-milter-0.3.1-1.el5.rf). I notice that the default setup is to run it as root. I set up my previous mailserver on Centos4, and I can't remember if I did anything special, but on that machine it runs as user "sa-milt". Is

Sorry, not a direct CentOS question, but I know there's a lot of experienced users on this list...I'm using CentOS with sendmail and spamassassin. I've got it configured with spamass-milter and it is working correctly. However, I was expecting to be able to reject mail that is marked as spam, not just deliver it as usual. Anyone know if it can be done and how? I know a milter

On Wed, 8 Mar 2017, Mark Weaver wrote: > Hello all, > > I've been googling my brains out since yesterday looking for up-to-date > information on this matter, and have found information that is anywhere from > 15 to 5 years old. I'd really like some information that much more up to date > on the subject. Specifically configuring Sendmail SMTP authentication (_no >

I wish to add options to sendmail INPUT_MAIL_FILTER(`spamassassin', `S=local:/var/run/spamass-milter/spamass-milter.sock, F=T, T=C:5m;S:4m;R:4m;E:5m')dnl dnl MAILER(cyrusv2)dnl INPUT_MAIL_FILTER(`greylist', `S=local:/var/run/milter-greylist/milter-greylist.sock') define(`confMILTER_MACROS_CONNECT', `j, {if_addr}') define(`confMILTER_MACROS_HELO', `{verify},

Am 09.02.2015 um 22:29 schrieb Leander Sch?fer: > I'm currently busy with a substiution of my current mail server. I'm > currently using > > * Clam-SMTP and > * SpamAssassin > > to fight Spam. I wonder if it is worth implementing AmaViS with > SpamAssassin backend instead and also using AmaViS to speak to clamd > directly. But I more and more wonder wether

I've everything running fine under CentOS-7, as far as I can tell, except that spam is not being diverted to my spam folder ~/Maildir/.Spam . I'm running postfix + spamass-milter + spamass-milter-postfix + dovecot (+ spamassassin), and spam is being duly marked before ending in my inbox . As far as I can see, the current advice is to leave filtering to dovecot, using the

On Sat, 21 Sep 2019, Kenneth Porter wrote: > I've been doing sendmail -> MIMEDefang -> SpamAssassin/clamd and > then sendmail -> procmail -> SpamAssassin. Yeah, SA gets run twice, > once to reject scores > 10 by the milter and then again by each user > to incorporate their Bayes scores. I'd love to run it only once but > haven't invested time in

Does anybody have a good method for disabling SA checks on outbound email under sendmail running the spamass milter? Some of our Vhost accounts are getting flagged as spam on the way out due to being on a dirty ISP network. John Hinton

I'm trying to clarify the various ways in which I could set up Postfix + Dovecot + SpamAssassin under CentOS-7, and I'd welcome any comments on the following remarks. As far as I can see there are 3 standard ways of setting this up: 1. Use amavisd 2. Use dovecot + pigeonhole/sieve 3. Use spamass-milter At present I'm following (2), but am thinking of going over to (1), since

Switching to dovecot LMTP appears to have change the information in the received header, which appears to be causing my spam filter to wig out and mark local to local emails as spam. Here?s what the received header used to look like: Received: from [10.0.5.3] (c-71-229-144-93.hsd1.co.comcast.net [71.229.144.93]) by mail.covisp.net (Postfix) with ESMTPS id B67B8118AD59 for <kreme at

On 9/3/07, Feizhou <feizhou at graffiti.net> wrote: > > > Now, I can find some files @ /etc/mail > > > > below are files. > > > > mimedefang-filter > > sa-mimedefang.cf <http://sa-mimedefang.cf> > > sa-mimedefang.cf.example > > > > I first want to block Bcc and limit Cc to about 5 users. I googled a > > lot. But, I am still

Hello all, I finally got spamass-milter and clamav-milter running, but have one error I've not been able to determine what is happening. From the log entry I see this line: SYSERR(sa-milt): hash map "Alias0": unsafe map file /etc/aliases.db: Permission denied: 39 Time(s) any pointers here? The 2nd item is with yum. I attempted to update, and wound up getting a fail on a

I am following this tutorial: https://www.linuxbabe.com/redhat/spamassassin-centos-rhel-block-email-spam. I followed the steps in "Move Spam into the Junk Folder". When I send an email from a blacklisted e-mail address, I get a bounce e-mail from my e-mail server. Here is what is in my spamass-milter file: EXTRA_FLAGS="-m -r 8 -R NO_SPAM -i 127.0.0.1 -g sa-milt --

Say someone has setup spf for his domain and sends an email to a user that has in roundcube enabled the sieve forward. If the message is forwarded without altering the message headers, this could result in a message being blocked or not relayed, because sending hosts ip, is not in the spf of the from: domain. Possible solutions are: - add option if enabled, it replaces the From: with that

Hi all, I'm trying to add some milters (particularly spamass-milter and clamav-milter, which I acquired through rpmforge) to my postfix configuration on Centos5 with the targeted SELinux policy.. I'm running into difficulty getting postfix to communicate through the unix domain sockets created by the milters, because selinux keeps blocking them. I've attempted to use audit2allow

Hello everyone, We have Dovecot 2.1.6 and Pigeonhole 0.3.0. We would like Pigeonhole not to send the vacation response to noreply at whatever.com<mailto:noreply at whatever.com>. In this wiki http://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Vacation_auto-reply are showed the different exceptions, but the noreply is not in there. How can I add this address, or another one, to this exception

I'm trying to clarify the various ways in which I could set up Postfix + Dovecot + SpamAssassin under CentOS-7, and I'd welcome any comments on the following remarks. As far as I can see there are 3 standard ways of setting this up: 1. Use amavisd 2. Use dovecot + pigeonhole/sieve 3. Use spamass-milter At present I'm following (2), but am thinking of going over to (1), since

I know, I should not have to ask this question, but it appears that ALL my previous yum.repos.d entries have been trashed, with the only ones left is base, CentOS Media then the mirrors.rpmforge.reo, rhel-mondo.repo, rpmforge.repo, and webmin.repo. I've been bitten by the mixing of repositories before and want to avoid that scenario. Something is amok in the existing, and it throws all

RFC3028 say: Folding of long header lines (as described in [IMAIL] 3.4.8) is removed prior to interpretation of the data. The folding syntax (the CRLF that ends a line plus any leading whitespace at the beginning of the next line that indicates folding) are interpreted as if they were a single space. But it seems to be not true for dovecot-sieve-1.0.2 for header Received: