Bug 294070 - KMail2 does not detect spamd filtering
Summary: KMail2 does not detect spamd filtering
Status: RESOLVED UPSTREAM
Alias: None
Product: kmail2
Classification: Applications
Component: filtering (show other bugs)
Version: 4.8
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-14 13:49 UTC by Burroughs
Modified: 2012-02-16 11:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Burroughs 2012-02-14 13:49:22 UTC
Version:           4.8 (using KDE 4.8.0) 
OS:                Linux

If launching the wizard to setup spamd as the default application anti-spam filtering method, KMail2 answers no software of this kind is present in the system.

Reproducible: Always

Steps to Reproduce:
KMail2>>Tools>>antispam wizard.

Actual Results:  
No spamd is present in the system.

Expected Results:  
Spamd should be found.

These are the paths in my Arch Linux installation containing the spamd daemon:

/etc/conf.d/spamd
/etc/rc.d/spamd
/usr/bin/spamd
/usr/bin/vendor_perl/spamd
Comment 1 Laurent Montel 2012-02-14 18:24:23 UTC
We use 

echo "From: test" | spamc -x && spamassassin -V | grep "SpamAssassin version 3"

to test if spamd is ok.
could you test it ?
Comment 2 Burroughs 2012-02-14 18:35:42 UTC
(In reply to comment #1)
> We use 
> 
> echo "From: test" | spamc -x && spamassassin -V | grep "SpamAssassin version 3"
> 
> to test if spamd is ok.
> could you test it ?

This is what I get:

[alutri@andy ~]$ echo "From: test" | spamc -x && spamassassin -V | grep "SpamAssassin version 3"
Received: from localhost by andy.mytech.org
        with SpamAssassin (version 3.3.2);
        Tue, 14 Feb 2012 19:30:42 +0100
From: test
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on andy.mytech.org
X-Spam-Flag: YES
X-Spam-Level: ********
X-Spam-Status: Yes, score=8.1 required=5.0 tests=EMPTY_MESSAGE,
        FH_FROMEML_NOTLD,MISSING_DATE,MISSING_HEADERS,MISSING_MID,MISSING_SUBJECT,
        NO_HEADERS_MESSAGE,NO_RECEIVED,NO_RELAYS autolearn=no version=3.3.2
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_4F3AA852.C1CFF4A3"

This is a multi-part message in MIME format.

------------=_4F3AA852.C1CFF4A3
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Spam detection software, running on the system "andy.mytech.org", has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
root@localhost for details.

Content preview:  [...] 

Content analysis details:   (8.1 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 1.1 FH_FROMEML_NOTLD       E-mail address doesn't have TLD (.com, etc.)
-0.0 NO_RELAYS              Informational: message was not relayed via SMTP
 1.0 MISSING_HEADERS        Missing To: header
 0.5 MISSING_MID            Missing Message-Id: header
 1.8 MISSING_SUBJECT        Missing Subject: header
 2.3 EMPTY_MESSAGE          Message appears to have no textual parts and no
                            Subject: text
-0.0 NO_RECEIVED            Informational: message has no Received headers
 1.4 MISSING_DATE           Missing Date: header
 0.0 NO_HEADERS_MESSAGE     Message appears to be missing most RFC-822 headers



------------=_4F3AA852.C1CFF4A3
Content-Type: message/rfc822; x-spam-type=original
Content-Description: original message before SpamAssassin
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

From: test

------------=_4F3AA852.C1CFF4A3--

bash: spamassassin: command not found
Comment 3 Laurent Montel 2012-02-14 21:56:46 UTC
'bash: spamassassin: command not found'
so you have your solution
=> install spamassassin
Comment 4 Burroughs 2012-02-15 09:38:15 UTC
(In reply to comment #3)
> 'bash: spamassassin: command not found'
> so you have your solution
> => install spamassassin

Spamassassin was installed, of course (I use since... well, I dont't remember but we're speaking about years).
The fact is that the Arch Linux package doesn't install the executable spamassassin in the main path (/usr/bin) so I had to add a symbolic link to fix the problem...
Anyway, thanks tor helping me find out the trick.
Comment 5 Laurent Montel 2012-02-15 18:44:11 UTC
it's ok now ?
Comment 6 Burroughs 2012-02-16 10:53:00 UTC
(In reply to comment #5)
> it's ok now ?

Yes, spamd is being detected correctly.
Anyway, don't know if this "bug" can be extended to other distributions as well: for instance, if Debian or Ubuntu don't create a symbolic link to the spamassassin or spamc executables, there may be the same problems.
Apart from this, Laurent, please take a look at the second bug I reported (#294071): it's much more dangerous, imho.
Comment 7 Laurent Montel 2012-02-16 11:20:28 UTC
It's a bug from distro. now kmail I will close it.

Will look at 294071