svn commit: r484357 - head/mail/spamassassin

Niclas Zeising zeising at freebsd.org
Wed Nov 7 09:33:05 UTC 2018


On 11/7/18 10:22 AM, Baptiste Daroussin wrote:
> On Wed, Nov 07, 2018 at 10:17:50AM +0100, Niclas Zeising wrote:
>> On 11/7/18 10:10 AM, Koichiro Iwao wrote:
>>> On Wed, Nov 07, 2018 at 09:31:05AM +0100, Baptiste Daroussin wrote:
>>>> Is there still a need for the japanese spamassassin? if yes, can't the specific
>>>> patch be incorporated in the regular one?
>>>>
>>>> That would simplify the life of many people to have only one spamassassin
>>>>
>>>> Bapt
>>>
>>> AFAIK yes. Additional patch improves spam detection accuracy on emails written
>>> in Japanese but using mail/spamassassin's accuracy is not too bad.
>>>
>>> Regarding the current japanese/spamassassin port, I think it is deprecated. It
>>> is created for the old version of spamassassin and not updated for years.
>>>
>>> I can found another Japanese tokenizer patch for the latest
>>> spamassassin. The port should be renewed based on this:
>>>
>>> https://github.com/heartbeatsjp/spamassassin_ja
>>>
>>
>> Hi!
>> japanese/spamassassin is up for grabs.  If you are interested in maintaining
>> it and in updating it with that patch, I can help a little. I don't have
>> time to maintain it myself.
>> Regards
> 
> Can't those patches be available in the files directory on the
> mail/spamassassins so we have one single port to maintain?
> 

I don't know why japanese/spamassassin was made into a separate port to 
begin with, it's been that way since I took over maintainership over 
mail/spamassassin.

Looking at SVN history it seems like japanese/spamassassin was created 
because the patch was for an older version of spamassassin originally, 
so two different versions were needed.

Regards
-- 
Niclas Zeising


More information about the svn-ports-all mailing list