Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.3
-
None
-
None
Description
In src/test/resources/testmsgs we have files with unknown copyright.
I guess they are test files from the Perl MIME-tools library written by
ZeeGee software (http://www.zeegee.com/products/MIME-tools/).
I also verified that every msg file (the original encoded messages are
only the msg files, the others are expanded/elaborated data/expected
results generated from that messages) is in the following file:
MIME-tools-6.200_02.tar.gz
I found that file here: http://search.cpan.org/~eryq/MIME-tools-6.200_02/
---------
The "MIME-tools" Perl5 toolkit.
Copyright (c) 1996 by Eryq. All rights reserved.
Copyright (c) 1999 by ZeeGee Software Inc. All rights reserved.
This program is free software; you can redistribute it and/or
modify it under the same terms as Perl itself.
You should have received a copy of the Perl license along with
Perl; see the file README in Perl distribution.
You should have received a copy of the GNU General Public License
along with Perl; see the file Copying. If not, write to
the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.
You should have received a copy of the Artistic License
along with Perl; see the file Artistic.
---------
Perl is distributed under the Artistic License:
http://www.perl.com/language/misc/Artistic.html
Artistic License is not listed in the 3rd party page:
http://people.apache.org/~cliffs/3party.html
>From a fast reading of the license I would say that it is a category B
license.
I don't know if proper NOTICE/LICENSE text allow us to include the test
suite (it is difficult for me to say if a MIME message is a source file
or a binary file).
That said I pass the microphone to someone with better legal knowledge.
Imho, if we can't have an official answer to this problem in a short
time we should simply remove that files. (we could even generate some
message with similar structure from scratch).
PS: Kudos to Bernd for his diligence in finding this issue.
--------------------
The best solution would be to create a new test suite based on artificially generated data (or public corpus, as Norman suggested: http://spamassassin.apache.org/publiccorpus/)