Hi Daniel,
thanks for your reply.
Comments follow.
Daniel Quinlan <[EMAIL PROTECTED]> wrote:
Daniel Quinlan <[EMAIL PROTECTED]> wrote:
>> 1.- Is there interest for a tool such as SAProxy?
> Yes.
>> I will start highligthing that SAProxy is the only real way to use
>> SpamAssassin in a Windows end user environment where there is not MTA
>> SpamAssassin support.
> That is not really true. There are other Windows front-ends:
> http://wiki.apache.org/spamassassin/CommercialWindows
You are certainly right. Let me reword: SAProxy is the only "open source" real way to use SA in a windows end user environment...
>> It is a pain in the * not having any developer interested in SAProxy
>> and furthering its development (under whichever licence it could
>> be). Saddly, I am not perl literate. Blood, sweet and tears was what
>> it took me to make saproxy 1.2 from the sourceforge CVS to work with
>> SA 2.64. Now I am frightened to try with SA 3+
>I agree, but complaining on the Wiki is not going to fix that.
Well, yes and no. I am not just complaining in the Wiki, I am trying to put together enough info on the wiki to pave the way for a rebirth of Pop3proxy. Should I know perl, I would do it by myself. I am not trying to bring havoc to the wiki, but the first step is that people know about SAProxy. I noted that the situation tended to forget about it (I am not implying intentional obliviance ... but it happened). And lack of precission to distinguish Pop3proxy, SAProxy (CVS and packaged) and SAProxy pro. I believe it essential to be publicised that SAProxy is a free product by contrast to the pro one.
>> You can see the PAL here
>>
>> http://www.opensource.org/licenses/artistic-license.php
>>
>> so, IMHO, Stata Labs must provide the source code. I cannot understand
>> why do you believe that under PAL they should not have to provide the
>> source code. And, last version SAProxy Pro has not been commited to
>> sourceforge CVS. And I have asked them for the code and have not reply
>> (yet).
>Perhaps, but that's up to the authors: Dan McDonald, Johan, and myself.
Yes, thanks, I beg Johan�s pardon as I always forget his name.
>I believe only the authors have standing to enforce the license. I've
asked Stata Labs to ask Yahoo! if the software can be released and I'm
going to wait a short while for an answer before proceeding.
As how I understand it, the authors can relieve StataLabs from its obligation.I know Dan was (have no current information) interest in going that way. I do not know what could happen if one coauthor would say no and two say yes ...
But ... I would not be able to legally "enforce" the licence, but I am in my right to ask for the source code. The modifier has the obligation to put it into the public domain ...
Thanks for contacting StataLabs/Yahoo, certainly you have more chances to get a positive answer. It certainly merits to wait and see. Meanwhile we can let the wiki page as it is, eventhough I believe that a mention that the source code should be put into the public domain by StataLabs is not untrue.
By the way, I think you should also review and align the SaProxy wiki page to be in line with SaProxyStatus (by the way, the paragraph starting with "What happened to the free version" was already in the wiki before my changes ...
Again,
thanks for your interest
CTone
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
