skipping message ... and stopping scanning until 'postsuper -r
ALL'
Martin Hepworth
maxsec at gmail.com
Thu Nov 3 19:43:12 GMT 2011
always this message or repeats it even if you remove that message?
--
Martin Hepworth
Oxford, UK
On 3 November 2011 11:10, Alessandro Dentella <sandro at e-den.it> wrote:
> Hi,
>
>
> I have a debian squeeze box w/ MailScanner 4.84.3 and postfix 2.7.1 +
> baruwa
> 1.1.1. This should be almost a clone of a working setup I did myself some
> months ago and is still working.
>
> The problem
> ===========
>
> The problem now is that mailscanner stops processing mails until u run
> "postfix -r ALL", it processes the queue and stops again. I have
> mailscanner
> pick incoming postfix queue via 'header_checks'. If I commenti it (and
> bypass mailscanner) mail don't get stuck.
>
> The logs
> ========
>
> When MS stops scanning mail, it starts complaining in mail.log that
>
> MailScanner[28558]: Warning: skipping message 06A602E1BA8.AFAE8 as it
> has been attempted too many times
> MailScanner[28558]: Quarantined message 06A602E1BA8.AFAE8 as it caused
> MailScanner to crash several times
>
> This goes on forever, content of Processing.db:
>
>
> baruwa:/var/spool/MailScanner/incoming# sqlite3 Processing.db .dump
> PRAGMA foreign_keys=OFF;
> BEGIN TRANSACTION;
> CREATE TABLE processing (id TEXT, count INT, nexttime INT);
> INSERT INTO "processing" VALUES('06A602E1BA8.AFAE8',6,1320255994);
> INSERT INTO "processing" VALUES('06CD02E06BC.A7D24',2,1320264046);
> CREATE TABLE archive (id TEXT, count INT, nexttime INT);
> CREATE UNIQUE INDEX id_uniq ON processing(id);
> COMMIT;
>
>
> Some questions to debug
> =======================
>
> I'd like to understand:
>
> 1. Where is the message with id 06A602E1BA8.AFAE8 stored? I thought it was
> under /var/spool/MailScanner but I can't find it anywhere.
>
> 2. Why does MailScanner processes again the message if it believe it should
> be skipped?
>
> 3. How can I diagnose why MailScanner stops scanning new messages?
> syslog helps saying:
>
> Process did not exit cleanly, returned 255 with signal 0
>
> but nothing more. MailScanner --lint seems not to complain of
> anything... (below the result).
>
> Any help is really appreciated
>
> thanks in advance
> sandro
> *:-)
>
> --
> Sandro Dentella *:-)
> http://www.reteisi.org Soluzioni libere per le scuole
> http://sqlkit.argolinux.org SQLkit home page -
> PyGTK/python/sqlalchemy
>
>
> /var/log/mail.log
> ===================
>
> ... MailScanner[28558]: Warning: skipping message 06A602E1BA8.AFAE8 as it
> has been attempted too many times
> ... MailScanner[28558]: Quarantined message 06A602E1BA8.AFAE8 as it caused
> MailScanner to crash several times
> ... MailScanner[28563]: MailScanner E-Mail Virus Scanner version 4.84.3
> starting...
> ... MailScanner[28563]: Reading configuration file
> /etc/MailScanner/MailScanner.conf
> ... MailScanner[28563]: Reading configuration file
> /etc/MailScanner/conf.d/baruwa.conf
> ... MailScanner[28563]: Reading configuration file
> /etc/MailScanner/conf.d/mit.conf
> ... MailScanner[28563]: Read 869 hostnames from the phishing whitelist
> ... MailScanner[28563]: Read 4252 hostnames from the phishing blacklists
> ... MailScanner[28563]: Config: calling custom init function BaruwaLowScore
> ... MailScanner[28563]: Baruwa: Populating spam score settings
> ... MailScanner[28563]: Baruwa: no spam score settings found using defaults
> ... MailScanner[28563]: Config: calling custom init function
> BaruwaBlacklist
> ... MailScanner[28563]: Baruwa: Starting blacklists
> ... MailScanner[28563]: Baruwa: Read 0 blacklist items
> ... MailScanner[28563]: Baruwa: Ip blocks blacklisted:
> ... MailScanner[28563]: Config: calling custom init function BaruwaSQL
> ... MailScanner[28564]: Baruwa: Starting SQL logger
> ... MailScanner[28563]: Config: calling custom init function
> BaruwaHighScore
> ... MailScanner[28563]: Baruwa: Populating high spam score settings
> ... MailScanner[28563]: Baruwa: no high spam score settings found using
> defaults
> ... MailScanner[28563]: Config: calling custom init function
> BaruwaWhitelist
> ... MailScanner[28563]: Baruwa: Starting whitelists
> ... MailScanner[28563]: Baruwa: Read 0 whitelist items
> ... MailScanner[28563]: Baruwa: Ip blocks whitelisted:
> ... MailScanner[28563]: Using SpamAssassin results cache
> ... MailScanner[28563]: Connected to SpamAssassin cache database
> ... MailScanner[28563]: Connected to Processing Attempts Database
> ... MailScanner[28563]: Found 1 messages in the Processing Attempts
> Database
> ... MailScanner[28563]: Using locktype = flock
> ... MailScanner[28563]: Warning: skipping message 06A602E1BA8.AFAE8 as it
> has been attempted too many times
>
>
>
> MailScanner --lint
> =====================
>
> baruwa-thunder:/var/spool/MailScanner/incoming# MailScanner --lint
> Trying to setlogsock(unix)
>
> Reading configuration file /etc/MailScanner/MailScanner.conf
> Reading configuration file /etc/MailScanner/conf.d/baruwa.conf
> Reading configuration file /etc/MailScanner/conf.d/mit.conf
> Read 869 hostnames from the phishing whitelist
> Read 4252 hostnames from the phishing blacklists
> Config: calling custom init function BaruwaLowScore
> Baruwa: Populating spam score settings
> Baruwa: no spam score settings found using defaults
> Config: calling custom init function BaruwaBlacklist
> Baruwa: Starting blacklists
> Baruwa: Read 0 blacklist items
> Baruwa: Ip blocks blacklisted:
> Config: calling custom init function BaruwaSQL
> Baruwa: Starting SQL logger
> Config: calling custom init function BaruwaHighScore
> Baruwa: Populating high spam score settings
> Baruwa: no high spam score settings found using defaults
> Config: calling custom init function BaruwaWhitelist
> Baruwa: Starting whitelists
> Baruwa: Read 0 whitelist items
> Baruwa: Ip blocks whitelisted:
>
> Checking version numbers...
> Version number in MailScanner.conf (4.84.3) is correct.
>
> Your envelope_sender_header in spam.assassin.prefs.conf is correct.
> MailScanner setting GID to (33)
> MailScanner setting UID to (103)
>
> Checking for SpamAssassin errors (if you use it)...
> Using SpamAssassin results cache
> Connected to SpamAssassin cache database
> SpamAssassin reported no errors.
> Connected to Processing Attempts Database
> Created Processing Attempts Database successfully
> There are 2 messages in the Processing Attempts Database
> Using locktype = posix
> MailScanner.conf says "Virus Scanners = clamd"
> Found these virus scanners installed: clamd
> ===========================================================================
> Virus and Content Scanning: Starting
> ===========================================================================
>
> If any of your virus scanners (clamd)
> are not listed there, you should check that they are installed correctly
> and that MailScanner is finding them correctly via its virus.scanners.conf.
> Config: calling custom end function BaruwaLowScore
> Baruwa: Shutting down spam score settings
> Config: calling custom end function BaruwaBlacklist
> Baruwa: Shutting down blacklists
> Config: calling custom end function BaruwaSQL
> Baruwa: Shutting down SQL logger
> Config: calling custom end function BaruwaHighScore
> Baruwa: Shutting down high spam score settings
> Config: calling custom end function BaruwaWhitelist
> Baruwa: Shutting down whitelists
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20111103/4daae3d4/attachment.html
More information about the MailScanner
mailing list