taskSavannah Administration - Tasks: task #14387, Submission of Gene Hightower's...

 
 

task #14387: Submission of Gene Hightower's SMTP server

Submitter:  Gene Hightower <Digilicious>
Submitted:  Sun 26 Feb 2017 06:59:07 PM UTC
   
 
Should Start On:  Sun 26 Feb 2017 08:00:00 AM UTC Should be Finished on:  Wed 08 Mar 2017 08:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Cancelled Privacy:  Public
Assigned to:  ineiev Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Wed 08 Mar 2017 06:24:33 AM UTC, comment #12: 

Thank you; cancelling.

Ineiev <ineiev>
Site Administrator
Wed 08 Mar 2017 01:28:56 AM UTC, comment #11: 

Thanks, but no thanks.  Please disregard my request to host my project at Savannah.

Gene Hightower <Digilicious>
Thu 02 Mar 2017 10:21:06 PM UTC, comment #10: 

Gene: the simple way out for README etc. is to add a line that says "This file is public domain."

For files with a particular format where it's inconvenient or impossible to accept comments, just put a similar statement in a README. "The files X, Y, Z are public domain."

Generated files: it's best if the generation includes generating a license statement, like (e.g.) autoconf does. If it stays.

FWIW ...

Karl Berry <karl>
Site Administrator
Thu 02 Mar 2017 08:22:43 AM UTC, comment #9: 

black, white, ip-black, ip-white: Where do they come from? The format seems quite simple, why can't it include comments?

_clang-format: Automatically generated files are typically not included in source code; are there reasons this file should be included at all?

input.txt and README: If a file has no copyright and licensing terms, it technically can't be redistributed.  Your users would have to remove those files in order to avoid legal risks.
https://www.gnu.org/prep/maintain/html_node/License-Notices.html

Ineiev <ineiev>
Site Administrator
Wed 01 Mar 2017 04:30:06 PM UTC, comment #8: 

No, the files black, white, ip-black, ip-white are simply lists of
domain or IP address.  They are data files with specific format
requirements.  There is no way to add comments to these files.

The file _clang-format was automatically generated.

The file input.txt is SMTP protocol data.  It is used as test input to
the server.

I guess I could add a copyright notice to the README file, but I just
don't want to.


Gene Hightower <Digilicious>
Wed 01 Mar 2017 02:48:36 PM UTC, comment #7: 

Some files (black, white, ip-black, ip-white, _clang-format, input.txt,
README) lack copyright and licensing notices; could you fix them?

Ineiev <ineiev>
Site Administrator
Tue 28 Feb 2017 09:53:59 PM UTC, comment #6: 

There is no other third-party GPLv3 code in the present case, is there? Not seeing any in Gene's list.

Since this exception is used in GNU packages, I think Savannah (clearly) should accept it.

Down-the-road hackers would always have the option of removing the permission, and the dependency on OpenSSL, e.g., if they wanted to combine this package with other GPLv3 code that doesn't have the additional permission.

Karl Berry <karl>
Site Administrator
Tue 28 Feb 2017 05:49:47 AM UTC, comment #5: 

Err.. but the exception shan't apply to arbitrary third party's GPLv3+-ed code the user may want to combine with this package: I mean, the package with such exception may not be strictly GPLv3+-compatible.

Karl, what do you think?

Ineiev <ineiev>
Site Administrator
Mon 27 Feb 2017 11:51:13 PM UTC, comment #4: 

I have added the additional permission notice to each source file.

New tarball can be found at:
https://digilicious.com/ghsmtp.tar.gz

Gene Hightower <Digilicious>
Mon 27 Feb 2017 10:55:22 PM UTC, comment #3: 

Yes, the openssl license is incompatible with the (A)GPL. It is explicitl stated in the FSF license-list file.
https://www.gnu.org/licenses/license-list.html#OpenSSL

The simplest way out, assuming the usage is intended to be permitted (as it clearly is here), is to add an additional permission to the files as is done in, e.g., wget:

--------------------------
Additional permission under GNU GPL version 3 section 7

If you modify this program, or any covered work, by linking or
combining it with the OpenSSL project's OpenSSL library (or a
modified version of that library), containing parts covered by the
terms of the OpenSSL or SSLeay licenses, the Free Software Foundation
grants you additional permission to convey the resulting work.
Corresponding Source for a non-source form of such a combination
shall include the source code for the parts of OpenSSL used as well
as that of the covered work.
---------------------------------

Gene: regarding the argument of no distribution of the combined work, no, that's not sufficient (per FSF legal advice). if a program P is intended to be linked with module M, then P's and M's licenses in combination must be compatible, even if M is not physically distributed with P.

It may not be intuitive, but that's where we are. Here's an exchange between rms and haible regarding GPL'd readline and at-the-time-not-GPL'd clisp (which was not distributing readline, "just" using it) which is essentially the same issue. Search for "subterfuge" for the crucial message.

As best I understand things ...


Karl Berry <karl>
Site Administrator
Mon 27 Feb 2017 05:28:37 PM UTC, comment #2: 

Depends on what you want to do.

I am not a lawyer or a judge, but as I understand it the
incompatibility would occur only if one wanted to create and
distribute a “Combined Work” based on both OpenSSL and ghsmtp.

I do not expect that ghsmtp will be distributed that way.

I expect ghsmtp to be pulled as source code and used by people to
create their own email servers on their own computers.

Gene Hightower <Digilicious>
Mon 27 Feb 2017 05:01:04 PM UTC, comment #1: 
Ineiev <ineiev>
Site Administrator
Sun 26 Feb 2017 06:59:07 PM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards the registration.


Registration Administration


While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):



Registration Details


  • Name: Gene Hightower's SMTP server
  • System Name:  ghsmtp
  • Type: non-GNU software and documentation
  • License: Other (AGPLv3)





Description:

Gene Hightower's simple SMTP server.

A program to receive Internet (RFC 5321) mail.

Written using Standard C++.

No runtime configuration file — code as configuration.

Run it from (x)inetd or daemontools as a non-root user.  It will accept mail and store it in that user's ~/Maildir.



Other Software Required:

Ragel
MIT + exception
<https://www.colm.net/open-source/ragel/>

OpenSSL
Apache License 1.0 and 4-clause BSD License
<https://www.openssl.org/>

boost
Boost Software License
<https://boost.org/>

ldns
3-clause BSD
<https://www.nlnetlabs.nl/projects/ldns/>

libspf2
LGPL2.1+ or 2-clause BSD
<http://www.libspf2.org/>

regdom
Apache License
<https://github.com/usrflo/registered-domain-libs.git>

TinyCDB
Public Domain
<http://www.corpit.ru/mjt/tinycdb.html>

glog
3-clause BSD
<https://code.google.com/archive/p/google-glog/>



Tarball URL:

https://savannah.gnu.org/submissions_uploads/ghsmtp.tar.gz


Gene Hightower <Digilicious>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by karl (Posted a comment)
  • -email is unavailable- added by ineiev (Posted a comment)
  • -email is unavailable- added by Digilicious (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-03-08 ineiev StatusIn Progress Cancelled
        Open/ClosedOpen Closed
    2017-02-27 ineiev StatusNone In Progress
        Assigned toNone ineiev

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code