similar to: recent spam on mailing lists

Hai,   I run this on a debian Jessie, postfix 2.11 (all debian packages )   Route for me is like this. -> postscreen -> policy-weight -> policy-spf -> clamsmtp (-> spamassassin) -> user     A1. I have in main.cfg    content_filter = clamsmtp:127.0.0.1:10025   A2.  Yes, you can. This is how i did set up.. ..there maybe improvements on this, but for now works for

As many of you have probably realized, the spam filtering at @stat.math.ethz.ch has been dead for since yesterday (09-25) ~16:50 till today ~08:30. The sudden death may have been caused by unrelated installation of some perl modules (spamassassin *is* running on perl) by our IT staff. We are very sorry for this event. On the bright side: You have been able to get a glimpse of what you are

Sorry wrong list, .. :-/ my outlook replace sometimes the reply email adres to the mail below the one i selected.. :-/ Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens L.P.H. van Belle > Verzonden: woensdag 2 december 2015 14:41 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] 2 questions: Can I add

We have locally collected good experience the last few weeks using procmail-spam filtering, inclduing spamassassin to the procmail filters. The last two spams that went past the majordomo filters (the "traditional ones I've been using) through to R-devel both were not delivered to me, be but caught by the filters. I have now collected a bit more of a week experience using the new scheme

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:

heads up and fyi folks... CentOS 4 latest... SpamAssassin version 3.3.1 running on Perl version 5.8.8 :-) i noticed on a centos 4 box after doing a manual yum update and getting 2 updated perl packages from rpmforge again, just a heads up as rpmforge has been rock solid for us for years so we are no bashing spamassassin would not restart after the updates.... spamd: Oct 27 22:32:01.340

Package: logcheck-database Version: 1.2.43a Severity: minor Since last weekend's upgrade of logcheck-database from 1.2.42 to 1.2.43a, logcheck stopped ignoring routine SpamAssassin messages of the form Feb 20 21:36:16 tux64 spamd[4665]: spamd: checking message <20060220190721.0E0B41C5207 at llwb563.servidoresdns.net> for amu:7286 Could you please edit the second pattern in

I've been messing with this for too long, now, and I'm blind to whatever's wrong. Or I'm simply being dense. Either way, I need help with a common issue. I'm trying to get Postfix+Spamassassin+Dovecot going on Fedora 10. (I'll get back to the global Sieve thingy soon, but I need to get this going, first.) When using the simple: mailbox_command =

Trying to set up a mail server under CentOS7 - having done this with CentOS5 and CentOS6 over the last decade with no issues and reliable service, it was time to upgrade (?) to CentOS7. Shouldn't be a problem, right? Getting to grips with systemd has been challenging - to say the least. So a brief overview of what I am trying to set up: postfix / amavisd-new / spamassassin / clamav so we

Hi! I have dovecot, Spamassassin and postfix running. I started to use sa-learn to get better and more precise spam identification and filtering. I have not set the Bayes_path preference on my local.cf file, thus when I call sa-learn -u myuser at mydomain.org --spam, the Bayes DB gets updated at /root/.spamassassin. I decided then to create a sieve filter on dovecot, as described on

Hello fellow CentOS-users, on the net there are lots of Spamassassin related HOWTOs - describing how to create a shell script for Postfix and how to install Spamassassin and start its spamd daemon - step by step. Additionally antivirus setups are described... But I have a strong feeling, that this is unneeded on CentOS 6 - because there are already preconfigured stock packages for postfix and

Sorry if this not the right place to post this.... BUT... Since May 31st, ALL of these user list messages have been filtered by "spamassassin" running on my Linux box. - Claim to be listed in "Bayes" as spam. - Have no clue why this is happening. Luckily, "spamassassin" sent the messages to the "probably-spam" folder on the Linux box & I was able to

Hi, I set up DCC on CentOS 5 with Dual Sendmail - Amavisd-new and and Spam assassin. I installed DCC from AT rpms. pls see below for installed DCC rpm. [root at mailgw ~]# rpm -qa |grep DCC DCC-1.3.50-16.0.el5 Then, I configured in Deamon mode. I did below steps. [root at mailgw ~]# yum install DCC then, [root at mailgw ~]# cdcc "delete 127.0.0.1" [root at mailgw ~]# cdcc

The CentOS team likes to offer an apology for the political spam mails which went through our mail servers earlier today. Due to the nature of mailing list software for public discussion groups, there aren't that many security measures which can be taken to check which mails are supposed to get through and which mails aren't. Total safety can only be had by a moderation of all lists -

In order to prevent viruses being posted on the R (or ESS) mailing lists, I've disallowed binary attachments (of the "octet-stream" kind) as of 15 minutes ago. BTW, the case of Jan.10 was a typcial "MS Outlook address book" one. I've received automated e-mails from about 20 sites where the mail delivery server auto-detected the virus and didn't deliver it to

On 10/08/17 15:37, Paul Heinlein wrote: > On Thu, 10 Aug 2017, Gary Stainburn wrote: > >> I have the following error message in my /var/log/spamd >> >> spf: lookup failed: available_nameservers: No DNS servers available! >> >> Having Googled the error message I've found a number of responses >> which involve patching Perl or Spamassassin or other

I have a problem getting spamd and sendmail (both stock CentOS4 rpms) to work together on a couple of smtp relay machines. This is clearly a configuration issue and no doubt revolves around my lack of comprehension of how this is to work. Basically, the setup consists of two frontend public smtp transports that redirect all email through a firewall to an internal imap server for final

Package: logcheck-database Version: 1.2.63 Severity: normal Tags: patch spamassassin is now reporting Unix domain sockets in the rport field. I'm not exactly sure what changed to cause this to happen; it started after an upgrade whose only remotely relevant package was razor. I think the following pattern in ignore.d.server/spamd will work ^\w{3} [ :0-9]{11} [._[:alnum:]-]+

On Thursday 10 August 2017 18:45:32 Gordon Messmer wrote: > On 08/10/2017 01:21 AM, Gary Stainburn wrote: > > I have the following error message in my /var/log/spamd > > > > spf: lookup failed: available_nameservers: No DNS servers available! > > Try starting spamassassin later. Run "systemctl edit > spamassassin.service" and insert two lines: > >

On 12/12/2017 04:37 AM, Nicolas Kovacs wrote: > Spamassassin has been working nicely on my main server running CentOS 7 > and Postfix. SELinux is activated (Enforcing). > ... > SELinux is preventing /usr/bin/perl from 'read, write' accesses on the > file /var/log/spamassassin/.spamassassin/bayes_toks. > ... > Source Context system_u:system_r:spamd_t:s0