From owner-freebsd-questions@freebsd.org Wed Sep 9 12:09:11 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CD45A0049F for ; Wed, 9 Sep 2015 12:09:11 +0000 (UTC) (envelope-from gandalf@shopzeus.com) Received: from fep24.mx.upcmail.net (fep24.mx.upcmail.net [62.179.121.44]) by mx1.freebsd.org (Postfix) with ESMTP id 50A771F7B for ; Wed, 9 Sep 2015 12:09:09 +0000 (UTC) (envelope-from gandalf@shopzeus.com) Received: from edge02.upcmail.net ([192.168.13.237]) by viefep31-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20150909115957.HOGM18055.viefep31-int.chello.at@edge02.upcmail.net> for ; Wed, 9 Sep 2015 13:59:57 +0200 Received: from [192.168.1.160] ([86.101.30.40]) by edge02.upcmail.net with edge id F08B1r00C0rw6r20108Bgw; Wed, 09 Sep 2015 14:08:13 +0200 X-SourceIP: 86.101.30.40 To: freebsd-questions@freebsd.org From: =?UTF-8?Q?Nagy_L=c3=a1szl=c3=b3_Zsolt?= Subject: Cannot test spamassassin, what is going on here? Message-ID: <55F0212B.9090708@shopzeus.com> Date: Wed, 9 Sep 2015 14:08:11 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2015 12:09:11 -0000 Given a test file "test.eml" I can run this test: spamassassin -t test.eml and I get this: > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > Spam detection software, running on the system "shopzeus.com", > has NOT identified this incoming email as spam. The original > message has been attached to this so you can view it or label > similar future email. If you have any questions, see > The administrator of that system for details. > > Content preview: We've run into ths bug: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148581 > [libc] fopen(3) fails with EMFILE if there are more than SHORT_MAX > fds open > [...] > > Content analysis details: (-5.0 points, 5.0 required) > > pts rule name description > ---- ---------------------- > -------------------------------------------------- > -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at > http://www.dnswl.org/, high > trust > [8.8.178.116 listed in list.dnswl.org] However, the very same email went through postfix/Mailscanner and resulted in these headers: > X-shopzeus-MailScanner-Information: Please contact the ISP for more information > X-shopzeus-MailScanner-ID: 4FFF48895E15.AB608 > X-shopzeus-MailScanner: Found to be clean > X-shopzeus-MailScanner-SpamCheck: spam, JUNKEMAIL > X-shopzeus-MailScanner-From: owner-freebsd-questions@freebsd.org > X-Spam-Status: Yes So the "spamassassin -t" command gives -5.0 score identifying as ham, but when the email actually comes in then it is identified as spam. Looks like spamassassin is using different rules/settings when it is ran from the mailscanner daemon. The configuration should be the same ( /usr/local/etc/mail/spamassassin is a symbolic link to /usr/local/etc/MailScanner/spam.assassin.prefs.conf ) I cannot test spamassassin with the same user, because it is postfix which is disabled: > > # su postfix " spamassassin -t test.eml " > This account is currently not available. How to overcome this problem? What is going on here? Thanks Laszlo