[Fwd: Re: SquirrelSAP 1.0.3 for Squirrel Mail is Ready!]

[p dont think <pd...@angrynerds.com>]

Ron,

   You are sending from a non-deliverable address.  I assumed since your 
message went to me offlist that you wanted to move this thread off the 
list, however, my mail just gets returned (see attached bounce).

  -Paul

-------- Original Message --------
Subject: Re: SquirrelSAP 1.0.3 for Squirrel Mail is Ready!
Date: Tue, 08 Mar 2005 11:59:29 -0800
From: Paul Lesneiwski <pa...@squirrelmail.org>
Organization: Open Guild, LLC
To: Codger <li...@pmbx.net>,  perlstalker@falconsroost.alamosa.co.us
References: <52...@pmbx.net> 
<42...@angrynerds.com> 
<47...@pmbx.net>



Codger wrote:
> There are two important things that are different. Mine is compatible 
> with version 5 of php

What in the other plugin is not?

> and does not rely on register_globals to be on. 

Sasql has had some major hurdles to get past that requirement, as well
as all the PHP Notices it spewed out, but my understanding is that those
issues have long since been resolved.

> Second, it is designed to work with Spamassassin 3.0.2 where some basic 
> configurations are different than previous versions. For example, in pre 
> 3.x.x versions, the spam score marking threshold is defined as 
> 'required_hits' and in 3.x.x it is 'required_score'. My pages allow you 
> to work with the older version of spamassassin also by simply choosing 
> which you're using in the config location.

If sasql doesn't support that simple switch, it could very easily.  You
should submit a patch to Randy for that change.

> This project was originally one that had existed on the php-sa-sql 
> project page (Rick McDougal is the project leader, www.limelyte.com). 

I've never heard of that, and wish someone there had coordinated with us
a long time ago.  :)

> That code required only a few pages and was much more well thought out 
> and though it was stale by one to two years, was more amenable to the 
> rewrite. It is also open source. Rick has asked me to take over the 
> development of that part of the SourceForge project (he's working on the 
> standalone part of the project) as a result of my interest.

Still, there is no reason the current sasql plugin can't be cleaned
where needed and ported to that project if that is the desire.  From
what I can tell sasql is slightly more feature-rich.  And with two
interested parties working together on it, it can become that much better!

> Because I use the code in my secure email services company 
> (https://www.pmbx.net) the features that I put in were ones that I knew 
> were most easily understood and requested by users. There are other 
> features that can be added, but the average person is going to lost 
> otherwise. But the feature set is not fixed and I am interested in input 
> and feature requests to improve the pages always.

I agree about limiting the configuration items, since most users won't
hardly use those anyway.  However, sasql allows the admin to make the
ultimate choice thru simple configuration (although I haven't done so
myself), which means the plugin author doesn't have to respond to all
sorts of random requests to add this and that config item...

> One of the things that would very much interest me is a way for 
> hostmasters like myself to add code into the pages that I developed 
> which would allow them to accommodate server specific code. For example, 
> I use CommuniGate Pro and our Settings page for each user also offers 
> them the ability to have email automatically deleted at a certain level. 
> It would be way cool to have that incorporated into SquirrelSAP. But 
> likely any such code would be very specific to the type of mail server 
> you run. I don't think any consideration for that is presently in any 
> similar php pages.

That example would be code that I would never put into a PHP front-end
for something that the spam scanner or SMTP server should be responsible
for.  However, if I understand you, you are just musing about how nice
it'd be to add new config types to the plugin, which possibly do more
than change a SA setting.  I don't see why that couldn't be added to
either plugin.

> As far as the plugin architecture itself, I'm new to developing plugins 
> for SquirrelMail, but am interested in following all the specifications.

Please have a look at the links I sent you separately.

One other thing I should mention is that sasql also places links to
report spam to sa-learn in the user interface.  However, I am was
planning to request that Randy add a configuration item to turn those
off, since I am using a plugin that does the same thing a little more
comprehensively (completely configurable, not necessarily tied to SA).
That plugin is attached and might be released soon.  Randy?

   - Paul




> On Mar 8, 2005, at 2:22 PM, p dont think wrote:
> 
>> Can you please explain how your plugin differs from this one:
>>
>> http://www.squirrelmail.org/plugin_view.php?id=167
>>
>> It looks like yours is somewhat non-standard (per SquirrelMail plugin 
>> specifications) and does not offer the flexibility to add as many 
>> custom user configurable options as you like.
>>
>> It'd be great to see you combine efforts with Randy to make that 
>> plugin more solid (it's had its problems to date, but is generally a 
>> good plugin).
>>
>>  - Paul
> 
> 
> Ron
> 

Re: [Fwd: Re: SquirrelSAP 1.0.3 for Squirrel Mail is Ready!]

[Rick Macdougall <ri...@nougen.com>]

p dont think wrote:
> Ron,
> 
>   You are sending from a non-deliverable address.  I assumed since your 
> message went to me offlist that you wanted to move this thread off the 
> list, however, my mail just gets returned (see attached bounce).
> 
>  -Paul
> 
>> This project was originally one that had existed on the php-sa-sql 
>> project page (Rick McDougal is the project leader, www.limelyte.com). 
> 
> 
> I've never heard of that, and wish someone there had coordinated with us
> a long time ago.  :)

Hi,

Originally (and actually still to this day) it was meant as a stand 
alone interface to SQL SA user preferences.  I modified it to allow it 
to become a plugin to Squirrel at the request of a client who wanted 
both interfaces to look the same.

If Paul and/or Randy want to use the SourceForge site I've created to 
merge the two codebases together, I'm more than willing if Ron is.

Regards,

Rick