<p>What is the debug result for a gtube run, not eicar as you showed that to be fine...?<br>
The processing db thing kind of indicate that something is killing ms.</p>
<p>Cheers<br>
-- <br>
-- Glenn</p>
<div class="gmail_quote">Den 23 aug 2011 00:12 skrev &quot;John Bull&quot; &lt;<a href="mailto:jbull@esd113.org">jbull@esd113.org</a>&gt;:<br type="attribution">&gt; List,<br>&gt; <br>&gt; Testing Lab - Installation specifics:<br>
&gt; MailScanner-4.84.3-1.rpm.tar<br>&gt; Postfix 2.6.6<br>&gt; Scientific Linux 6.1, perl 5.10.1<br>&gt; High scoring spam is set to: store and notify<br>&gt; <br>&gt; Problem:<br>&gt; Email with gtube spam test remains in the Postfix hold queue and is not delivered to the spam quarantine.<br>
&gt; <br>&gt; # postqueue -p<br>&gt; -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------<br>&gt; EFF9C4EB9!      755 Mon Aug 22 13:22:51  jbull@esd113.lab<br>&gt;                                          tone@test.lab&lt;mailto:<a href="mailto:tone@test.lab">tone@test.lab</a>&gt;<br>
&gt; <br>&gt; MailScanner successfully creates /var/Spool/MailScanner/quarantine/&lt;date&gt;/spam<br>&gt; but the email never makes it there.<br>&gt; <br>&gt; Directory Permissions:<br>&gt; chown -R postfix.clamav /var/spool/MailScanner/incoming<br>
&gt; chmod -R 770 /var/spool/MailScanner/incoming<br>&gt; chown postfix.postfix /var/spool/MailScanner/incoming/SpamAssassin.cache.db<br>&gt; chown postfix.postfix -R /var/spool/MailScanner/incoming/SpamAssassin-Temp<br>&gt; chown postfix.postfix /var/spool/MailScanner/incoming/Processing.db<br>
&gt; <br>&gt; chown -R postfix.apache /var/spool/MailScanner/quarantine<br>&gt; chmod 770 -R /var/spool/MailScanner/quarantine<br>&gt; <br>&gt; mkdir /var/spool/MailScanner/spamassassin<br>&gt; chown -R postfix:postfix /var/spool/MailScanner/spamassassin<br>
&gt; chmod -R 770 /var/spool/MailScanner/spamassassin<br>&gt; <br>&gt; MailScanner Config<br>&gt; Run As User = postfix<br>&gt; Run As Group = postfix<br>&gt; Incoming Queue Dir = /var/spool/postfix/hold<br>&gt; Outgoing Queue Dir = /var/spool/postfix/incoming<br>
&gt; Incoming Work Dir = /var/spool/MailScanner/incoming<br>&gt; MTA = postfix<br>&gt; Sendmail = /usr/sbin/sendmail.postfix<br>&gt; Incoming Work Group = clamav<br>&gt; Incoming Work Permissions = 0644<br>&gt; Quarantine User = postfix<br>
&gt; Quarantine Group = apache<br>&gt; Quarantine Permissions = 0660<br>&gt; Virus Scanners = clamd<br>&gt; Quarantine Infections = no<br>&gt; Quarantine Whole Message = yes<br>&gt; Quarantine Whole Messages As Queue Files = no<br>
&gt; Keep Spam And MCP Archive Clean = yes<br>&gt; Spam Checks = yes<br>&gt; Is Definitely Not Spam = %rules-dir%/spam.whitelist.rules<br>&gt; Is Definitely Spam = %rules-dir%/spam.blacklist.rules<br>&gt; Definite Spam Is High Scoring = yes<br>
&gt; Use SpamAssassin = yes<br>&gt; Required SpamAssassin Score = 4.75<br>&gt; High SpamAssassin Score = 6<br>&gt; Spam Score = yes<br>&gt; Spam Actions = deliver<br>&gt; High Scoring Spam Actions = store notify<br>&gt; <br>
&gt; <br>&gt; Maillog:<br>&gt; Spam Checks: Starting<br>&gt; Aug 22 13:26:06 opened MailScanner[2548]: Message EFF9C4EB9.A5C23 from 192.168.0.110 (jbull@esd113.lab) to test.lab is spam, SpamAssassin (score=1001.99, required 4.75, autolearn=disabled, ALL_TRUSTED -1.00, DCC_CHECK 3.00, GTUBE 1000.00, T_RP_MATCHES_RCVD -0.01)<br>
&gt; Aug 22 13:26:06 opened MailScanner[2548]: Spam Checks: Found 1 spam messages<br>&gt; Aug 22 13:26:06 opened MailScanner[2548]: Spam Actions: message EFF9C4EB9.A5C23 actions are store,notify<br>&gt; Aug 22 13:26:06 opened MailScanner[2548]: Spam Actions: Notify tone@test.lab&lt;mailto:<a href="mailto:tone@test.lab">tone@test.lab</a>&gt;<br>
&gt; <br>&gt; : Warning: skipping message EFF9C4EB9.A5C23 as it has been attempted too many times<br>&gt; Aug 22 13:46:35 opened MailScanner[3396]: Quarantined message EFF9C4EB9.A5C23 as it caused MailScanner to crash several times<br>
&gt; <br>&gt; MailScanner --processing<br>&gt; Currently being processed:<br>&gt; <br>&gt; Number of messages: 1<br>&gt; Tries      Message              Next Try At<br>&gt; =====    =======                ===========<br>&gt; 6              EFF9C4EB9.A5C23            Mon Aug 22 13:49:34 2011<br>
&gt; <br>&gt; # MailScanner --lint --debug<br>&gt; Trying to setlogsock(unix)<br>&gt; <br>&gt; Reading configuration file /etc/MailScanner/MailScanner.conf<br>&gt; Reading configuration file /etc/MailScanner/conf.d/README<br>
&gt; Read 867 hostnames from the phishing whitelist<br>&gt; Read 4076 hostnames from the phishing blacklists<br>&gt; <br>&gt; Checking version numbers...<br>&gt; Version number in MailScanner.conf (4.84.3) is correct.<br>
&gt; MailScanner setting GID to  (89)<br>&gt; MailScanner setting UID to  (89)<br>&gt; <br>&gt; Checking for SpamAssassin errors (if you use it)...<br>&gt; Using SpamAssassin results cache<br>&gt; Connected to SpamAssassin cache database<br>
&gt; SpamAssassin reported no errors.<br>&gt; Connected to Processing Attempts Database<br>&gt; Created Processing Attempts Database successfully<br>&gt; There is 1 message in the Processing Attempts Database<br>&gt; Using locktype = posix<br>
&gt; MailScanner.conf says &quot;Virus Scanners = clamd&quot;<br>&gt; Found these virus scanners installed: clamd<br>&gt; ===========================================================================<br>&gt; Filename Checks: Windows/DOS Executable (1 <a href="http://eicar.com">eicar.com</a>)<br>
&gt; Other Checks: Found 1 problems<br>&gt; Virus and Content Scanning: Starting<br>&gt; Clamd::INFECTED:: Eicar-Test-Signature :: ./1/<a href="http://eicar.com">eicar.com</a><br>&gt; Virus Scanning: Clamd found 2 infections<br>
&gt; Infected message 1 came from 10.1.1.1<br>&gt; Virus Scanning: Found 2 viruses<br>&gt; ===========================================================================<br>&gt; Virus Scanner test reports:<br>&gt; Clamd said &quot;<a href="http://eicar.com">eicar.com</a> was infected: Eicar-Test-Signature&quot;<br>
&gt; <br>&gt; If any of your virus scanners (clamd)<br>&gt; are not listed there, you should check that they are installed correctly<br>&gt; and that MailScanner is finding them correctly via its virus.scanners.conf.<br>&gt; <br>
&gt; Thank you,<br>&gt; John<br></div>