Bug 4204 - Remove dcc from list of default plugins
Summary: Remove dcc from list of default plugins
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Plugins (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 normal
Target Milestone: 3.1.0
Assignee: Daniel Quinlan
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-18 11:06 UTC by Justin Mason
Modified: 2005-03-18 06:00 UTC (History)
1 user (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Mason 2005-03-18 11:06:16 UTC 
http://www.rhyolite.com/pipermail/dcc/2005/002572.html says:

> So I'm close to signing an agreement with Commtouch that
> includes support for those ideas.  It requires changes to the license
> for versions of the DCC source after this week's.  The changed license
> is intended to leave the DCC as free as it was before except
> 
>    "... any entity which sells anti-spam solutions to others, or
>    provides an anti-spam solution as part of a security solution
>    sold to other entities, or to a private network which employs
>    DCC or uses data provided by operation of DCC but does not provide
>    corresponding data to other users."

IOW, dcc is no longer free software.
This means we need to take the same action we took with Razor, comment it out by
default in init.pre:

# Razor2 - perform Razor2 message checks.
#
# Razor2 is disabled here because it is not available for unlimited free
# use.  It is currently free for personal use, subject to capacity
# constraints.  See the Cloudmark SpamNet Service Policy for more details.
#
#loadplugin Mail::SpamAssassin::Plugin::Razor2

BTW, that change seems to have been made without ever opening a bug, which is
annoying, as it means finding the old correspondence about that issue is a lot
harder (requiring digging through mail archives).

ISTR Daniel talking about making our own, free hash-sharing plugin -- this may
be a good idea, since the field seems to be shrinking rapidly :(
Comment 1 Justin Mason 2005-03-18 11:09:06 UTC 
http://www.rhyolite.com/pipermail/dcc/2005/002590.html

the new license text:

 * Distributed Checksum Clearinghouse
 *
 * Copyright (c) 2005 by Rhyolite Software
 *
 * This agreement is not applicable to any entity which sells anti-spam
 * solutions to others or provides an anti-spam solution as part of a
 * security solution sold to other entities, or to a private network
 * which employes DCC or uses data provided by operation of DCC but does
 * not provide corresponding data to other users.
 *
 * Permission to use, copy, modify, and distribute this software for any
 * purpose with or without fee is hereby granted, provided that the above
 * copyright notice and this permission notice appear in all copies.
 *
 * Parties not eligible to receive a license under this agreement can 
 * obtain a commercial license to use DCC and permission to use
 * U.S. Patent 6,330,590 by contacting Commtouch at www.commtouch.com.
 *
 * THE SOFTWARE IS PROVIDED "AS IS" AND RHYOLITE SOFTWARE DISCLAIMS ALL
 * WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
 * OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL RHYOLITE SOFTWARE
 * BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES
 * OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
 * WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
 * ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
 * SOFTWARE.
Comment 2 Justin Mason 2005-03-18 12:13:47 UTC 
Matt Sergeant said:

>> ISTR Daniel talking about making our own, free hash-sharing plugin -- 
>> this may be a good idea, since the field seems to be shrinking rapidly :(
>
> Wouldn't that violate the patent in question?

possibly -- I haven't read the patent (as dictated by ASF policy ;)
Comment 3 Theo Van Dinter 2005-03-18 12:19:53 UTC 
Subject: Re:  Remove dcc from list of default plugins

On Fri, Mar 18, 2005 at 12:13:47PM -0800, bugzilla-daemon@bugzilla.spamassassin.org wrote:
> > Wouldn't that violate the patent in question?
> 
> possibly -- I haven't read the patent (as dictated by ASF policy ;)

Same here.  BTW: if we want to actively discuss this idea, it should either be
another ticket or a dev@ discussion.  This ticket should be a simple "disable
dcc by default" and then be closed.
Comment 4 Daniel Quinlan 2005-03-18 14:38:56 UTC 
Subject: Re:  Remove dcc from list of default plugins

I will go ahead and disable the plugin per our policy.  I think that's a
good call: self-consistent and appropriate.

In terms of the patent, please do not read it.  If we should want to
develop our own technology, it will be important to consult with an ASF
attorney.

Daniel
Comment 5 Daniel Quinlan 2005-03-18 14:48:04 UTC 
grabbing bug
Comment 6 Daniel Quinlan 2005-03-18 15:00:19 UTC 
done to HEAD