Problems after upgrade from 4.85 to 5.03

Tue Oct 11 18:38:50 UTC 2016

Hi Daniel, 

Don't ignore the Pyzor error..... I had the same. You need to solve it. Spamassassin isnt working correctly if you don't solve it. 

I found a solution somewhere via Google. 

Met vriendelijke groet, Best regards, 

Thom van der Boon 
E-Mail: thom at vdb.nl 

===== 

Thom.H. van der Boon b.v. 
Transito 4 
6909 DA Babberich 
Tel.: +31 (0)88 4272727 
Fax: +31 (0)88 4272789 
Home Page: http://www.vdb.nl/ 

Van: "Daniel Malmgren" <daniel at kolefors.se> 
Aan: "MailScanner Discussion" <mailscanner at lists.mailscanner.info> 
Verzonden: Dinsdag 11 oktober 2016 20:29:51 
Onderwerp: Re: Problems after upgrade from 4.85 to 5.03 

Hi all. 

Thanks for all answers. When I ran MailScanner --debug I got error 
messages about mailscanner not finding the custom functions added by 
MailWatch. After some digging I found out that the custom functions 
directory moved between 4.85 and 4.86. I had to redo some of the steps 
on http://docs.mailwatch.org/doc/installing.html to get things working 
again. 

Another question while I'm at it. When running in debug mode I see this: 

pyzor: check failed: internal error, python traceback seen in response 

Doesn't seem to do any harm, is it safe just to ignore it? Tried 
upgrading pyzor (pip install --upgrade pyzor) but I still get the same 
warning. 

/Daniel 

Den 2016-10-11 kl. 10:12, skrev Daniel Malmgren: 
> Hi 
> I've upgraded from mailscanner 4.85 to 5.03 and I think I need some 
> help with getting things going after the upgrade. I'm running postfix 
> so I have got things set up as per instruktions on 
> https://www.mailscanner.info/postfix/. After the upgrade I got 
> permissions problems, so now I've changed "Run As Group" to mtagroup 
> and "Incoming Work Permissions" to 0660 which made all errors go away 
> and a check with --lint returns all fine. Now it seems though that 
> MailScanner processes the same messages again and again, like it's 
> stuck in a loop, see log snippet below. The messages seem to stay in 
> postfix's hold queue. 
> 
> Oct 11 09:29:39 cube MailScanner[10550]: MailScanner Email Processor 
> version 5.0.3 starting... 
> Oct 11 09:29:39 cube MailScanner[10550]: Reading configuration file 
> /etc/MailScanner/MailScanner.conf 
> Oct 11 09:29:39 cube MailScanner[10550]: Reading configuration file 
> /etc/MailScanner/conf.d/README 
> Oct 11 09:29:40 cube MailScanner[10550]: Read 501 hostnames from the 
> phishing whitelist 
> Oct 11 09:29:40 cube MailScanner[10550]: Read 19224 hostnames from the 
> phishing blacklists 
> Oct 11 09:29:40 cube MailScanner[10550]: Config: calling custom init 
> function SQLBlacklist 
> Oct 11 09:29:40 cube MailScanner[10550]: Config: calling custom init 
> function SQLWhitelist 
> Oct 11 09:29:40 cube MailScanner[10550]: Config: calling custom init 
> function MailWatchLogging 
> Oct 11 09:29:41 cube MailScanner[10550]: Using SpamAssassin results cache 
> Oct 11 09:29:41 cube MailScanner[10550]: Connected to SpamAssassin 
> cache database 
> Oct 11 09:29:41 cube MailScanner[10550]: Enabling SpamAssassin 
> auto-whitelist functionality... 
> Oct 11 09:29:48 cube MailScanner[10538]: Connected to Processing 
> Attempts Database 
> Oct 11 09:29:48 cube MailScanner[10538]: Found 2 messages in the 
> Processing Attempts Database 
> Oct 11 09:29:48 cube MailScanner[10538]: Using locktype = flock 
> Oct 11 09:29:48 cube MailScanner[10538]: Making attempt 4 at 
> processing message 9CC2E45321.A7F02 
> Oct 11 09:29:48 cube MailScanner[10538]: New Batch: Scanning 1 
> messages, 14245 bytes 
> Oct 11 09:29:49 cube MailScanner[10538]: Virus and Content Scanning: 
> Starting 
> Oct 11 09:29:52 cube MailScanner[10550]: Connected to Processing 
> Attempts Database 
> Oct 11 09:29:52 cube MailScanner[10550]: Found 2 messages in the 
> Processing Attempts Database 
> Oct 11 09:29:52 cube MailScanner[10550]: Using locktype = flock 
> Oct 11 09:30:41 cube MailScanner[10632]: MailScanner Email Processor 
> version 5.0.3 starting... 
> Oct 11 09:30:41 cube MailScanner[10632]: Reading configuration file 
> /etc/MailScanner/MailScanner.conf 
> Oct 11 09:30:41 cube MailScanner[10632]: Reading configuration file 
> /etc/MailScanner/conf.d/README 
> Oct 11 09:30:41 cube MailScanner[10632]: Read 501 hostnames from the 
> phishing whitelist 
> Oct 11 09:30:42 cube MailScanner[10632]: Read 19224 hostnames from the 
> phishing blacklists 
> Oct 11 09:30:42 cube MailScanner[10632]: Config: calling custom init 
> function SQLWhitelist 
> Oct 11 09:30:42 cube MailScanner[10632]: Config: calling custom init 
> function MailWatchLogging 
> Oct 11 09:30:42 cube MailScanner[10632]: Config: calling custom init 
> function SQLBlacklist 
> Oct 11 09:30:43 cube MailScanner[10632]: Using SpamAssassin results cache 
> Oct 11 09:30:43 cube MailScanner[10632]: Connected to SpamAssassin 
> cache database 
> Oct 11 09:30:43 cube MailScanner[10632]: Enabling SpamAssassin 
> auto-whitelist functionality... 
> Oct 11 09:30:54 cube MailScanner[10632]: Connected to Processing 
> Attempts Database 
> Oct 11 09:30:54 cube MailScanner[10632]: Found 2 messages in the 
> Processing Attempts Database 
> Oct 11 09:30:54 cube MailScanner[10632]: Using locktype = flock 
> Oct 11 09:33:09 cube MailScanner[10550]: Making attempt 5 at 
> processing message 9CC2E45321.A7F02 
> Oct 11 09:33:09 cube MailScanner[10550]: New Batch: Scanning 1 
> messages, 14245 bytes 
> Oct 11 09:33:09 cube MailScanner[10550]: Virus and Content Scanning: 
> Starting 
> 
> Since I don't get any errors I don't really where to continue looking. 
> Anyone see anything obvious? 
> 
> I'm using MailWatch, Debian 8.6 and postfix 2.11.3. 
> 
> /Daniel 
> 
> 

-- 
MailScanner mailing list 
mailscanner at lists.mailscanner.info 
http://lists.mailscanner.info/mailman/listinfo/mailscanner 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mailscanner.info/pipermail/mailscanner/attachments/20161011/e061d548/attachment.html>