[drupal-devel] Licence issues using GPL'ed SquirrelMail code in mailhandler.module?

Mark Leicester mark.leicester at efurbishment.com
Sun May 22 16:11:09 UTC 2005

The approach I have taken is to lift a file containing the library 
function I need, and remove any other functions. I'm avoiding mixing 
Drupal and SM code. In theory this should aid maintainability, and 
enable us to quote the licence in full.

I'll contact the SM people too, so that I can double check their OK on 
this. They've written some nice handy functions I would really rather 
not rewrite! :)


On 22 May 2005, at 17:07, Evan Heidtmann wrote:

> The best option is to read the license and/or contact the Squirrelmail 
> folks.
> My understanding of the GPL is that everything is fair game as long as
> the same license applies. Squirrelmail's license appears to be vanilla
> GPL v2, so as long as your module has that license, you should be
> fine. The only thorn appears to be this condition for redistribution
> of modified copies (Section 2):
>     a) You must cause the modified files to carry prominent notices
>     stating that you changed the files and the date of any change.
> But since you're lifting code, not modifying existing files, I'm not
> sure what this means.
> Also, I am definitely not a lawyer. I may have no idea what I'm 
> talking about.
> Evan
> On 5/22/05, Mark Leicester <mark.leicester at efurbishment.com> wrote:
>> Hello all       ,
>> I'm making improvements to the mailhandler (and fixing the
>> drupal_special_chars problem by replacing with check_plain).
>> SquirrelMail already implements a very thorough URL parser, attachment
>> handler, and mail re-wrapper. SquirrelMail is GNU GPL, so I'm 
>> wondering
>> if I can re-use that code rather than reinvent. What are the licence
>> implications? Do we simply need to credit the SquirrelMail project and
>> redistribute the licence intact?
>> Regards,
>> Mark

More information about the drupal-devel mailing list