Bug 102856 - Parse Spam Status from MailScanner headers
Summary: Parse Spam Status from MailScanner headers
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.8
Platform: Slackware Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-30 15:33 UTC by Thanos Kyritsis
Modified: 2012-09-10 01:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thanos Kyritsis 2005-03-30 15:33:45 UTC
Version:           1.8 (using KDE KDE 3.4.0)
Installed from:    Slackware Packages
OS:                Linux

As it is right now, Kmail can parse and show fancy headers from the X-Spam-* headers.

Could you please parse the X-*-MailScanner-* headers as well ?? An example of Mailscanner Headers is the following:

X-ISP_name_here-MailScanner: Found to be clean
X-ISP_name_here-MailScanner-SpamCheck: not spam, SpamAssassin (score=-2.599,
	required 5, autolearn=not spam, AWL 0.00, BAYES_00 -2.60,
	SPF_HELO_PASS -0.00)

I guess it's the same thing to extract the spam status information kmail needs from the above headers as it is to extract them from the following headers:

X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on ISP_name_here
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Comment 1 Andreas Gungl 2005-07-31 13:22:03 UTC
Can you point me to a detailed description of the possible content in the MailScanner headers? I would need to know all variants to be able to provide a serious implementation.
Comment 2 Thanos Kyritsis 2005-10-22 11:19:09 UTC
Unfortunatelly, MailScanner devs don't provide such a detailed description of the possible content in the MailScanner headers.

The headers follow this format:

X-*-MailScanner-SpamCheck: with a detailed SA scoring information, for example:
not spam, SpamAssassin (score=-2.102,required 5, autolearn=not spam, AWL 0.50, BAYES_00 -2.60)

and there is also this:

X-*-MailScanner-SpamScore:
header which will by default contain 1 's' for every point of the
SpamAssassin score. 

All you need to do is measure the number of 's' characters and you have the score. Or you can take it directly from the X-*-MailScanner-SpamCheck header.
Comment 3 Myriam Schweingruber 2012-08-18 08:07:33 UTC
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented.
Thank you for your understanding.
Comment 4 Luigi Toscano 2012-08-19 00:42:23 UTC
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.
Comment 5 Thanos Kyritsis 2012-09-07 07:47:11 UTC
To be honest, it's been 7 years since I reported it, no hard feelings there though, I know it was never a top priority or a major feature, but I've switched several Desktop Environments and mail clients since then :) (for totally different reasons), but I'm still on the same Open Source "train". I propose we close this feature request for the time being and if/when I move back to Kmail, I will certainly look for this feature once more :) Best Wishes
Comment 6 Myriam Schweingruber 2012-09-10 01:49:41 UTC
Thank you for the feedback.