spamc --reporttype= not working and curious log message.

2018-04-18 Thread Reio Remma
Hello! I'm trying to use this to report spam: spamc --reporttype=report --username=amavis < mail However all I get is: spamc[9632]: Please specify a legal report type It works if I omit the = after --reporttype. This is with SA 3.4.2 from SVN, iirc it worked the other day with --reporttype=r

Re: Can't locate Mail/SpamAssassin/Plugin/SpamCop.pm: lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied

2018-04-18 Thread Rainer Dorsch
Yes, but the inotify version (not working anymore) I start in rc.local using su -c /home/rd/bin/reportspam rd 2>&1 >> /var/log/reportspam & Not sure if that has any side effects... Rainer Am Donnerstag, 19. April 2018, 00:23:15 CEST schrieb Reio Remma: > Are you running both commands as the sam

EMF file vulnerability?

2018-04-18 Thread Alex
Hi all, this may be slightly OT, but we've been blocking .emf files forever but today a user complained that we blocked their Word documents which apparently have "image1.emf" files in them and were considered a threat by amavisd due to our restricted file type policy. I recall this being an issue

Re: Can't locate Mail/SpamAssassin/Plugin/SpamCop.pm: lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied

2018-04-18 Thread Reio Remma
Are you running both commands as the same user? Reio On 18.04.2018 23:00, Rainer Dorsch wrote: That was also my first guess, but it seems not the be the case here alll dirs are 755 and the file 644: rd@netcup:~$ locate SpamCop.pm /usr/share/perl5/Mail/SpamAssassin/Plugin/SpamCop.pm rd@netcup:~

Re: Can't locate Mail/SpamAssassin/Plugin/SpamCop.pm: lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied

2018-04-18 Thread Rainer Dorsch
That was also my first guess, but it seems not the be the case here alll dirs are 755 and the file 644: rd@netcup:~$ locate SpamCop.pm /usr/share/perl5/Mail/SpamAssassin/Plugin/SpamCop.pm rd@netcup:~$ ls -l /usr/share/perl5/Mail/SpamAssassin/Plugin/SpamCop.pm -rw-r--r-- 1 root root 8578 Feb 7 2

Re: plugin: eval failed: __alarm__ignore__(xxx) how to troubleshoot

2018-04-18 Thread Chris Conn
maybe solved in centos7 ? i do not use precompiled problems Hello, I guess I will soon find out.  Not using bayes or anything, most plugins are disabled actually.  Just trying to figure out which one is misbehaving, as spamd grows to 4Gb of resident memory usage, at 100% CPU, and eventual

Re: Can't locate Mail/SpamAssassin/Plugin/SpamCop.pm: lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied

2018-04-18 Thread Christian Grunfeld
"Can´t locate" and "permission denied" seems to be a directory permission issue 2018-04-18 14:03 GMT-03:00 Rainer Dorsch : > Hello, > > I have a strange problem when reporting spam using spamassassin -rD > > I monitor an imap directory using inotifywait: > > inotifywait --monitor --quiet --event

Can't locate Mail/SpamAssassin/Plugin/SpamCop.pm: lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied

2018-04-18 Thread Rainer Dorsch
Hello, I have a strange problem when reporting spam using spamassassin -rD I monitor an imap directory using inotifywait: inotifywait --monitor --quiet --event moved_to,create --format '%f' /home/rd/ Maildir/.SPAM-learned/cur/ | /home/rd/bin/reportspam-line.sh 2>&1 and then report spam using r

Re: match rules to base64 encoded body

2018-04-18 Thread Kris Deugau
(Please keep list mail on the list.) On 11/04/2018 16:15, Kris Deugau wrote: >> Please post the rules you think should match on this example. saqariden wrote: this is my rule: uri    __FR_SHORT_SPAM_URI_1 /(\/[a-zA-Z\d]{1,3}\.php\?[a-zA-Z\d]{3,9})|(\/[a-zA-Z\d]{3,10}\/[a-zA-Z\d]{3,9}\.php\

Re: plugin: eval failed: __alarm__ignore__(xxx) how to troubleshoot

2018-04-18 Thread Benny Pedersen
Chris Conn skrev den 2018-04-18 16:00: this is a relatively old install, SA 3.3.1 on Centos6 (stock RPMs) maybe solved in centos7 ? i do not use precompiled problems

Re: plugin: eval failed: __alarm__ignore__(xxx) how to troubleshoot

2018-04-18 Thread Daniele Duca
On 18/04/2018 16:08, David Jones wrote: I too have been seeing a very high number of SA timeouts via MailScanner the past week and would like to know how to troubleshoot these timeouts.  I have never been able to catch problem messages in the act to figure out what is causing them. FWIW, w

Re: plugin: eval failed: __alarm__ignore__(xxx) how to troubleshoot

2018-04-18 Thread David Jones
On 04/18/2018 09:00 AM, Chris Conn wrote: Hello, We recently started having problems on a few servers with spamd processes starting to hog RAM (3G++ per child) and we are noting some timeouts in the logs.  as well,  we are seeing this msg Apr 18 08:48:24 spamd[2451]: plugin: eval failed: __a

plugin: eval failed: __alarm__ignore__(xxx) how to troubleshoot

2018-04-18 Thread Chris Conn
Hello, We recently started having problems on a few servers with spamd processes starting to hog RAM (3G++ per child) and we are noting some timeouts in the logs.  as well,  we are seeing this msg Apr 18 08:48:24 spamd[2451]: plugin: eval failed: __alarm__ignore__(156) Apr 18 08:58:25 spamd[1