https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6698
--- Comment #5 from Sidney Markowitz <[email protected]> 2011-11-12 05:55:02 UTC --- I've been convinced by some off-list emails that it is not be true to say that just because the optional DCC.pm plugin requires the dcc software to work after it is enabled, that enabling the plugin in SpamAssassin without distributing the dcc software would violate the ASF third-party software criteria. The ASF policy that the criteria relate to says http://www.apache.org/legal/resolved.html#optional "Can Apache projects rely on components whose licensing affects the Apache product? Apache projects cannot distribute any such components. However, if the component is only needed for optional features, a project can provide the user with instructions on how to obtain and install the non-included work. Optional means that the component is not required for standard use of the product or for the product to achieve a desirable level of quality. The question to ask yourself in this situation is: 'Will the majority of users want to use my product without adding the optional components?'" That says we cannot distribute the dcc software. We can distribute DCC.pm and make it an optional feature. However, I agree with not enabling the plugin by default. It is just plain ugly to have it enabled when it cannot work because required software is not installed. Here is another proposed wording: Note that DCC is disabled by default in C<v310.pre> because its use requires software that is not distributed with SpamAssassin and that has license restrictions for certain commercial uses. See the DCC license at http://www.dcc-servers.net/dcc/LICENSE for details. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
