[dev] [commits] Horde branch master updated. f13f13083d82d1a51389c8f6b54b8050655c8cf8

[Jan Schneider]

Zitat von Michael M Slusarz <slusarz at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
>> The branch "master" has been updated.
>> The following is a summary of the commits.
>>
>> from: 69d439d3de6ebc024ecdacb8f57e472baebe9d30
>>
>> f13f130 [jan] Re-add option to report messages as spam/ham through  
>> redirection.
>>
>> -----------------------------------------------------------------------
>>
>> commit f13f13083d82d1a51389c8f6b54b8050655c8cf8
>> Author: Jan Schneider <jan at horde.org>
>> Date:   Fri Jun 1 16:13:32 2012 +0200
>>
>>    [jan] Re-add option to report messages as spam/ham through redirection.
>>
>> imp/config/conf.xml |    8 +++++
>> imp/docs/CHANGES    |    1 +
>> imp/lib/Compose.php |   18 ++++++++-----
>> imp/lib/Spam.php    |   72  
>> ++++++++++++++++++++++++++++++--------------------
>> imp/package.xml     |    2 +
>> 5 files changed, 65 insertions(+), 36 deletions(-)
>>
>> http://git.horde.org/horde-git/-/commit/f13f13083d82d1a51389c8f6b54b8050655c8cf8
>
> This should be added as a new hook instead.  Or modify the existing  
> spam_email hook to encompass both setting an email address AND  
> modifying the contents.  We don't want spam configuration located in  
> two entirely different configuration files.

Not sure what you mean, this flag is in the same spam configuration  
section in the same configuration file.

> And just for my own information: what spam reporting service doesn't  
> support multipart/digest emails?  All spam reporters that I know of  
> that use signature based detection work fine with multipart/digest.

I don't know which solution/service exactly this is, but this for some  
existing service at a client's site, and I wasn't able to convince  
them to a different solution.

-- 
Jan Schneider
The Horde Project
http://www.horde.org/