ARTISTIC, BSD, GPL-2, LGPL-2
Also other licenses may apply, see files/symlinks in LICENSES/ subdirectory.
Below "you" is defined as packager, not as recipient of that package. The packager must indicate which license(s) have been chosen to apply.
If the end-user is unhappy with packager chosen license combination, the end-user can always default back to ZMailer.ORG original version. (Of course, possibly loosing packagers additional features not present in original version.)
The license for ZMailer is herewith set as: "pick any you like":
ARTISTIC: The PERL way; respect copyrights, otherwise do whatever you like, preferrably also contribute changes to the baseline. Details are in the file. BSD: Demands only, that you don't remove copyright notices. Otherwise you are free to e.g. hoard your changes / new features. Details are in the file. GPL-2 / LGPL-2: Of these the LGPL is applicable to all parts of ZMailer that are libraries, or you were able to otherwise embed in librarized form for other uses than directly related to ZMailer.. Otherwise use GPL.
Demands contributing changes back to the baseline or very least redistributing (or offering to..) possibly modified sources long with binaries, etc. Details are in the file.
I (Matti Aarnio) have also contemplated adapting Mozilla/Netscape community license, or Qt's QPL, but those go a tad far in demands of wanting the modifications to be made available to the original author(s). Similar worrysome things exist with GPLv3 proposal (2006 january). I am myself somewhat partial towards use of "ARTISTIC".
I have (probably) somewhere emails, where Rayan Zachariassen said, he wanted to publish completed thing under GPL(v1).
In every case:
THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.and:
Disputes with Matti Aarnio (current primary maintainer) shall be handled per Finnish laws in Helsinki City Courts.
Matti Aarnio - email@example.com - firstname.lastname@example.org - 2003-06-27, 2006-01-28