squirrelmail-plugins — SquirrelMail Plugins Mailing List

Re: [SM-PLUGINS] php-5.4.10-1 / avelsieve

[Brendan P. <br...@db...>]

Excellent!  I can confirm that this patch fixed my debian installation also.

Well done.


On 05/01/13 09:14, Scott Ruckh wrote:
> Yo.   This is what you said earlier: Paul Lesniewski
>>>> Peter
>>> It looks like I spoke too soon.
>>>
>>> Although the existing policies were displayed when clicking on the
>>> "Filters" link, when attempting to create a new policy the following
>>> error
>>> is thrown:
>>>
>>> Fatal error: Call-time pass-by-reference has been removed in
>>> /usr/local/squirrelmail/www/plugins/avelsieve/include/avelsieve_condition_datetime.class.php
>>> on line 56
>>>
>>> This same error is also thrown if you attempt to add a rule directly
>>> from
>>> an email and clicking on one of the filter links.
>> There is a newer version of the Server Settings Backend plugin (not
>> yet publicly released, but available for the asking) that provides the
>> ability to connect to a socket backend such as a Sieve server, and
>> thus it can be used with the newest Server Side Filters plugin code.
>> That may be a more actively maintained route you can take(?).
>>
>> --
>> Paul Lesniewski
>> SquirrelMail Team
>> Please support Open Source Software by donating to SquirrelMail!
>> http://squirrelmail.org/donate_paul_lesniewski.php
> It looks like the following "hack" might have resolved this issue...
>
> In the file
> squirrelmail/www/plugins/avelsieve/include/avelsieve_condition_datetime.class.php:
>
> Change line 56 from this
> parent::__construct(&$s, $rule, $n);
>
> to this
> parent::__construct($s, $rule, $n);
>
> ------------------------------------------------------------------------------
> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
> much more. Get web development skills now with LearnDevNow -
> 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122812
> -----
> squirrelmail-plugins mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squ...@li...
> List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
> List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

[SM-PLUGINS] Squirrel Mail support for Blackberry Enterprise Server Platform

[sandipsarang2010 <san...@gm...>]

Hi TeamAs all of us are aware that Blackberry Enterprise Server support below
mail platform :1] Microsoft Exchange Domain.2] IBM Lotus Domino Domain.3]
Novell Groupwise Domain.4] Google Apps Domain.5] Zimbra Domain.Is it
possible to configure squirrel mail user account on Blackberry Enterprise
Server. Is your technical team working to make it work out in near
future.Kindly revert back to us.ThanksSandip



--
View this message in context: http://squirrelmail.5843.n7.nabble.com/Squirrel-Mail-support-for-Blackberry-Enterprise-Server-Platform-tp25209.html
Sent from the squirrelmail-plugins mailing list archive at Nabble.com.

Re: [SM-PLUGINS] php-5.4.10-1 / avelsieve

[Scott R. <sr...@ge...>]

Yo.   This is what you said earlier: Paul Lesniewski
>>> Peter
>>
>> It looks like I spoke too soon.
>>
>> Although the existing policies were displayed when clicking on the
>> "Filters" link, when attempting to create a new policy the following
>> error
>> is thrown:
>>
>> Fatal error: Call-time pass-by-reference has been removed in
>> /usr/local/squirrelmail/www/plugins/avelsieve/include/avelsieve_condition_datetime.class.php
>> on line 56
>>
>> This same error is also thrown if you attempt to add a rule directly
>> from
>> an email and clicking on one of the filter links.
>
> There is a newer version of the Server Settings Backend plugin (not
> yet publicly released, but available for the asking) that provides the
> ability to connect to a socket backend such as a Sieve server, and
> thus it can be used with the newest Server Side Filters plugin code.
> That may be a more actively maintained route you can take(?).
>
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php

It looks like the following "hack" might have resolved this issue...

In the file
squirrelmail/www/plugins/avelsieve/include/avelsieve_condition_datetime.class.php:

Change line 56 from this
parent::__construct(&$s, $rule, $n);

to this
parent::__construct($s, $rule, $n);

Re: [SM-PLUGINS] php-5.4.10-1 / avelsieve

[Paul L. <pa...@sq...>]

On Thu, Jan 3, 2013 at 9:59 AM, Scott Ruckh <sr...@ge...> wrote:
>
> Yo.   This is what you said earlier: Peter Senft
>> Hi,
>>
>> I had the same issue and created a patch for avelsieve to run on PHP
>> 5.3. and higher:
>>
>> http://www.rfc3092.net/projects/avelsieve/
>>
>> That should take care of the warnings for split() and other deprecated
>> functions. Not sure if that also fixes the other problem. Maybe give it
>> a shot and let me know.
>>
>> FYI, that is just a patch and not the official version or a branch.
>> AFAIK that patch was incorporated into the official version but so far
>> there no new version including the patch was released.
>>
>> Peter
>
> It looks like I spoke too soon.
>
> Although the existing policies were displayed when clicking on the
> "Filters" link, when attempting to create a new policy the following error
> is thrown:
>
> Fatal error: Call-time pass-by-reference has been removed in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/avelsieve_condition_datetime.class.php
> on line 56
>
> This same error is also thrown if you attempt to add a rule directly from
> an email and clicking on one of the filter links.

There is a newer version of the Server Settings Backend plugin (not
yet publicly released, but available for the asking) that provides the
ability to connect to a socket backend such as a Sieve server, and
thus it can be used with the newest Server Side Filters plugin code.
That may be a more actively maintained route you can take(?).

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-PLUGINS] php-5.4.10-1 / avelsieve

[Peter S. <du...@gm...>]

Scott,

I guess I have to take look at my patch then. A problem might be that I
don't have PHP 5.4 installed yet. So, I hope I can reproduce the error
on 5.3.

Peter

On 01/03/2013 12:59 PM, Scott Ruckh wrote:
> 
> Yo.   This is what you said earlier: Peter Senft
>> Hi,
>>
>> I had the same issue and created a patch for avelsieve to run on PHP
>> 5.3. and higher:
>>
>> http://www.rfc3092.net/projects/avelsieve/
>>
>> That should take care of the warnings for split() and other deprecated
>> functions. Not sure if that also fixes the other problem. Maybe give it
>> a shot and let me know.
>>
>> FYI, that is just a patch and not the official version or a branch.
>> AFAIK that patch was incorporated into the official version but so far
>> there no new version including the patch was released.
>>
>> Peter
> 
> It looks like I spoke too soon.
> 
> Although the existing policies were displayed when clicking on the
> "Filters" link, when attempting to create a new policy the following error
> is thrown:
> 
> Fatal error: Call-time pass-by-reference has been removed in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/avelsieve_condition_datetime.class.php
> on line 56
> 
> This same error is also thrown if you attempt to add a rule directly from
> an email and clicking on one of the filter links.
> 
> Thank You.
> 
> Scott
> 
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122712
> -----
> squirrelmail-plugins mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squ...@li...
> List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
> List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins
> 

-- 
/"\                        | Peter Senft
\ / ASCII ribbon campaign  | E-Mail : pe...@du...
 X  against HTML mail      | Jabber : du...@ja...
/ \                        | ICQ    : 62090394

Re: [SM-PLUGINS] php-5.4.10-1 / avelsieve

[Peter S. <du...@gm...>]

Hi,

that sounds odd. Which version of PHP do you use?

Peter

On 12/30/2012 11:57 PM, Brendan Pike wrote:
> I've tried installing the patched version but having trouble, I get a 
> blank page when trying to add a rule.
> 
> If anyone else if using dovecot could they please send me their 
> config.php file for comparison.
> 
> Thanks
> Brendan
> 
> 
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> -----
> squirrelmail-plugins mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squ...@li...
> List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
> List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins
> 

-- 
/"\                        | Peter Senft
\ / ASCII ribbon campaign  | E-Mail : du...@gm...
 X  against HTML mail      | Jabber : du...@ja...
/ \                        | ICQ    : 62090394

Re: [SM-PLUGINS] php-5.4.10-1 / avelsieve

[Scott R. <sr...@ge...>]

Yo.   This is what you said earlier: Peter Senft
> Hi,
>
> I had the same issue and created a patch for avelsieve to run on PHP
> 5.3. and higher:
>
> http://www.rfc3092.net/projects/avelsieve/
>
> That should take care of the warnings for split() and other deprecated
> functions. Not sure if that also fixes the other problem. Maybe give it
> a shot and let me know.
>
> FYI, that is just a patch and not the official version or a branch.
> AFAIK that patch was incorporated into the official version but so far
> there no new version including the patch was released.
>
> Peter

It looks like I spoke too soon.

Although the existing policies were displayed when clicking on the
"Filters" link, when attempting to create a new policy the following error
is thrown:

Fatal error: Call-time pass-by-reference has been removed in
/usr/local/squirrelmail/www/plugins/avelsieve/include/avelsieve_condition_datetime.class.php
on line 56

This same error is also thrown if you attempt to add a rule directly from
an email and clicking on one of the filter links.

Thank You.

Scott

Re: [SM-PLUGINS] php-5.4.10-1 / avelsieve

[Scott R. <sr...@ge...>]

Yo.   This is what you said earlier: Peter Senft
> Hi,
>
> I had the same issue and created a patch for avelsieve to run on PHP
> 5.3. and higher:
>
> http://www.rfc3092.net/projects/avelsieve/
>
> That should take care of the warnings for split() and other deprecated
> functions. Not sure if that also fixes the other problem. Maybe give it
> a shot and let me know.
>
> FYI, that is just a patch and not the official version or a branch.
> AFAIK that patch was incorporated into the official version but so far
> there no new version including the patch was released.
>
> Peter

It looks like I spoke too soon.

Although the existing policies were displayed when clicking on the
"Filters" link, when attempting to create a new policy the following error
is thrown:

Fatal error: Call-time pass-by-reference has been removed in
/usr/local/squirrelmail/www/plugins/avelsieve/include/avelsieve_condition_datetime.class.php
on line 56

This same error is also thrown if you attempt to add a rule directly from
an email and clicking on one of the filter links.

Thank You.

Scott

Re: [SM-PLUGINS] SpamAssassin plugin overwrites values on submit

[Paul L. <pa...@sq...>]

>> >> >> > I?ve been researching this problem to no avail for sometime.  We
>> >> >> > use the (very old) SpamAssassin plugin
>> >> >> > (http://squirrelmail.org/plugin_view.php?id=146) with our
>> > Squirrelmail.
>> >> >> > This plugin serves us well in terms of ease of use and we can
>> >> >> > connect it easily to our mail server spamassassin.  The only
>> >> >> > issue that any time a
>> >> > user
>> >> >> > makes a change (like adding an email to the
>> >> >> > blacklist/whitelist), all
>> >> > prior
>> >> >> > changes are overwritten.  In the README, there is a note that
>> >> >> > this was a
>> >> >> bug
>> >> >> > but resolved.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > Does anyone have any exp with this plugin and resolved this issue?
>> >> >> > Or
>> >> > is
>> >> >> > there an older thread regarding this plugin/issue that someone
>> >> >> > could
>> >> > point
>> >> >> > me to?  Thanks for any help you guys can offer.
>> >> >>
>> >> >> Please think about migrating to the Server Settings plugin, which
>> >> >> is actively maintained and should be able to do anything that the
>> >> >> various outdated SpamAssassin front end plugins can do.  There are
>> >> >> plenty of examples in the sample configuration files it comes with.
>> >> >> If you find something that it cannot replicate, let me know.
>> >> >
>> >> > Thanks for the reply, I just received the digest.  I changed my
>> >> > options so I can get a more immediate reply.  I downloaded Server
>> >> > Settings, a bit confused by the configuration examples but I chose
>> >> > one
>> > that
>> >> seemed to fit.
>> >> > When I check the SA configuration validation, it says everything is
>> > working.
>> >> > In the Options, there are various selections related to the plugin
>> >> > but choosing any of them generates this fatal error:
>> >> >
>> >> > Fatal error: Call to undefined function retrieve_server_setting()
>> >> > in
>> >> >
>> >>
>> /var/www/webmail.neoterichovercraft.com/plugins/server_settings/optio
>> >> n
>> >> > s.php
>> >> > on line 281
>> >> >
>> >> > Is there a step that I've missed?  I get it regardless of which
>> >> > configuration example I try to implement, but my initial thought is
>> >> > that the config_example_file_using_php.php or
>> >> > config_example_ftp.php matches our environment more closely.
>> >>
>> >> You probably didn't install the Server Settings Backend plugin.
>> >> Should be referenced in the docs I think.
>> >
>> > That did help, I will need to learn some more about how this works.
>> > Do you know off the top of your head if there is an additional plugin
>> > or configuration that allows one-click white/blacklist from with an
> email?
>>
>> There was a blacklist feature in a couple different plugins, but whether
> or not
>> you can use that depends on where the blacklist is kept on your server.
>> That's why the Server Settings Backend can be helpful
>> - it abstracts the backend from the user interface - the blacklist can be
>> anywhere you need it to be.
>>
>> > From what I'm reading I think I can setup other spam configuration
>> > options within the server setting plugin and I will mess around with
>> > that, but I think the most desired function was the ability to easily
>> > white/blacklist a sender or domain directly from an email.
>>
>> I don't recall if I included examples of how to put "blacklist" or
> "whitelist"
>> links on the read message screen that use the Server Settings (Backend)
>> infrastructure, but it can probably be done without too much trouble.
>> HOWEVER, this is the last thing you should be looking to implement.  What
>> would you blacklist - the "From" address?
>> That address is the first thing spammers spoof.  In general, exposing
> blacklists
>> to users is misleading and unproductive.  Whitelists, yes, perhaps, but
> you
>> really should focus on implementing a high quality anti-spam system for
> your
>> users.
>
> Thanks for the reply.  We already have a SpamAssassin system on the mail
> server.  However, the president of the company still gets spam that he says
> is consistently from the same organization/individual or contains words such
> as "male enlargement", etc.

Two thoughts:

1) Maybe your SA configuration or MTA configuration needs to be
reviewed.  Maybe you need to add another anti-spam layer

2) Have you actually verified the president's claim?  Just the fact
that he continues to receive this spam from the same place after
having been using the blacklist feature shows that it does not work
for this purpose.

> So he requests the ability to blacklist, which

It's your job to educate him as to why this is an ineffective,
inefficient and inadvisable tactic.

> is a feature that exists in SpamAssassin so I'm not sure why we would not
> want to use it.

Because you are using it for the wrong reasons.

> Regardless, he pays the bills so I will try to accommodate
> him.  I hope you can understand this.

I'd hope he's paying you to be smart and do a good job.

> The former plugin I mentioned was
> setup perfectly to allow fine tune control over the SpamAssassin
> configuration (black/whitelist, threshold, rules, etc).   Of course that
> plugin has a major bug, so all we need is some basic front end functionality
> in the K.I.S.S. mentality.  The former plugin could blacklist both domain
> and sender, but we might want to whitelist as well (supported by the
> plugin).
>
> So is it possible to modify the front end to allow the black/white list
> functionality from within the message?  I've come to understand how the
> options page works and I believe I can set that up to duplicate the main
> SpamAssassin config we need, but he would get confused trying to find the
> option page and really wants the feature directly in the reading view.

If that's not supported with some configuration changes (IRIC it
isn't), it would be easy to create another plugin or an extension to
Server Settings that uses Server Settings Backend to do what you want.
 I might try to look at a Server Settings adaptation for this, but my
time to do unpaid work is a bit limited at the moment, so it might
take me a week or more.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-PLUGINS] php-5.4.10-1 / custom_from

[Paul L. <pa...@sq...>]

On Wed, Jan 2, 2013 at 7:48 AM, Scott Ruckh <sr...@ge...> wrote:
>>
>> Make sure the user preference setting for it is enabled.
>>
>> --
>> Paul Lesniewski
>> SquirrelMail Team
>> Please support Open Source Software by donating to SquirrelMail!
>> http://squirrelmail.org/donate_paul_lesniewski.php
>>
>
> Thank you for the suggestion.
>
> Allow Arbitrary From Addresses: is "checked" for the user who is testing
> custom_from feature.  Configuration item was unchecked, and rechecked to
> see if it would make any difference.  Making this change did not resolve
> the issue.

Try reverting your PHP version to confirm that PHP is not the problem,
although, again, it should be triggering errors if this is the case.
This issue seems to be specific to your environment, as no one else
has reported such problems, so you might have to do some debugging in
the code itself.  Do you know PHP?

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-PLUGINS] php-5.4.10-1 / custom_from

[Scott R. <sr...@ge...>]

>
> Make sure the user preference setting for it is enabled.
>
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php
>

Thank you for the suggestion.

Allow Arbitrary From Addresses: is "checked" for the user who is testing
custom_from feature.  Configuration item was unchecked, and rechecked to
see if it would make any difference.  Making this change did not resolve
the issue.

-Scott

Re: [SM-PLUGINS] SpamAssassin plugin overwrites values on submit

[Ryan D. <dt...@da...>]

> -----Original Message-----
> From: pdo...@gm... [mailto:pdo...@gm...] On Behalf Of
> Paul Lesniewski
> Sent: Friday, December 28, 2012 8:01 PM
> To: Ryan Dagey
> Cc: Squirrelmail Plugins Mailing List
> Subject: Re: [SM-PLUGINS] SpamAssassin plugin overwrites values on submit
> 
> >> >> > I?ve been researching this problem to no avail for sometime.  We
> >> >> > use the (very old) SpamAssassin plugin
> >> >> > (http://squirrelmail.org/plugin_view.php?id=146) with our
> > Squirrelmail.
> >> >> > This plugin serves us well in terms of ease of use and we can
> >> >> > connect it easily to our mail server spamassassin.  The only
> >> >> > issue that any time a
> >> > user
> >> >> > makes a change (like adding an email to the
> >> >> > blacklist/whitelist), all
> >> > prior
> >> >> > changes are overwritten.  In the README, there is a note that
> >> >> > this was a
> >> >> bug
> >> >> > but resolved.
> >> >> >
> >> >> >
> >> >> >
> >> >> > Does anyone have any exp with this plugin and resolved this issue?
> >> >> > Or
> >> > is
> >> >> > there an older thread regarding this plugin/issue that someone
> >> >> > could
> >> > point
> >> >> > me to?  Thanks for any help you guys can offer.
> >> >>
> >> >> Please think about migrating to the Server Settings plugin, which
> >> >> is actively maintained and should be able to do anything that the
> >> >> various outdated SpamAssassin front end plugins can do.  There are
> >> >> plenty of examples in the sample configuration files it comes with.
> >> >> If you find something that it cannot replicate, let me know.
> >> >
> >> > Thanks for the reply, I just received the digest.  I changed my
> >> > options so I can get a more immediate reply.  I downloaded Server
> >> > Settings, a bit confused by the configuration examples but I chose
> >> > one
> > that
> >> seemed to fit.
> >> > When I check the SA configuration validation, it says everything is
> > working.
> >> > In the Options, there are various selections related to the plugin
> >> > but choosing any of them generates this fatal error:
> >> >
> >> > Fatal error: Call to undefined function retrieve_server_setting()
> >> > in
> >> >
> >>
> /var/www/webmail.neoterichovercraft.com/plugins/server_settings/optio
> >> n
> >> > s.php
> >> > on line 281
> >> >
> >> > Is there a step that I've missed?  I get it regardless of which
> >> > configuration example I try to implement, but my initial thought is
> >> > that the config_example_file_using_php.php or
> >> > config_example_ftp.php matches our environment more closely.
> >>
> >> You probably didn't install the Server Settings Backend plugin.
> >> Should be referenced in the docs I think.
> >
> > That did help, I will need to learn some more about how this works.
> > Do you know off the top of your head if there is an additional plugin
> > or configuration that allows one-click white/blacklist from with an
email?
> 
> There was a blacklist feature in a couple different plugins, but whether
or not
> you can use that depends on where the blacklist is kept on your server.
> That's why the Server Settings Backend can be helpful
> - it abstracts the backend from the user interface - the blacklist can be
> anywhere you need it to be.
> 
> > From what I'm reading I think I can setup other spam configuration
> > options within the server setting plugin and I will mess around with
> > that, but I think the most desired function was the ability to easily
> > white/blacklist a sender or domain directly from an email.
> 
> I don't recall if I included examples of how to put "blacklist" or
"whitelist"
> links on the read message screen that use the Server Settings (Backend)
> infrastructure, but it can probably be done without too much trouble.
> HOWEVER, this is the last thing you should be looking to implement.  What
> would you blacklist - the "From" address?
> That address is the first thing spammers spoof.  In general, exposing
blacklists
> to users is misleading and unproductive.  Whitelists, yes, perhaps, but
you
> really should focus on implementing a high quality anti-spam system for
your
> users.
> 
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php

Hello Paul:

Thanks for the reply.  We already have a SpamAssassin system on the mail
server.  However, the president of the company still gets spam that he says
is consistently from the same organization/individual or contains words such
as "male enlargement", etc.  So he requests the ability to blacklist, which
is a feature that exists in SpamAssassin so I'm not sure why we would not
want to use it.  Regardless, he pays the bills so I will try to accommodate
him.  I hope you can understand this.  The former plugin I mentioned was
setup perfectly to allow fine tune control over the SpamAssassin
configuration (black/whitelist, threshold, rules, etc).   Of course that
plugin has a major bug, so all we need is some basic front end functionality
in the K.I.S.S. mentality.  The former plugin could blacklist both domain
and sender, but we might want to whitelist as well (supported by the
plugin).

So is it possible to modify the front end to allow the black/white list
functionality from within the message?  I've come to understand how the
options page works and I believe I can set that up to duplicate the main
SpamAssassin config we need, but he would get confused trying to find the
option page and really wants the feature directly in the reading view.

--
Ryan Dagey
President, Dagey Technology Solutions LLC

Re: [SM-PLUGINS] php-5.4.10-1 / custom_from

[Paul L. <pa...@sq...>]

On Tue, Jan 1, 2013 at 10:12 AM, Scott Ruckh <sr...@ge...> wrote:
>
> Yo.   This is what you said earlier: Paul Lesniewski
>> On Tue, Jan 1, 2013 at 9:24 AM, Scott Ruckh <sr...@ge...> wrote:
>>> SquirrelMail version:  1.4.23 (SVN 2012-12-21)
>>> Every plugin installed: (change_sqlpass, delete_move_next, select_range,
>>> javascript_libs, custom_from, avelsieve)
>>> PHP version: (php-5.4.10-1)
>>> Web server Apache (httpd-2.2.3-65), lighttpd (lighttpd-1.4.31-1)
>>> IMAP server (cyrus-imapd-2.4.16-1)
>>> SMTP server (postfix-2.9.1-1)
>>> OS and, if applicable, distribution (CentOS Linux 5.8 x64, kernel
>>> 2.6.18-308.24.1)
>>>
>>> PHP was recently upgraded to  PHP 5.4.  It appears that the custom_from
>>> plugin is no longer working correctly with my environment.
>>>
>>> I removed the existing custom_from directory from the plugins directory.
>>> I downloaded custom_from-2.0-1.4.0 from squirrelmail repository.  I
>>> extracted the tarball to plugins directory, copied
>>> config/config_example.php to config/config.php, and ran the squirrelmail
>>> configure to ensure the custom_from was selected in the "Installed
>>> Plugins" section.  No changes were made to config.php.
>>
>> If you made no changes to the configuration, please try deleting this
>> file.
>>
>>> As I am running
>>> version 1.4.23, I am under the impression the compatibility plugin is
>>> not
>>> necessary.
>>>
>>> When clicking on "Compose", the From field is not displayed.  The
>>> expected
>>> result is that the From field would be displayed.
>>>
>>> I tried to enable display_errors in php.ini, but no errors are displayed
>>> when clicking on the Compose link.
>>>
>>> It is assumed the PHP 5.4 upgrade has caused this plugin to stop
>>> functioning.
>>
>> That is doubtful if there are no errors being reported in your logs.
>> I'd suggest looking in your web server error logs instead of turning
>> on display_errors.
>>
>> --
>> Paul Lesniewski
>> SquirrelMail Team
>> Please support Open Source Software by donating to SquirrelMail!
>> http://squirrelmail.org/donate_paul_lesniewski.php
>>
>>
>
> Deleting the config.php did not change the results.
>
> The following lines are the only thing showing up in the ssl_error_log
> from the web server:
>
> The "From" field is also not present when choosing to "Reply".

Make sure the user preference setting for it is enabled.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-PLUGINS] php-5.4.10-1 / custom_from

[Scott R. <sr...@ge...>]

Yo.   This is what you said earlier: Paul Lesniewski
> On Tue, Jan 1, 2013 at 9:24 AM, Scott Ruckh <sr...@ge...> wrote:
>> SquirrelMail version:  1.4.23 (SVN 2012-12-21)
>> Every plugin installed: (change_sqlpass, delete_move_next, select_range,
>> javascript_libs, custom_from, avelsieve)
>> PHP version: (php-5.4.10-1)
>> Web server Apache (httpd-2.2.3-65), lighttpd (lighttpd-1.4.31-1)
>> IMAP server (cyrus-imapd-2.4.16-1)
>> SMTP server (postfix-2.9.1-1)
>> OS and, if applicable, distribution (CentOS Linux 5.8 x64, kernel
>> 2.6.18-308.24.1)
>>
>> PHP was recently upgraded to  PHP 5.4.  It appears that the custom_from
>> plugin is no longer working correctly with my environment.
>>
>> I removed the existing custom_from directory from the plugins directory.
>> I downloaded custom_from-2.0-1.4.0 from squirrelmail repository.  I
>> extracted the tarball to plugins directory, copied
>> config/config_example.php to config/config.php, and ran the squirrelmail
>> configure to ensure the custom_from was selected in the "Installed
>> Plugins" section.  No changes were made to config.php.
>
> If you made no changes to the configuration, please try deleting this
> file.
>
>> As I am running
>> version 1.4.23, I am under the impression the compatibility plugin is
>> not
>> necessary.
>>
>> When clicking on "Compose", the From field is not displayed.  The
>> expected
>> result is that the From field would be displayed.
>>
>> I tried to enable display_errors in php.ini, but no errors are displayed
>> when clicking on the Compose link.
>>
>> It is assumed the PHP 5.4 upgrade has caused this plugin to stop
>> functioning.
>
> That is doubtful if there are no errors being reported in your logs.
> I'd suggest looking in your web server error logs instead of turning
> on display_errors.
>
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php
>
>

Deleting the config.php did not change the results.

The following lines are the only thing showing up in the ssl_error_log
from the web server:

[Tue Jan 01 11:00:09 2013] [error] [client x.x.x.x] File does not exist:
/usr/local/squirrelmail/www/favicon.ico
[Tue Jan 01 11:00:20 2013] [error] [client x.x.x.x] PHP Strict Standards: 
Non-static method DO_Sieve::decode_script() should not be called
statically in
/usr/local/squirrelmail/www/plugins/avelsieve/include/sieve_getrule.inc.php
on line 67, referer: https://webmail.gemneye.org/src/webmail.php

Possibly unrelated, but the following PHP error is displayed when choosing
to "Reply" rather then choosing "Compose" :

Strict Standards: Non-static method Message::parseStructure() should not
be called statically in /usr/local/squirrelmail/www/functions/mime.php on
line 36 Strict Standards: Non-static method Message::parseBodyStructure()
should not be called statically in
/usr/local/squirrelmail/www/class/mime/Message.class.php on line 296

The "From" field is also not present when choosing to "Reply".

Thank you for your response.
Scott

Re: [SM-PLUGINS] php-5.4.10-1 / custom_from

[Paul L. <pa...@sq...>]

On Tue, Jan 1, 2013 at 9:24 AM, Scott Ruckh <sr...@ge...> wrote:
> SquirrelMail version:  1.4.23 (SVN 2012-12-21)
> Every plugin installed: (change_sqlpass, delete_move_next, select_range,
> javascript_libs, custom_from, avelsieve)
> PHP version: (php-5.4.10-1)
> Web server Apache (httpd-2.2.3-65), lighttpd (lighttpd-1.4.31-1)
> IMAP server (cyrus-imapd-2.4.16-1)
> SMTP server (postfix-2.9.1-1)
> OS and, if applicable, distribution (CentOS Linux 5.8 x64, kernel
> 2.6.18-308.24.1)
>
> PHP was recently upgraded to  PHP 5.4.  It appears that the custom_from
> plugin is no longer working correctly with my environment.
>
> I removed the existing custom_from directory from the plugins directory.
> I downloaded custom_from-2.0-1.4.0 from squirrelmail repository.  I
> extracted the tarball to plugins directory, copied
> config/config_example.php to config/config.php, and ran the squirrelmail
> configure to ensure the custom_from was selected in the "Installed
> Plugins" section.  No changes were made to config.php.

If you made no changes to the configuration, please try deleting this file.

> As I am running
> version 1.4.23, I am under the impression the compatibility plugin is not
> necessary.
>
> When clicking on "Compose", the From field is not displayed.  The expected
> result is that the From field would be displayed.
>
> I tried to enable display_errors in php.ini, but no errors are displayed
> when clicking on the Compose link.
>
> It is assumed the PHP 5.4 upgrade has caused this plugin to stop functioning.

That is doubtful if there are no errors being reported in your logs.
I'd suggest looking in your web server error logs instead of turning
on display_errors.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

[SM-PLUGINS] php-5.4.10-1 / custom_from

[Scott R. <sr...@ge...>]

SquirrelMail version:  1.4.23 (SVN 2012-12-21)
Every plugin installed: (change_sqlpass, delete_move_next, select_range,
javascript_libs, custom_from, avelsieve)
PHP version: (php-5.4.10-1)
Web server Apache (httpd-2.2.3-65), lighttpd (lighttpd-1.4.31-1)
IMAP server (cyrus-imapd-2.4.16-1)
SMTP server (postfix-2.9.1-1)
OS and, if applicable, distribution (CentOS Linux 5.8 x64, kernel
2.6.18-308.24.1)

PHP was recently upgraded to  PHP 5.4.  It appears that the custom_from
plugin is no longer working correctly with my environment.

I removed the existing custom_from directory from the plugins directory. 
I downloaded custom_from-2.0-1.4.0 from squirrelmail repository.  I
extracted the tarball to plugins directory, copied
config/config_example.php to config/config.php, and ran the squirrelmail
configure to ensure the custom_from was selected in the "Installed
Plugins" section.  No changes were made to config.php.  As I am running
version 1.4.23, I am under the impression the compatibility plugin is not
necessary.

When clicking on "Compose", the From field is not displayed.  The expected
result is that the From field would be displayed.

I tried to enable display_errors in php.ini, but no errors are displayed
when clicking on the Compose link.

It is assumed the PHP 5.4 upgrade has caused this plugin to stop functioning.

Thank You.
-- 

Re: [SM-PLUGINS] php-5.4.10-1 / avelsieve

[Scott R. <sr...@ge...>]

Yo.   This is what you said earlier: Scott Ruckh
>
> Yo.   This is what you said earlier: Peter Senft
>> Hi,
>>
>> I had the same issue and created a patch for avelsieve to run on PHP
>> 5.3. and higher:
>>
>> http://www.rfc3092.net/projects/avelsieve/
>>
>> That should take care of the warnings for split() and other deprecated
>> functions. Not sure if that also fixes the other problem. Maybe give it
>> a shot and let me know.
>>
>> FYI, that is just a patch and not the official version or a branch.
>> AFAIK that patch was incorporated into the official version but so far
>> there no new version including the patch was released.
>>
>> Peter
>
> I downloaded avelsieve-1.9.9-hps.tar.gz from the link you provided above.
> I renamed my current avelsieve directory, and unpacked your tarball
> archive into the squirrelmail plugin directory.  I copied my existing
> config.php to  the newly unpacked avelsieve/config directory (I believe
> this is the default config.php file).
>
> I did not have debugging turned on nor did I enable displaying PHP errors,
> but the avelsieve rules are now displayed upon clicking the "Filters"
> link.
>
> I will have to test further, but your patches are definitely better than
> before.  Thank you for your work, being part of the community and taking
> the time to respond the my note.  Your time and work is much appreciated.
>
> Thank You.

Just an FYI --

Although it does not seem to be an issue, the following error is displayed
from the main screen after a successful login when display_errors is
enabled.

Strict Standards: Non-static method DO_Sieve::decode_script() should not
be called statically in
/usr/local/squirrelmail/www/plugins/avelsieve/include/sieve_getrule.inc.php
on line 67 Select Range

Thank You.

[SM-PLUGINS] Bug Report

[wijnand s. <w.s...@ca...>]

I subscribe to the squirrelmail-users mailing list. 
[x ] True - No
need to CC me when replying 
[ ] False - Please CC me when replying


This bug occurs when Iopen my webmail ... 



The description of the bug: 


I can reproduce the
bug by: 


(Optional) I got bored and found the bug occurs
in: 


(Optional) I got really bored and here's a fix: 


---------------------------------------------- 

My browser information: 
Mozilla/5.0 (compatible; MSIE 9.0; Windows
NT 6.0; Trident/5.0) 

My web server information: 
PHP
Version 5.2.17 
PHP Extensions (List) 
* 0 = date 
* 1 =
libxml 
* 2 = openssl 
* 3 = pcre 
* 4 = zlib 
* 5 =
bz2 
* 6 = calendar 
* 7 = ctype 
* 8 = curl 
* 9 =
hash 
* 10 = filter 
* 11 = ftp 
* 12 = gettext 
* 13
= gmp 
* 14 = session 
* 15 = iconv 
* 16 = mime_magic 
* 17 = posix 
* 18 = pspell 
* 19 = Reflection 
* 20 =
standard 
* 21 = shmop 
* 22 = SimpleXML 
* 23 = SPL 
* 24 = sockets 
* 25 = exif 
* 26 = sysvmsg 
* 27 =
sysvsem 
* 28 = sysvshm 
* 29 = tokenizer 
* 30 = wddx 
* 31 = xml 
* 32 = apache2handler 
* 33 = gd 
* 34 = json

* 35 = mbstring 
* 36 = mcrypt 
* 37 = mysql 
* 38 =
mysqli 
* 39 = PDO 
* 40 = pdo_mysql 
* 41 = pdo_sqlite 
* 42 = zip 

SquirrelMail-specific information: 
Version:
1.4.19 
Plugins (List) 
* 0 = abook_group 
* 1 = bookmarks

* 2 = bug_report 
* 3 = calendar 
* 4 = compatibility 
* 5 = fortune 
* 6 = html_mail 
* 7 = listcommands 
* 8 =
login_auto 
* 9 = message_details 
* 10 = msg_flags 
* 11 =
newmail 
* 12 = notes 
* 13 = preview_pane 
* 14 =
sent_subfolders 
* 15 = show_user_and_ip 
* 16 = squirrelspell

* 17 = todo 
* 18 = translate 
* 19 = view_as_html 
*
20 = empty_trash 
* 21 = abook_import_export 
* 22 =
abook_group_pagination 
* 23 = avelsieve 
* 24 =
calendar_file_backend 
* 25 = smallcal 
* 26 = auto_prune_sent

* 27 = check_quota 
* 28 = delete_move_next 
* 29 =
select_language 

My IMAP server information: 
Server type:
cyrus 
Server info: * OK [HIDDEN] Ready pop20.prolocation.net
0002097c 
Capabilities: IMAP4 IMAP4REV1 

Re: [SM-PLUGINS] php-5.4.10-1 / avelsieve

[Brendan P. <br...@db...>]

I've tried installing the patched version but having trouble, I get a 
blank page when trying to add a rule.

If anyone else if using dovecot could they please send me their 
config.php file for comparison.

Thanks
Brendan

Re: [SM-PLUGINS] SpamAssassin plugin overwrites values on submit

[Paul L. <pa...@sq...>]

>> >> > I?ve been researching this problem to no avail for sometime.  We
>> >> > use the (very old) SpamAssassin plugin
>> >> > (http://squirrelmail.org/plugin_view.php?id=146) with our
> Squirrelmail.
>> >> > This plugin serves us well in terms of ease of use and we can
>> >> > connect it easily to our mail server spamassassin.  The only issue
>> >> > that any time a
>> > user
>> >> > makes a change (like adding an email to the blacklist/whitelist),
>> >> > all
>> > prior
>> >> > changes are overwritten.  In the README, there is a note that this
>> >> > was a
>> >> bug
>> >> > but resolved.
>> >> >
>> >> >
>> >> >
>> >> > Does anyone have any exp with this plugin and resolved this issue?
>> >> > Or
>> > is
>> >> > there an older thread regarding this plugin/issue that someone
>> >> > could
>> > point
>> >> > me to?  Thanks for any help you guys can offer.
>> >>
>> >> Please think about migrating to the Server Settings plugin, which is
>> >> actively maintained and should be able to do anything that the
>> >> various outdated SpamAssassin front end plugins can do.  There are
>> >> plenty of examples in the sample configuration files it comes with.
>> >> If you find something that it cannot replicate, let me know.
>> >
>> > Thanks for the reply, I just received the digest.  I changed my
>> > options so I can get a more immediate reply.  I downloaded Server
>> > Settings, a bit confused by the configuration examples but I chose one
> that
>> seemed to fit.
>> > When I check the SA configuration validation, it says everything is
> working.
>> > In the Options, there are various selections related to the plugin but
>> > choosing any of them generates this fatal error:
>> >
>> > Fatal error: Call to undefined function retrieve_server_setting() in
>> >
>> /var/www/webmail.neoterichovercraft.com/plugins/server_settings/option
>> > s.php
>> > on line 281
>> >
>> > Is there a step that I've missed?  I get it regardless of which
>> > configuration example I try to implement, but my initial thought is
>> > that the config_example_file_using_php.php or config_example_ftp.php
>> > matches our environment more closely.
>>
>> You probably didn't install the Server Settings Backend plugin.
>> Should be referenced in the docs I think.
>
> That did help, I will need to learn some more about how this works.  Do you
> know off the top of your head if there is an additional plugin or
> configuration that allows one-click white/blacklist from with an email?

There was a blacklist feature in a couple different plugins, but
whether or not you can use that depends on where the blacklist is kept
on your server.  That's why the Server Settings Backend can be helpful
- it abstracts the backend from the user interface - the blacklist can
be anywhere you need it to be.

> From what I'm reading I think I can setup other spam configuration options
> within the server setting plugin and I will mess around with that, but I
> think the most desired function was the ability to easily white/blacklist a
> sender or domain directly from an email.

I don't recall if I included examples of how to put "blacklist" or
"whitelist" links on the read message screen that use the Server
Settings (Backend) infrastructure, but it can probably be done without
too much trouble.  HOWEVER, this is the last thing you should be
looking to implement.  What would you blacklist - the "From" address?
That address is the first thing spammers spoof.  In general, exposing
blacklists to users is misleading and unproductive.  Whitelists, yes,
perhaps, but you really should focus on implementing a high quality
anti-spam system for your users.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-PLUGINS] SpamAssassin plugin overwrites values on submit

[Ryan D. <dt...@da...>]

> On Thu, Dec 27, 2012 at 11:28 AM, Ryan Dagey <dt...@da...> wrote:
> >> On Thu, Nov 15, 2012 at 7:24 PM, Ryan Dagey <dt...@da...> wrote:
> >> > Hello:
> >> >
> >> >
> >> >
> >> > I?ve been researching this problem to no avail for sometime.  We
> >> > use the (very old) SpamAssassin plugin
> >> > (http://squirrelmail.org/plugin_view.php?id=146) with our
Squirrelmail.
> >> > This plugin serves us well in terms of ease of use and we can
> >> > connect it easily to our mail server spamassassin.  The only issue
> >> > that any time a
> > user
> >> > makes a change (like adding an email to the blacklist/whitelist),
> >> > all
> > prior
> >> > changes are overwritten.  In the README, there is a note that this
> >> > was a
> >> bug
> >> > but resolved.
> >> >
> >> >
> >> >
> >> > Does anyone have any exp with this plugin and resolved this issue?
> >> > Or
> > is
> >> > there an older thread regarding this plugin/issue that someone
> >> > could
> > point
> >> > me to?  Thanks for any help you guys can offer.
> >>
> >> Please think about migrating to the Server Settings plugin, which is
> >> actively maintained and should be able to do anything that the
> >> various outdated SpamAssassin front end plugins can do.  There are
> >> plenty of examples in the sample configuration files it comes with.
> >> If you find something that it cannot replicate, let me know.
> >>
> >> Cheers,
> >>
> >>   Paul
> >>
> >> --
> >> Paul Lesniewski
> >> SquirrelMail Team
> >> Please support Open Source Software by donating to SquirrelMail!
> >> http://squirrelmail.org/donate_paul_lesniewski.php
> >
> > Hello Paul:
> >
> > Thanks for the reply, I just received the digest.  I changed my
> > options so I can get a more immediate reply.  I downloaded Server
> > Settings, a bit confused by the configuration examples but I chose one
that
> seemed to fit.
> > When I check the SA configuration validation, it says everything is
working.
> > In the Options, there are various selections related to the plugin but
> > choosing any of them generates this fatal error:
> >
> > Fatal error: Call to undefined function retrieve_server_setting() in
> >
> /var/www/webmail.neoterichovercraft.com/plugins/server_settings/option
> > s.php
> > on line 281
> >
> > Is there a step that I've missed?  I get it regardless of which
> > configuration example I try to implement, but my initial thought is
> > that the config_example_file_using_php.php or config_example_ftp.php
> > matches our environment more closely.
> 
> You probably didn't install the Server Settings Backend plugin.
> Should be referenced in the docs I think.
> 
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php

Hello Paul:

That did help, I will need to learn some more about how this works.  Do you
know off the top of your head if there is an additional plugin or
configuration that allows one-click white/blacklist from with an email?
>From what I'm reading I think I can setup other spam configuration options
within the server setting plugin and I will mess around with that, but I
think the most desired function was the ability to easily white/blacklist a
sender or domain directly from an email.  Thanks for all your help, I won't
hesitate to ask if there are other questions that come up.

Re: [SM-PLUGINS] SpamAssassin plugin overwrites values on submit

[Paul L. <pa...@sq...>]

On Thu, Dec 27, 2012 at 11:28 AM, Ryan Dagey <dt...@da...> wrote:
>> On Thu, Nov 15, 2012 at 7:24 PM, Ryan Dagey <dt...@da...> wrote:
>> > Hello:
>> >
>> >
>> >
>> > I?ve been researching this problem to no avail for sometime.  We use the
>> > (very old) SpamAssassin plugin
>> > (http://squirrelmail.org/plugin_view.php?id=146) with our Squirrelmail.
>> > This plugin serves us well in terms of ease of use and we can connect it
>> > easily to our mail server spamassassin.  The only issue that any time a
> user
>> > makes a change (like adding an email to the blacklist/whitelist), all
> prior
>> > changes are overwritten.  In the README, there is a note that this was a
>> bug
>> > but resolved.
>> >
>> >
>> >
>> > Does anyone have any exp with this plugin and resolved this issue?  Or
> is
>> > there an older thread regarding this plugin/issue that someone could
> point
>> > me to?  Thanks for any help you guys can offer.
>>
>> Please think about migrating to the Server Settings plugin, which is
>> actively maintained and should be able to do anything that the various
>> outdated SpamAssassin front end plugins can do.  There are plenty of
>> examples in the sample configuration files it comes with.  If you find
>> something that it cannot replicate, let me know.
>>
>> Cheers,
>>
>>   Paul
>>
>> --
>> Paul Lesniewski
>> SquirrelMail Team
>> Please support Open Source Software by donating to SquirrelMail!
>> http://squirrelmail.org/donate_paul_lesniewski.php
>
> Hello Paul:
>
> Thanks for the reply, I just received the digest.  I changed my options so I
> can get a more immediate reply.  I downloaded Server Settings, a bit
> confused by the configuration examples but I chose one that seemed to fit.
> When I check the SA configuration validation, it says everything is working.
> In the Options, there are various selections related to the plugin but
> choosing any of them generates this fatal error:
>
> Fatal error: Call to undefined function retrieve_server_setting() in
> /var/www/webmail.neoterichovercraft.com/plugins/server_settings/options.php
> on line 281
>
> Is there a step that I've missed?  I get it regardless of which
> configuration example I try to implement, but my initial thought is that the
> config_example_file_using_php.php or config_example_ftp.php matches our
> environment more closely.

You probably didn't install the Server Settings Backend plugin.
Should be referenced in the docs I think.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-PLUGINS] php-5.4.10-1 / avelsieve

[Scott R. <sr...@ge...>]

Yo.   This is what you said earlier: Peter Senft
> Hi,
>
> I had the same issue and created a patch for avelsieve to run on PHP
> 5.3. and higher:
>
> http://www.rfc3092.net/projects/avelsieve/
>
> That should take care of the warnings for split() and other deprecated
> functions. Not sure if that also fixes the other problem. Maybe give it
> a shot and let me know.
>
> FYI, that is just a patch and not the official version or a branch.
> AFAIK that patch was incorporated into the official version but so far
> there no new version including the patch was released.
>
> Peter

I downloaded avelsieve-1.9.9-hps.tar.gz from the link you provided above. 
I renamed my current avelsieve directory, and unpacked your tarball
archive into the squirrelmail plugin directory.  I copied my existing
config.php to  the newly unpacked avelsieve/config directory (I believe
this is the default config.php file).

I did not have debugging turned on nor did I enable displaying PHP errors,
but the avelsieve rules are now displayed upon clicking the "Filters"
link.

I will have to test further, but your patches are definitely better than
before.  Thank you for your work, being part of the community and taking
the time to respond the my note.  Your time and work is much appreciated.

Thank You.

Re: [SM-PLUGINS] SpamAssassin plugin overwrites values on submit

[Ryan D. <dt...@da...>]

> On Thu, Nov 15, 2012 at 7:24 PM, Ryan Dagey <dt...@da...> wrote:
> > Hello:
> >
> >
> >
> > I?ve been researching this problem to no avail for sometime.  We use the
> > (very old) SpamAssassin plugin
> > (http://squirrelmail.org/plugin_view.php?id=146) with our Squirrelmail.
> > This plugin serves us well in terms of ease of use and we can connect it
> > easily to our mail server spamassassin.  The only issue that any time a
user
> > makes a change (like adding an email to the blacklist/whitelist), all
prior
> > changes are overwritten.  In the README, there is a note that this was a
> bug
> > but resolved.
> >
> >
> >
> > Does anyone have any exp with this plugin and resolved this issue?  Or
is
> > there an older thread regarding this plugin/issue that someone could
point
> > me to?  Thanks for any help you guys can offer.
> 
> Please think about migrating to the Server Settings plugin, which is
> actively maintained and should be able to do anything that the various
> outdated SpamAssassin front end plugins can do.  There are plenty of
> examples in the sample configuration files it comes with.  If you find
> something that it cannot replicate, let me know.
> 
> Cheers,
> 
>   Paul
> 
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php

Hello Paul:

Thanks for the reply, I just received the digest.  I changed my options so I
can get a more immediate reply.  I downloaded Server Settings, a bit
confused by the configuration examples but I chose one that seemed to fit.
When I check the SA configuration validation, it says everything is working.
In the Options, there are various selections related to the plugin but
choosing any of them generates this fatal error:

Fatal error: Call to undefined function retrieve_server_setting() in
/var/www/webmail.neoterichovercraft.com/plugins/server_settings/options.php
on line 281

Is there a step that I've missed?  I get it regardless of which
configuration example I try to implement, but my initial thought is that the
config_example_file_using_php.php or config_example_ftp.php matches our
environment more closely. 

--
Ryan Dagey

Re: [SM-PLUGINS] php-5.4.10-1 / avelsieve

[Peter S. <pe...@rf...>]

Hi,

I had the same issue and created a patch for avelsieve to run on PHP
5.3. and higher:

http://www.rfc3092.net/projects/avelsieve/

That should take care of the warnings for split() and other deprecated
functions. Not sure if that also fixes the other problem. Maybe give it
a shot and let me know.

FYI, that is just a patch and not the official version or a branch.
AFAIK that patch was incorporated into the official version but so far
there no new version including the patch was released.

Peter

On 12/26/2012 05:45 PM, Scott Ruckh wrote:
> SquirrelMail version:  1.4.23 (SVN 2012-12-21)
> Every plugin installed: (change_sqlpass, delete_move_next, select_range,
> javascript_libs, custom_from, avelsieve)
> PHP version: (php-5.4.10-1)
> Web server Apache (httpd-2.2.3-65), lighttpd (lighttpd-1.4.31-1)
> IMAP server (cyrus-imapd-2.4.16-1)
> SMTP server (postfix-2.9.1-1)
> OS and, if applicable, distribution (CentOS Linux 5.8 x64, kernel
> 2.6.18-308.24.1)
> 
> PHP was recently upgraded to PHP 5.4.  Squirrelmail upgraded to SVN
> version 1.4.23 (from Dec 21, 2012).
> 
> It appears that after PHP upgrade the avelsieve plugin (avelsieve-1.9.9)
> no longer functions.
> 
> The avelsieve web site suggests using this mailing list for primary
> support for the plugin.
> 
> When the "Filters" link is clicked on from the main menu an empty blank
> white screen is given.  The expected result is for a list of the
> configured sieve rules to be displayed.
> 
> If PHP errors are turned on, the following errors are displayed:
> 
> These errors are displayed right after logging into squirrelmail, when the
> main interface is displayed.
> Deprecated: Function ereg() is deprecated in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/managesieve.lib.php
> on line 441 Deprecated: Function split() is deprecated in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/managesieve.lib.php
> on line 457 Deprecated: Function split() is deprecated in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/managesieve.lib.php
> on line 457 Deprecated: Function split() is deprecated in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/managesieve.lib.php
> on line 887 Deprecated: Function split() is deprecated in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/managesieve.lib.php
> on line 887 Deprecated: Function split() is deprecated in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/managesieve.lib.php
> on line 887 Deprecated: Function split() is deprecated in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/managesieve.lib.php
> on line 142 Deprecated: Function split() is deprecated in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/managesieve.lib.php
> on line 142 Strict Standards: Non-static method DO_Sieve::decode_script()
> should not be called statically in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/sieve_getrule.inc.php
> on line 67 Select Range
> 
> This error is displayed when clicking on the "Filters" link.
> Fatal error: Call to undefined function session_unregister() in
> /usr/local/squirrelmail/www/plugins/avelsieve/include/html_rulestable.inc.php
> on line 164
> 
> This plugin has not been updated in quite a long time, is it actively
> maintained?
> 
> Thank You.
> Scott
> 
> 

-- 
/"\                        | Peter Senft
\ / ASCII ribbon campaign  | E-Mail : pe...@du...
 X  against HTML mail      | Jabber : du...@ja...
/ \                        | ICQ    : 62090394



-- 
/"\                        | Peter Senft
\ / ASCII ribbon campaign  | E-Mail : pe...@rf...
 X  against HTML mail      | Jabber : du...@ja...
/ \                        | ICQ    : 62090394