Mailing List Archive

[SpamAssassin Wiki] Updated: SaProxyStatus
Date: 2004-10-22T02:13:40
Editor: CasperTone2003 <spamassassin.z.caspertone2003@spamgourmet.com>
Wiki: SpamAssassin Wiki
Page: SaProxyStatus
URL: http://wiki.apache.org/spamassassin/SaProxyStatus

no comment

Change Log:

------------------------------------------------------------------------------
@@ -14,7 +14,19 @@

SaProxy "evolver and curator" said that [http://bugzilla.spamassassin.org/show_bug.cgi?id=2200 "We were unable to bring SAproxy/pop3proxy into the Apache Software Foundation therefore we are unfortunately unable to continue supporting it as part of the SpamAssassin project"]. So ... SaProxy could not move to apache (from sourceforge); seems that there were some legalities implications that avoided it. Perhaps somebody with perl knowledge could lead further the open source project? -in a non-apache based place-

- * SaProxy Pro is not free
+ * SaProxy '''Phoenix''' may be on its way? (Dan Wing has been able to install it with SA 3.0)
+
+ 2004-Oct-22
+
+ Have a look to http://sourceforge.net/mailarchive/forum.php?thread_id=5812011&forum_id=27500
+
+ * SaProxy Pro is not free (and is dead!)
+
+STOP PRESS ... Oct 20 2004 ... visit www.statalabs.com ...
+
+[...] Stata Labs has been acquired by Yahoo! [...]
+
+[...] Will Yahoo! sell Bloomba or SAproxy Pro? '''At this time there are no plans for Yahoo! to sell Bloomba or SAproxy Pro''' [...]

... and the maker in order to fulfill perl artistic licence must release any changes made to SaProxy into the public domain (unless the author allows otherwise ...; that means, IMHO, the creator of Pop3Proxy; and, up to my knowledge, he has not granted otherwise ...)
[SpamAssassin Wiki] Updated: SaProxyStatus [ In reply to ]
Date: 2004-10-22T11:04:59
Editor: JustinMason <jm@jmason.org>
Wiki: SpamAssassin Wiki
Page: SaProxyStatus
URL: http://wiki.apache.org/spamassassin/SaProxyStatus

commenting on the editorial aspect of this page

Change Log:

------------------------------------------------------------------------------
@@ -2,6 +2,8 @@

The following is based on Internet googling and deep searching in sourceforge, apache, and so on. So, this only represents a view on reality, and my own on my journey through it.

+ ''(JustinMason: please note that this page represents the opinions of one person, and does not represent those of the SpamAssassin development team.)''
+
= Situation =

Currently:
@@ -14,6 +16,8 @@

SaProxy "evolver and curator" said that [http://bugzilla.spamassassin.org/show_bug.cgi?id=2200 "We were unable to bring SAproxy/pop3proxy into the Apache Software Foundation therefore we are unfortunately unable to continue supporting it as part of the SpamAssassin project"]. So ... SaProxy could not move to apache (from sourceforge); seems that there were some legalities implications that avoided it. Perhaps somebody with perl knowledge could lead further the open source project? -in a non-apache based place-

+ ''(JustinMason: Dan Mc Donald preferred to keep his code licensed using 2.x's dual PAL/GPL licenses. Since we were moving SpamAssassin to the ASF, and since the Apache license was required for that, this meant we could not distribute or host Dan's code at Apache.)''
+
* SaProxy '''Phoenix''' may be on its way? (Dan Wing has been able to install it with SA 3.0)

2004-Oct-22
@@ -30,6 +34,8 @@

... and the maker in order to fulfill perl artistic licence must release any changes made to SaProxy into the public domain (unless the author allows otherwise ...; that means, IMHO, the creator of Pop3Proxy; and, up to my knowledge, he has not granted otherwise ...)

+ ''(JustinMason: I think you are misreading Perl's Artistic license. The Artistic license does not require release of all changes as the GPL does.)''
+
But ... source code modifications are ... at least ... difficult to obtain:

- Have not been able to find packaged saproxy anywhere (either Stata Lab´s web either sourceforge) Perhaps others have better luck. And ... in sourceforge cvs, there are still most components of the packaging, but the latest changes have not been commited up to my knowledge for such a long time ... so, unless requested to Stata Labs, seems that modifications to open source code are not so available ... (I have some patches stored somewhere in my pc)
@@ -121,3 +127,6 @@
...

So, I believe this has make the open source community flew away from SAProxy ...
+
+ ''(JustinMason: speaking as a member of the SA development team, I have no problem with what Stata Labs did; there are many commercial products using SpamAssassin, and our licenses have always explicitly allowed that. Please don't generalise about "the open source community" where this may mischaracterise the developers' opinions.)''
+
[SpamAssassin Wiki] Updated: SaProxyStatus [ In reply to ]
Date: 2004-10-22T14:54:26
Editor: DanielQuinlan <quinlan@pathname.com>
Wiki: SpamAssassin Wiki
Page: SaProxyStatus
URL: http://wiki.apache.org/spamassassin/SaProxyStatus

remove loads of opinion and commentary, clean up page in general

Change Log:

------------------------------------------------------------------------------
@@ -1,76 +1,50 @@
-= Caveat Emptor =
-
-The following is based on Internet googling and deep searching in sourceforge, apache, and so on. So, this only represents a view on reality, and my own on my journey through it.
-
- ''(JustinMason: please note that this page represents the opinions of one person, and does not represent those of the SpamAssassin development team.)''
-
-= Situation =
+= SAproxy Status =

Currently:

- * Pop3Proxy is "dormant":
+ * Pop3Proxy is not being actively developed at this time:

- Pop3Proxy author says he is not currently able to continue with it. Although Dan Mc Donald intention is to publish a repacked updated Pop3Proxy, he is short of time ...
+ Dan McDonald, the primary author, reports that he is not currently able to work on it due to time constraints.

- * SaProxy is ... in limbo
+ * SaProxy is in an indeterminate state at this time:

- SaProxy "evolver and curator" said that [http://bugzilla.spamassassin.org/show_bug.cgi?id=2200 "We were unable to bring SAproxy/pop3proxy into the Apache Software Foundation therefore we are unfortunately unable to continue supporting it as part of the SpamAssassin project"]. So ... SaProxy could not move to apache (from sourceforge); seems that there were some legalities implications that avoided it. Perhaps somebody with perl knowledge could lead further the open source project? -in a non-apache based place-
+ [http://bugzilla.spamassassin.org/show_bug.cgi?id=2200 bug 2200 states] that "We were unable to bring SAproxy/pop3proxy into the Apache Software Foundation therefore we are unfortunately unable to continue supporting it as part of the SpamAssassin project".

- ''(JustinMason: Dan Mc Donald preferred to keep his code licensed using 2.x's dual PAL/GPL licenses. Since we were moving SpamAssassin to the ASF, and since the Apache license was required for that, this meant we could not distribute or host Dan's code at Apache.)''
+ ''(JustinMason: Dan McDonald preferred to keep his code licensed using 2.x's dual PAL/GPL licenses. Since we were moving SpamAssassin to the ASF, and since the Apache license was required for that, this meant we could not distribute or host Dan's code at Apache.)''

- * SaProxy '''Phoenix''' may be on its way? (Dan Wing has been able to install it with SA 3.0)
+ * SAproxy '''Phoenix''' may be on its way. (Dan Wing has been able to install it with SA 3.0)

2004-Oct-22

Have a look to http://sourceforge.net/mailarchive/forum.php?thread_id=5812011&forum_id=27500

- * SaProxy Pro is not free (and is dead!)
-
-STOP PRESS ... Oct 20 2004 ... visit www.statalabs.com ...
-
-[...] Stata Labs has been acquired by Yahoo! [...]
-
-[...] Will Yahoo! sell Bloomba or SAproxy Pro? '''At this time there are no plans for Yahoo! to sell Bloomba or SAproxy Pro''' [...]
-
- ... and the maker in order to fulfill perl artistic licence must release any changes made to SaProxy into the public domain (unless the author allows otherwise ...; that means, IMHO, the creator of Pop3Proxy; and, up to my knowledge, he has not granted otherwise ...)
-
- ''(JustinMason: I think you are misreading Perl's Artistic license. The Artistic license does not require release of all changes as the GPL does.)''
+ * SAproxy Pro is commercial software and may not be moving forward.

-But ... source code modifications are ... at least ... difficult to obtain:
+ As reported on www.statalabs.com on Oct 20 2004:

-- Have not been able to find packaged saproxy anywhere (either Stata Lab´s web either sourceforge) Perhaps others have better luck. And ... in sourceforge cvs, there are still most components of the packaging, but the latest changes have not been commited up to my knowledge for such a long time ... so, unless requested to Stata Labs, seems that modifications to open source code are not so available ... (I have some patches stored somewhere in my pc)
+ "[...] Stata Labs has been acquired by Yahoo! [...]"

-Said CVS still available for old SaProxy components at sourceforge: (under Pop3 header) http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/
+ "[...] Will Yahoo! sell Bloomba or SAproxy Pro? '''At this time there are no plans for Yahoo! to sell Bloomba or SAproxy Pro [...]"

- * SaProxy and SpamAssassin at sourceforge are deep frozen. SaProxy list at sourceforge is dead ... even if it has some scarce support for SaProxy Pro (curiously a commercial product suppported in a sourceforge list ...); Bugs no longer available at Sourceforge.
+ * CVS for an earlier SAproxy (predating "Pro") remain available at SourceForge: (under "pop3") in http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/

- * SaProxy is not covered under the new apache site, but some help/advice can be sought in their lists [http://wiki.apache.org/spamassassin/MailingLists Lists]
+ * SAproxy and SpamAssassin at sourceforge are not active. The SAproxy list at SourceForge is essentially inactive as well.

- * SaProxy old bugs/problems and current situation can be reviewed at [http://bugzilla.spamassassin.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=saproxy&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs]
-
-
-= Perspectives =
-
-a) hand installation of SAProxy last version; see SaProxyHowTo
-
-b) substitution by [http://spamgrinderprox.sourceforge.net/ Spam Grinder Proxy]
-
-c) saproxy phoenix ? (that is, somebody joining the lost pieces ...)
-
-d) Dan Mc Donald recovering spare time?
+ * SAproxy is not covered under the new apache site, but some help/advice can be sought in their lists [http://wiki.apache.org/spamassassin/MailingLists Lists]

+ * SAproxy old bugs/problems and current situation can be reviewed at [http://bugzilla.spamassassin.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=saproxy&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs]

= History =

-Dan Mc Donald is the father of Pop3proxy (Perl artistic license) that evolved (fullfilling license requirements) to SaProxy. Original Pop3Proxy in http://mcd.perlmonk.org/pop3proxy/
+Dan McDonald is the father of Pop3proxy (Perl artistic license) that evolved (fullfilling license requirements) to SaProxy. Original Pop3Proxy in http://mcd.perlmonk.org/pop3proxy/

-Dan, Johan Lindstrom and DanielQuinlan (last one commisioned by Stata Lab´s) made Pop3Proxy evolve into SaProxy (as per http://article.gmane.org/gmane.mail.spam.spamassassin.general/13810/match=pop3proxy)
+Dan, Johan Lindstrom and DanielQuinlan (Daniel under commission of Stata Labs) evolved Pop3Proxy into the much-improved SAproxy (as per http://article.gmane.org/gmane.mail.spam.spamassassin.general/13810/match=pop3proxy)

-SaProxy was under SpamAssassin sourceforge project (clearly an open source project).
+SAproxy was under SpamAssassin SourceForge project as an open source project for a time.

Major and minor versions and realeases (based on http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/ )

-- pop3proxy.pl at sourceforge
+- pop3proxy.pl at SourceForge

1.0 19 Nov 2002

@@ -78,7 +52,7 @@

1.15 26 May 2003

-- SaProxy at sourceforge
+- SAproxy at SourceForge

1.0, including SA 2.44, date unknown

@@ -86,47 +60,9 @@

1.2, including SA 2.55, and pop3proxy.pl 1.15?, 6 June 2003

-There have been later patches to bugs as per ... sourceforge bugs have gone ... I believe I have them somewhere in my pc ...
-
-SaProxy wraps SA and Pop3Proxy in a win installation and GUI, no Perl installation needed!
+SAproxy wraps SpamAssassin and pop3proxy.pl in a Win32 installation and GUI, no Perl installation needed!

Some bits of history:
http://article.gmane.org/gmane.mail.spam.spamassassin.general/23054/match=pop3proxy
http://article.gmane.org/gmane.mail.spam.spamassassin.general/13810/match=pop3proxy
http://article.gmane.org/gmane.mail.spam.spamassassin.general/14020/match=pop3proxy
-
-So, sourceforge list working but dead.
-
-SpamAssassin is under the apache project (http://spamassassin.apache.org/). No SaProxy there. SaProxy could not be moved to the new apache site ( http://bugzilla.spamassassin.org/show_bug.cgi?id=1865 )
-
-Currently, SA list (not SaProxy or Pop3Proxy either) is hosted within apache: http://wiki.apache.org/spamassassin/MailingLists
-
-
-= Licence fulfillment =
-
-Those are my only thoughs/imagination
-
-SaProxy Pro from Stata Lab´s builds up from Pop3Proxy / SaProxy.
-
-As such, in order to fulfill its licence, that company must make sources available. Those were so in the early times, but in a rather obscure and difficult way for even advanced users:
-a) buried in their website, the initial version
-b) as patches to SA in sourceforge for the following version
-c) later versions, I was unable to find them ...
-
-According to contacted author, have not given permission to relieve the need to freely distribute the source code.
-
-It is not only my point of view
-http://article.gmane.org/gmane.mail.spam.spamassassin.general/42505/match=pop3proxy
-
-From my personal point of view, the makers of SAProxy PrO perhaps might be fullfilling the writings of licence requirements (?) but not its spirit ... Can check in:
-http://www.statalabs.com/support/saproxypro/WebHelp/About_Spam_Assassin.htm
-
-As they say:
-Sa Proxy Pro complies with the Perl Artistic License in the following ways:
-Following 3(a) by placing the modifications in the Public Domain
-...
-
-So, I believe this has make the open source community flew away from SAProxy ...
-
- ''(JustinMason: speaking as a member of the SA development team, I have no problem with what Stata Labs did; there are many commercial products using SpamAssassin, and our licenses have always explicitly allowed that. Please don't generalise about "the open source community" where this may mischaracterise the developers' opinions.)''
-
[SpamAssassin Wiki] Updated: SaProxyStatus [ In reply to ]
Date: 2004-10-22T14:55:22
Editor: DanielQuinlan <quinlan@pathname.com>
Wiki: SpamAssassin Wiki
Page: SaProxyStatus
URL: http://wiki.apache.org/spamassassin/SaProxyStatus

remove extra bolding

Change Log:

------------------------------------------------------------------------------
@@ -24,7 +24,7 @@

"[...] Stata Labs has been acquired by Yahoo! [...]"

- "[...] Will Yahoo! sell Bloomba or SAproxy Pro? '''At this time there are no plans for Yahoo! to sell Bloomba or SAproxy Pro [...]"
+ "[...] Will Yahoo! sell Bloomba or SAproxy Pro? At this time there are no plans for Yahoo! to sell Bloomba or SAproxy Pro [...]"

* CVS for an earlier SAproxy (predating "Pro") remain available at SourceForge: (under "pop3") in http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/
[SpamAssassin Wiki] Updated: SaProxyStatus [ In reply to ]
Date: 2004-10-26T04:31:00
Editor: CasperTone2003 <spamassassin.z.caspertone2003@spamgourmet.com>
Wiki: SpamAssassin Wiki
Page: SaProxyStatus
URL: http://wiki.apache.org/spamassassin/SaProxyStatus

no comment

Change Log:

------------------------------------------------------------------------------
@@ -40,9 +40,11 @@

Dan, Johan Lindstrom and DanielQuinlan (Daniel under commission of Stata Labs) evolved Pop3Proxy into the much-improved SAproxy (as per http://article.gmane.org/gmane.mail.spam.spamassassin.general/13810/match=pop3proxy)

-SAproxy was under SpamAssassin SourceForge project as an open source project for a time.
+SAproxy was under SpamAssassin SourceForge project as an open source project for a time (How can be an open source project be open only for a time?!).

-Major and minor versions and realeases (based on http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/ )
+SAproxy Pro is (was) a commercial derivative of SAproxy. According to some people point of view (please respect freedom of speach) the company must release the source code and has not done it (interested in details, see http://wiki.apache.org/spamassassin/SaProxyStatus?action=diff&date=1098436420)
+
+SAproxy major and minor versions and realeases (based on http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/ )

- pop3proxy.pl at SourceForge
[SpamAssassin Wiki] Updated: SaProxyStatus [ In reply to ]
Date: 2004-10-26T10:55:53
Editor: JustinMason <jm@jmason.org>
Wiki: SpamAssassin Wiki
Page: SaProxyStatus
URL: http://wiki.apache.org/spamassassin/SaProxyStatus

more corrections

Change Log:

------------------------------------------------------------------------------
@@ -42,7 +42,11 @@

SAproxy was under SpamAssassin SourceForge project as an open source project for a time (How can be an open source project be open only for a time?!).

-SAproxy Pro is (was) a commercial derivative of SAproxy. According to some people point of view (please respect freedom of speach) the company must release the source code and has not done it (interested in details, see http://wiki.apache.org/spamassassin/SaProxyStatus?action=diff&date=1098436420)
+ (JustinMason: SAproxy is still there -- [http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/ sourceforge.net CVS].)
+
+SAproxy Pro is (was) a commercial derivative of SAproxy. According to some people point of view (please respect freedom of speach) the company must release the source code and has not done it (interested in details, see http://wiki.apache.org/spamassassin/SaProxyStatus?action=diff&date=1098436420)
+
+ (JustinMason: that would be the case if it was released under GPL. It is not. The Perl Artistic License != GPL.)

SAproxy major and minor versions and realeases (based on http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/ )
[SpamAssassin Wiki] Updated: SaProxyStatus [ In reply to ]
Date: 2004-10-26T11:11:31
Editor: JustinMason <jm@jmason.org>
Wiki: SpamAssassin Wiki
Page: SaProxyStatus
URL: http://wiki.apache.org/spamassassin/SaProxyStatus

yeesh, more comments

Change Log:

------------------------------------------------------------------------------
@@ -1,5 +1,7 @@
= SAproxy Status =

+''(Note: this page contains some statements that are under discussion. Editors: please sign any statements that may be under discussion. This is the wiki convention, and indicates to readers that it's not necessarily the consensus view.)''
+
Currently:

* Pop3Proxy is not being actively developed at this time:
@@ -10,13 +12,13 @@

[http://bugzilla.spamassassin.org/show_bug.cgi?id=2200 bug 2200 states] that "We were unable to bring SAproxy/pop3proxy into the Apache Software Foundation therefore we are unfortunately unable to continue supporting it as part of the SpamAssassin project".

- ''(JustinMason: Dan McDonald preferred to keep his code licensed using 2.x's dual PAL/GPL licenses. Since we were moving SpamAssassin to the ASF, and since the Apache license was required for that, this meant we could not distribute or host Dan's code at Apache.)''
+ JustinMason: Dan McDonald preferred to keep his code licensed using 2.x's dual PAL/GPL licenses. Since we were moving SpamAssassin to the ASF, and since the Apache license was required for that, this meant we could not distribute or host Dan's code at Apache.

- * SAproxy '''Phoenix''' may be on its way. (Dan Wing has been able to install it with SA 3.0)
+ Please note that someone ''could'' maintain, support, and further develop the open source SaProxy -- it's just that we in the SA development team are not likely to do so, given that it's not part of the Apache SpamAssassin project as a result of this.

- 2004-Oct-22
+ * SAproxy '''Phoenix''' may be on its way.

- Have a look to http://sourceforge.net/mailarchive/forum.php?thread_id=5812011&forum_id=27500
+ Dan Wing has been able to install it with SA 3.0 (2004-Oct-22) -- have a look [http://sourceforge.net/mailarchive/forum.php?thread_id=5812011&forum_id=27500 here].

* SAproxy Pro is commercial software and may not be moving forward.

@@ -30,9 +32,11 @@

* SAproxy and SpamAssassin at sourceforge are not active. The SAproxy list at SourceForge is essentially inactive as well.

- * SAproxy is not covered under the new apache site, but some help/advice can be sought in their lists [http://wiki.apache.org/spamassassin/MailingLists Lists]
+ JustinMason: SpamAssassin is indeed inactive at sourceforge, since we have moved the project to the ASF; the sf.net resources for that project are left there for historical purposes only.
+
+ * SAproxy is not covered under the new Apache site, but some help/advice can be sought in their lists [http://wiki.apache.org/spamassassin/MailingLists Lists].

- * SAproxy old bugs/problems and current situation can be reviewed at [http://bugzilla.spamassassin.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=saproxy&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs]
+ * SAproxy old bugs/problems and current situation can be reviewed at [http://bugzilla.spamassassin.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=saproxy&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs].

= History =

@@ -42,11 +46,11 @@

SAproxy was under SpamAssassin SourceForge project as an open source project for a time (How can be an open source project be open only for a time?!).

- (JustinMason: SAproxy is still there -- [http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/ sourceforge.net CVS].)
+ JustinMason: SAproxy is still there as can be seen in [http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/ sourceforge.net CVS]. It's not 'open only for a time' -- that code is still open, but now unmaintained. If someone was to maintain it, they could release new open source releases, no problem.

SAproxy Pro is (was) a commercial derivative of SAproxy. According to some people point of view (please respect freedom of speach) the company must release the source code and has not done it (interested in details, see http://wiki.apache.org/spamassassin/SaProxyStatus?action=diff&date=1098436420)

- (JustinMason: that would be the case if it was released under GPL. It is not. The Perl Artistic License != GPL.)
+ JustinMason: that would be the case if it was released under GPL alone. It is not. The license was dual Perl Artistic License and GPL. PAL != GPL.

SAproxy major and minor versions and realeases (based on http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/ )

@@ -72,3 +76,4 @@
http://article.gmane.org/gmane.mail.spam.spamassassin.general/23054/match=pop3proxy
http://article.gmane.org/gmane.mail.spam.spamassassin.general/13810/match=pop3proxy
http://article.gmane.org/gmane.mail.spam.spamassassin.general/14020/match=pop3proxy
+
[SpamAssassin Wiki] Updated: SaProxyStatus [ In reply to ]
Date: 2004-10-26T14:39:07
Editor: DanielQuinlan <quinlan@pathname.com>
Wiki: SpamAssassin Wiki
Page: SaProxyStatus
URL: http://wiki.apache.org/spamassassin/SaProxyStatus

consolidate comments, CasperTone2003: to discuss, please use dev list instead

Change Log:

------------------------------------------------------------------------------
@@ -8,13 +8,11 @@

Dan McDonald, the primary author, reports that he is not currently able to work on it due to time constraints.

- * SaProxy is in an indeterminate state at this time:
+ * SAproxy is in an indeterminate state at this time:

- [http://bugzilla.spamassassin.org/show_bug.cgi?id=2200 bug 2200 states] that "We were unable to bring SAproxy/pop3proxy into the Apache Software Foundation therefore we are unfortunately unable to continue supporting it as part of the SpamAssassin project".
+ [http://bugzilla.spamassassin.org/show_bug.cgi?id=2200 bug 2200 states] that "We were unable to bring SAproxy/pop3proxy into the Apache Software Foundation therefore we are unfortunately unable to continue supporting it as part of the SpamAssassin project". Dan McDonald preferred to keep his code licensed using the dual PAL/GPL license of SpamAssassin 2.x and SAproxy. Since the SpamAssassin project was moving to the ASF, and because the Apache license was required for that, this meant the SpamAssassin project could not distribute or host Dan McDonald's code at Apache.

- JustinMason: Dan McDonald preferred to keep his code licensed using 2.x's dual PAL/GPL licenses. Since we were moving SpamAssassin to the ASF, and since the Apache license was required for that, this meant we could not distribute or host Dan's code at Apache.
-
- Please note that someone ''could'' maintain, support, and further develop the open source SaProxy -- it's just that we in the SA development team are not likely to do so, given that it's not part of the Apache SpamAssassin project as a result of this.
+ Please note that someone ''could'' maintain, support, and further develop the open source SaProxy -- it's just that the SA development team is not likely to do so, given that it's not part of the Apache SpamAssassin project as a result of the inability to change the license.

* SAproxy '''Phoenix''' may be on its way.

@@ -30,9 +28,7 @@

* CVS for an earlier SAproxy (predating "Pro") remain available at SourceForge: (under "pop3") in http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/

- * SAproxy and SpamAssassin at sourceforge are not active. The SAproxy list at SourceForge is essentially inactive as well.
-
- JustinMason: SpamAssassin is indeed inactive at sourceforge, since we have moved the project to the ASF; the sf.net resources for that project are left there for historical purposes only.
+ * SAproxy and SpamAssassin at sourceforge are inactive because nobody is developing them now. The SAproxy list at SourceForge is essentially inactive as well. The sf.net resources for that project are left there for historical purposes only.

* SAproxy is not covered under the new Apache site, but some help/advice can be sought in their lists [http://wiki.apache.org/spamassassin/MailingLists Lists].

@@ -44,13 +40,9 @@

Dan, Johan Lindstrom and DanielQuinlan (Daniel under commission of Stata Labs) evolved Pop3Proxy into the much-improved SAproxy (as per http://article.gmane.org/gmane.mail.spam.spamassassin.general/13810/match=pop3proxy)

-SAproxy was under SpamAssassin SourceForge project as an open source project for a time (How can be an open source project be open only for a time?!).
-
- JustinMason: SAproxy is still there as can be seen in [http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/ sourceforge.net CVS]. It's not 'open only for a time' -- that code is still open, but now unmaintained. If someone was to maintain it, they could release new open source releases, no problem.
-
-SAproxy Pro is (was) a commercial derivative of SAproxy. According to some people point of view (please respect freedom of speach) the company must release the source code and has not done it (interested in details, see http://wiki.apache.org/spamassassin/SaProxyStatus?action=diff&date=1098436420)
+SAproxy was under SpamAssassin SourceForge project as an open source project and maintained there for a time, but is now unmaintained. SAproxy can be seen in [http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/ sourceforge.net CVS]. If someone were to take over maintainance, they could release new open source releases at SourceForge or elsewhere.

- JustinMason: that would be the case if it was released under GPL alone. It is not. The license was dual Perl Artistic License and GPL. PAL != GPL.
+SAproxy Pro is (was) a commercial derivative of SAproxy released under the Perl Artistic License.

SAproxy major and minor versions and realeases (based on http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/ )
[SpamAssassin Wiki] Updated: SaProxyStatus [ In reply to ]
Date: 2004-10-27T09:59:01
Editor: DavidForrest <drf5n+spamassassin@freeshell.org>
Wiki: SpamAssassin Wiki
Page: SaProxyStatus
URL: http://wiki.apache.org/spamassassin/SaProxyStatus

no comment

Change Log:

------------------------------------------------------------------------------
@@ -68,4 +68,5 @@
http://article.gmane.org/gmane.mail.spam.spamassassin.general/23054/match=pop3proxy
http://article.gmane.org/gmane.mail.spam.spamassassin.general/13810/match=pop3proxy
http://article.gmane.org/gmane.mail.spam.spamassassin.general/14020/match=pop3proxy
-
+----
+CategoryDevelopment