You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by sp...@incubator.apache.org on 2004/09/07 16:03:13 UTC

[SpamAssassin Wiki] New: SaProxyStatus

   Date: 2004-09-07T07:03:13
   Editor: CasperTone2003 <sp...@spamgourmet.com>
   Wiki: SpamAssassin Wiki
   Page: SaProxyStatus
   URL: http://wiki.apache.org/spamassassin/SaProxyStatus

   no comment

New Page:

= 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.

= Situation =

Currently:

 * Pop3Proxy is "dormant":

   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 ...

 * SaProxy is ... in limbo

   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

   ... 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 ...)

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)

Said CVS still available for old SaProxy components at sourceforge: (under Pop3 header) http://cvs.sourceforge.net/viewcvs.py/spamassassin/pop3/

 * 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.

 * 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]


= 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?


= 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, 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)

SaProxy was under SpamAssassin sourceforge project (clearly an open source project).

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

- pop3proxy.pl at sourceforge

1.0 19 Nov 2002

1.2 23 Nov 2002 (included GUI by Johan)

1.15 26 May 2003

- SaProxy at sourceforge

1.0, including SA 2.44, date unknown

1.1, including SA 2.52, and pop3proxy.pl 1.15, 26 May 2003

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!

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 ...