Paul Lesniewski | 1 Apr 2011 02:21
Favicon

Re: Captcha and Lockout

On Wed, Mar 30, 2011 at 6:36 PM, LuKreme <kremels <at> kreme.com> wrote:
> The email when lockout fires says to remove the CAPTCHA requirement remove
> the <IP>_CAPTCHA_TOO_MANY_FAILED_LOGIN_ATTEMPTS setting from the
> "lockout_plugin_login_failure_information" preference set.
>
> OK. HOW do I do this? (still running 1.6 of Lockout and 1.2 of CAPTCHA)

If you are using file-based preferences, look in your data directory
for a file called:

lockout_plugin_login_failure_information.pref

If your data directory is hashed (level 4), I think it should be in:

data/2/1/2/4/lockout_plugin_login_failure_information.pref

For other hash levels, just use find:

find . -name lockout_plugin_login_failure_information.pref

If you are storing preferences in a database, a query like this will
show the needed entires:

SELECT * FROM userprefs WHERE user = 'lockout_plugin_login_failure_information';

--

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

Paul Lesniewski | 16 Apr 2011 22:48
Favicon

Re: Cleanup e Empty-Trash

On Mon, Oct 16, 2006 at 6:36 AM, francesca_mecca
<francesca_mecca <at> yahoo.it> wrote:
> Hi,
> I've install the plugins Cleanup and Empty-trash.I uncompressed the
> archives in the plugins
> directory,  I run configure and add the plugins.
> It seems very simply.... but this plugins don't work and I don't see any
> error.... What is wrong?

There was a bug.  It was fixed in the newest version of this plugin.
Sorry for the late reply.

> Here my details:
>
>    * IMAP Server:  'other';
>    * PHP: 4.4.2
>    * Web server:  Apache 2
>    * Platform:  SunOS 5.9
>    * SquirrelMail version: 1.4.8

--

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

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
(Continue reading)

Rolando Cañer Roblejo | 19 Apr 2011 23:23
Picon

SquirrelMail 1.4.20 doesn't work with change_sqlpass-3.3-1.2

Hi,

I installed the change_sqlpass-3.3-1.2 plugins in my squirrelmail and it does not work good. Also, I installed the compatibility plugin 2.0.16.1.0 and the Pear DB library.
I use Ubuntu 10.04, PHP version 5.3.2, Apache2, Dovecot-Imap and Postfix.

When I try to change the password this error appear:

Strict Standards: Non-static method DB::connect() should not be called statically in /usr/share/squirrelmail/plugins/change_sqlpass/functions.php on line 92 Strict Standards: Non-static method DB::parseDSN() should not be called statically in /usr/share/php/DB.php on line 520 Strict Standards: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in /usr/share/php/DB/common.php on line 1899 Strict Standards: Non-static method DB::isError() should not be called statically, assuming $this from incompatible context in /usr/share/php/DB.php on line 688 Strict Standards: Non-static method DB::errorMessage() should not be called statically, assuming $this from incompatible context in /usr/share/php/DB.php on line 965 Strict Standards: Non-static method DB::isError() should not be called statically, assuming $this from incompatible context in /usr/share/php/DB.php on line 688 Strict Standards: Non-static method DB::isError() should not be called statically in /usr/share/php/DB.php on line 557 Strict Standards: Non-static method DB::isError() should not be called statically in /usr/share/squirrelmail/plugins/change_sqlpass/functions.php on line 93

ERROR:

Could not make database connection

Thanks!

Rolando.
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins
Paul Lesniewski | 20 Apr 2011 21:00
Favicon

Re: SquirrelMail 1.4.20 doesn't work with change_sqlpass-3.3-1.2

2011/4/19 Rolando Cañer Roblejo <rolando.caner <at> cnic.edu.cu>:
> Hi,
>
> I installed the change_sqlpass-3.3-1.2 plugins in my squirrelmail and it
> does not work good. Also, I installed the compatibility plugin 2.0.16.1.0
> and the Pear DB library.
> I use Ubuntu 10.04, PHP version 5.3.2, Apache2, Dovecot-Imap and Postfix.
>
> When I try to change the password this error appear:
>
> Strict Standards: Non-static method DB::connect() should not be called

You should do an Internet search before posting.  If you do so, you'll
find this is a common issue, one that is caused by Pear DB.  You
should relax you PHP error reporting settings to exclude E_STRICT.

> statically in /usr/share/squirrelmail/plugins/change_sqlpass/functions.php
> on line 92 Strict Standards: Non-static method DB::parseDSN() should not be
> called statically in /usr/share/php/DB.php on line 520 Strict Standards:
> Non-static method DB::errorMessage() should not be called statically,
> assuming $this from incompatible context in /usr/share/php/DB/common.php on
> line 1899 Strict Standards: Non-static method DB::isError() should not be
> called statically, assuming $this from incompatible context in
> /usr/share/php/DB.php on line 688 Strict Standards: Non-static method
> DB::errorMessage() should not be called statically, assuming $this from
> incompatible context in /usr/share/php/DB.php on line 965 Strict Standards:
> Non-static method DB::isError() should not be called statically, assuming
> $this from incompatible context in /usr/share/php/DB.php on line 688 Strict
> Standards: Non-static method DB::isError() should not be called statically
> in /usr/share/php/DB.php on line 557 Strict Standards: Non-static method
> DB::isError() should not be called statically in
> /usr/share/squirrelmail/plugins/change_sqlpass/functions.php on line 93
>
> ERROR:
>
> Could not make database connection

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

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

Michael Heydekamp | 1 May 2011 20:50
Picon
Favicon

quicksave and sent_confirmation incompatible?

Hello all,

during Easter we just updated our Debian and SM installation (details
further below), and for the first time afterwards also installed the
quicksave plugin, which we now find one of the most useful SM extensions
(and which we weren't aware of before at all, to be honest). Furthermore,
we had installed the sent_confirmation plugin already for years without
any problems in daily usage.

The thing now is, that neither quicksave nor sent_confirmation appear to
work correctly if at the same time both plugins are installed (and
activated). After I had sent the very first mail under this configuration,
no sent confirmation came up, but just a sort of empty window instead (not
really empty, but just with the typical SM links - "Compose, Addresses,
Folders [...]" etc. - at the top and nothing else below).

Furthermore and much more important, from this point on I couldn't create
a new mail or reply to an existing one at all anymore. Either the same
"empty" window came up, or SM forced me to do a new login - I was in a
sort of infinite loop and somewhat stuck.

It should be noted that I have the option "Compose Messages in New Window"
activated. After I deactivated this option, I was able to create a new
mail or reply to an existing one again, but after sending it, SM often
couldn't display the INBOX (or any other mail folder) anymore and was just
displaying the same "empty" window in the right frame (with it's typical
links at the top). From time to time SM couldn't even access the mail
folders at all anymore (red warning message in the right frame, new login
required). This is all somewhat difficult to describe, as being pretty
inconsistent and happening "out of the blue".

Then we deactivated sent_confirmation and (almost) everything worked fine
with quicksave (except that quicksave sometimes "complained" about an
unsent message, although the message had indeed been sent, but that's a
different issue which we may discuss later on). Then we tried the opposite
(deactivated quicksave and activated sent_confirmation) and everything
worked fine as all the years before (but without the quicksave facility
unfortunately).

Also changing the order of these two plugins doesn't make any difference.

At a certain scenario (sorry, can't remember anymore which scenario it
exactly was), I copied the following javascript error message (IE8,
German):

---------------------------------------------------------------------------
> Meldung: 'document.forms.compose.body' ist Null oder kein Objekt Zeile: 22
> Zeichen: 1
> Code: 0
> URI:
http://www.freexp.de/webmail/src/compose.php?passed_id=16370&mailbox=INBOX&startMessage=1&passed_ent_id=0&smaction=reply---------------------------------------------------------------------------

Dunno if that might tell anybody anything...

We simply refuse to believe ;-) that the combination of these two plugins
shall not work (as they are both being maintained by the most active
person in the SM plugin area at all). So we're wondering what WE might be
doing wrong here - any hint?

On gmane.org we have found some issues in the list which were related to
the combined use of these two plugins (e.g.
http://permalink.gmane.org/gmane.mail.squirrelmail.plugins/14100), but all
of these problems were of a totally different character - and pretty
outdated as well.

So some help/hint would be most appreciated. Here are (hopefully) all
relevant details:

SM version:               1.4.21-1 (Debian squeeze)
compatibility plugin:     2.0.16-1
quicksave plugin:         2.4.5-1
sent_confirmation plugin: 1.6-1
spam_buttons plugin:      2.3.1-1
view_as_html plugin:      3.8-3 (Debian package)

Plus some more (IMO irrelevant) plugins. If you really want a complete
list, please let me know.

PHP5 version:             5.3.3-7 (Debian squeeze)
Web server:               Apache2 2.2.16-6+squeeze1
IMAP server:              dovecot 1.2.15-4 (Debian squeeze)
OS:                       Debian GNU/Linux 6.0.1 (squeeze) for i386 (kernel
                          linux-image-2.6.32-5-amd64)
Installation:             all of Debian squeeze via apt

My local system with which I saw the issues above is a Win7 Pro 64-bit,
Browser IE8 8.0.7600.16385. But we have seen the same issues on a WinXP
Pro SP3 system with Firefox 4 as well. The local system and the browser
don't appear to make any difference.

Any helpful advice most appreciated. If even more information required,
just let us know.
--

-- 
Michael Heydekamp
Co-Admin freexp.de
Düsseldorf/Germany

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins


Gmane