[horde] Blacklist and forwarding

[Simon Wilson]

----- Message from Vilius Sumskas/LNK <vilius at lnk.lt> ---------
    Date: Wed, 9 Oct 2013 01:39:38 +0300
    From: Vilius Sumskas/LNK <vilius at lnk.lt>
Subject: Re: [horde] Blacklist and forwarding
      To: horde at lists.horde.org


>>>>> I have a SPAM control system that allows users to train it for
>>>> better
>>>>> results. They send spam mail to spam at mydomain e ham to
>>>> notspam at mydomain. I
>>>>> would like to integrate the Horde Blacklist feature with this. I
>>>> mean, when
>>>>> the user right-click an e-mail and mark it to blacklist, after
>>>> horde
>>>>> performs its actions (move to trash or something like that), the
>>>> mail would
>>>>> be forwarded to the spam at mydomain address.
>>>>>
>>>>>
>>>>>
>>>>> Is that possible?
>>>>
>>>> Not without editing the code.
>>>
>>>
>>> Excuse me for jumping into thread like this but wouldn't it be
>>> possible to create a shell script which sends email and use it in
>>
>>> IMP's Spam/Ham reporting in place of ordinary spamassassin reports?
>>
>>> If I remember correctly it was possible in H4.
>>
>> That's not what he's asking though.  He wants an action to take place
>>
>> on clicking the *blacklist* button (not the Report Spam button).
>>
>> Currently, clicking the blacklist button does nothing more than
>> sending the e-mail address to the blacklist registry API call
>> (handled
>> by ingo).  There's nothing currently in-between the user action and
>>
>> the API call that allows someone to add a hook.
>
> Then probably a shell script could do both :), 1) report spam and 2)  
> include emails into blacklist through PHP CLI using Horde API call.
>
> Obviously users should be trained to use Report Spam instead of  
> Blacklist then.
>
> However, Andre, you should not mix these two different features.  
> Blacklist is not really for spam addresses these days. Spammers  
> change email addresses pretty often or send spam from non-existent  
> addresses, so you just end up with a big pile of email addresses  
> which uses more and more server resources to process but provides  
> very little of value. Blacklist comes in handly only if you would  
> like to block one particular known real sender (a newsletter without  
> unsubscribtion address for example), or if you want to block whole  
> domain (*@*.ch) etc.
>
> --
>    Vilius

I ran into issues with domain level filtering using Ingo blacklist  
last year -  
http://lists.horde.org/archives/horde/Week-of-Mon-20121001/044879.html

Not sure if it's changed since then.

Simon

--
Simon Wilson
M: 0400 12 11 16
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 1339 bytes
Desc: PGP Public Key
URL: <http://lists.horde.org/archives/horde/attachments/20131009/ecef0f41/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: PGP Digital Signature
URL: <http://lists.horde.org/archives/horde/attachments/20131009/ecef0f41/attachment-0001.bin>