gmane.mail.squirrelmail.devel

MartyMacGyver | 18 Jun 02:51

Problems with 1.5.2 versus 1.5.1


I looked around for the answer to this but I've never seen anything that
matches this issue, so here goes.

I've been using Squirrelmail 1.5.1 for a while now, self-installed and all
(note that I don't have root on this system).  I created a parallel
installation of 1.5.2 (latest SVN) around the same time I installed that
(1-2 years ago now) and configured it similarly (most notably, I've enabled
filters on both).  When I first tried 1.5.2 I figured chalked this issue up
to it being inherently unstable or my php was old but now that I'm coming
back to it (with a newer PHP even) it's still not working any better and I'd
like to get to the bottom of why this is.

In 1.5.1 the filters work just fine and aren't causing any side-effects. 
All folders work as expected.

In 1.5.2, browsing my various mail folders (IMAP) works fine, but if I
enable filters a very weird thing happens: empty folders come up empty as
expected and the Inbox folder works as expected, but any other folder with
contents which is not Inbox ends up having a message list *exactly like
Inbox*, no matter what's really in it!  Selecting a message in those folders
produces an error (probably because they are actually Inbox messages in the
list and it's trying to map those message IDs into the sub-folder).  I'm not
sure what to make of this weirdness but again, it doesn't happen when I have
filters enabled (but from what I can tell filters should be pretty basic
stuff).

I'm using php 5.2.5.  The configtest results for 1.5.1 have no complaints
but 1.5.2 has one warning about magic_quotes_gpc being enabled (not sure I
can do anything about that but I suspect this has nothing to do with this

(Continue reading)

Michael Peddemors | 18 Jun 04:10

Re: Problems with 1.5.2 versus 1.5.1

On Tuesday 17 June 2008 17:53, MartyMacGyver wrote:
> Category:        PHP  [sometimes with ", Delayed" after it]
> Message:        A session had already been started - ignoring
> session_start() FILE:
>   /home/≤my_login>/squirrelmail_1.5.2/functions/global.php

Generally, these are harmless.. global.php tends to be inherited all over the 
place, and always tries to do a seesion_start() when it is loaded.

This issue is not related to your problem

--

-- 
--
"Catch the Magic of Linux..."
------------------------------------------------------------------------
Michael Peddemors - President/CEO - LinuxMagic
Products, Services, Support and Development
Visit us at http://www.linuxmagic.com
------------------------------------------------------------------------
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" is a Registered TradeMark of Wizard Tower TechnoServices Ltd.
------------------------------------------------------------------------
604-589-0037 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended 
solely for the use of the individual or entity to which they are addressed. 
Please note that any views or opinions presented in this email are solely 
those of the author and are not intended to  represent those of the company.

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

(Continue reading)

MartyMacGyver | 19 Jun 07:51

Re: Problems with 1.5.2 versus 1.5.1

Michael Peddemors wrote:
> 
> On Tuesday 17 June 2008 17:53, MartyMacGyver wrote:
>> Category:        PHP  [sometimes with ", Delayed" after it]
>> Message:        A session had already been started - ignoring
>> session_start() FILE:
>>   /home/≤my_login>/squirrelmail_1.5.2/functions/global.php
> 
> Generally, these are harmless.. global.php tends to be inherited all over
> the 
> place, and always tries to do a seesion_start() when it is loaded.
> This issue is not related to your problem
> 

Well, at least that rules that out.

So, the question is, is anyone successfully using the latest 1.5.2 with IMAP
folders and server-side filters enabled (and without the problems I
described originally)?  It seems odd to me that 1.5.1 (and 1.4.x before it)
work just fine for me but 1.5.2 appears broken.  I got 1.5.1 working without
much difficulty, so it's either a known issue or something on my end, and
I'd very much like to understand what I'm doing wrong if it comes down to
"operator error".  

 - Marty
--

-- 
View this message in context: http://www.nabble.com/Problems-with-1.5.2-versus-1.5.1-tp17957649p17997773.html
Sent from the squirrelmail-devel mailing list archive at Nabble.com.

(Continue reading)

Paul Lesniewski | 19 Jun 21:15

Re: Problems with 1.5.2 versus 1.5.1

On Wed, Jun 18, 2008 at 10:51 PM, MartyMacGyver <martin <at> falatic.com> wrote:
>
>
> Michael Peddemors wrote:
>>
>> On Tuesday 17 June 2008 17:53, MartyMacGyver wrote:
>>> Category:        PHP  [sometimes with ", Delayed" after it]
>>> Message:        A session had already been started - ignoring
>>> session_start() FILE:
>>>   /home/≤my_login>/squirrelmail_1.5.2/functions/global.php
>>
>> Generally, these are harmless.. global.php tends to be inherited all over
>> the
>> place, and always tries to do a seesion_start() when it is loaded.
>> This issue is not related to your problem
>>
>
> Well, at least that rules that out.
>
> So, the question is, is anyone successfully using the latest 1.5.2 with IMAP
> folders and server-side filters

*server-side*???  You mentioned NOTHING about *server-side* filters in
your original post.  In fact, my feeling was that it was vague enough
- were you in fact referring to the "filters" plugin that comes with
SM or not - that was my first question, but now you've really got me
wondering.  You need to come back with *SPECIFICS* - what software you
are using, what versions, and how to reproduce the issue (do you have
any filters configured and in use if you are using the "filters"
plugin), etc.

(Continue reading)

MartyMacGyver | 19 Jun 23:02

Re: Problems with 1.5.2 versus 1.5.1

Paul Lesniewski wrote:
> 
> *server-side*???  You mentioned NOTHING about *server-side* filters in
> your original post.  In fact, my feeling was that it was vague enough
> - were you in fact referring to the "filters" plugin that comes with
> SM or not - that was my first question, but now you've really got me
> wondering.  You need to come back with *SPECIFICS* - what software you
> are using, what versions, and how to reproduce the issue (do you have
> any filters configured and in use if you are using the "filters"
> plugin), etc.
> 

Actually, I didn't know there were any *other* filters in SquirrelMail
besides the filters plugin, which is what I'm using and is what's causing
the problem here.

What other info can I provide that isn't in my original post? This has
happened with every version of 1.5.2 I've grabbed from the SVN over the last
year or two (I've tried this a few times now), most recently with
squirrelmail-20080616_0000-SVN.devel.tar.gz.  I have no such problems with
1.5.1.

Again, I'm using the filters plugin (I also enabled the info plugin but it
doesn't affect the issue whether present or absent).  I had many filters but
I just tried another experiment: I *completely removed* my prefs file,
logged back in.  No filters = works ok.

Then I created just one filter in Options -> Message Filtering:
 - If Subject contains dgdfdsfgdfgdfsg then move to INBOX.Trash

(Continue reading)

Paul Lesniewski | 20 Jun 04:17

Re: Problems with 1.5.2 versus 1.5.1

>> *server-side*???  You mentioned NOTHING about *server-side* filters in
>> your original post.  In fact, my feeling was that it was vague enough
>> - were you in fact referring to the "filters" plugin that comes with
>> SM or not - that was my first question, but now you've really got me
>> wondering.  You need to come back with *SPECIFICS* - what software you
>> are using, what versions, and how to reproduce the issue (do you have
>> any filters configured and in use if you are using the "filters"
>> plugin), etc.
>
> Actually, I didn't know there were any *other* filters in SquirrelMail
> besides the filters plugin, which is what I'm using and is what's causing
> the problem here.

The filters plugin is NOT server-side filtering.  It's filtering in
the client - always the least desirable choice.

> What other info can I provide that isn't in my original post? This has
> happened with every version of 1.5.2 I've grabbed from the SVN over the last
> year or two (I've tried this a few times now), most recently with
> squirrelmail-20080616_0000-SVN.devel.tar.gz.  I have no such problems with
> 1.5.1.

Since no one can reproduce it, you probably need to show what filter
settings you have configured.  Dig them out of the prefs file (or DB)
for best accuracy.  Make sure to disable all other plugins.  Make sure
you are using the filters plugin that comes with the 1.5.2 package.
Try blasting all your user prefs and add each filter back one at a
time until you find the problematic one.

> Again, I'm using the filters plugin (I also enabled the info plugin but it

(Continue reading)

MartyMacGyver | 20 Jun 04:41

Re: Problems with 1.5.2 versus 1.5.1

Paul Lesniewski wrote:
> 
> The filters plugin is NOT server-side filtering.  It's filtering in
> the client - always the least desirable choice.
> ...
> If at all possible, you should have a server-side filtering solution.
> There are front ends for them for SquirrelMail, but they do the work
> when the mail is delivered, NOT when you log into the client.
> 

My bad... I was thinking of the fact that SquirrelMail resides on the server
(versus, say, Thunderbird, which would reside on a local machine). 
Unfortunately server-side filtering is not an option with my current host
(they actually removed it a long while back, which is why I went and
installed 1.5.1 and am happily using its filters plugin... it beats having
nothing).

Paul Lesniewski wrote:
> 
>> Then I created just one filter in Options -> Message Filtering:
>>  - If Subject contains dgdfdsfgdfgdfsg then move to INBOX.Trash
>>
>> With that, problem returned.
> 
> OK, this is helpful.  Someone can look at this.
> 

I presume this covers your earlier suggestion about disabling all filters
and then enabling them one by one.

(Continue reading)

Paul Lesniewski | 20 Jun 08:22

Re: Problems with 1.5.2 versus 1.5.1

On Thu, Jun 19, 2008 at 7:41 PM, MartyMacGyver <martin <at> falatic.com> wrote:
>
>
> Paul Lesniewski wrote:
>>
>> The filters plugin is NOT server-side filtering.  It's filtering in
>> the client - always the least desirable choice.
>> ...
>> If at all possible, you should have a server-side filtering solution.
>> There are front ends for them for SquirrelMail, but they do the work
>> when the mail is delivered, NOT when you log into the client.
>>
>
> My bad... I was thinking of the fact that SquirrelMail resides on the server
> (versus, say, Thunderbird, which would reside on a local machine).
> Unfortunately server-side filtering is not an option with my current host
> (they actually removed it a long while back, which is why I went and
> installed 1.5.1 and am happily using its filters plugin... it beats having
> nothing).
>
>
> Paul Lesniewski wrote:
>>
>>> Then I created just one filter in Options -> Message Filtering:
>>>  - If Subject contains dgdfdsfgdfgdfsg then move to INBOX.Trash
>>>
>>> With that, problem returned.
>>
>> OK, this is helpful.  Someone can look at this.
>>

(Continue reading)

MartyMacGyver | 20 Jun 08:57

Re: Problems with 1.5.2 versus 1.5.1

Paul Lesniewski wrote:
> 
> I cannot reproduce this.  What is the "What to scan" option set to?
> Please try downloading the Reset User Preferences plugin, save a copy
> of your preferences and then reset them and try again from a blank
> slate.  Have you modified the code in ANY way (even patches for
> plugins, etc)?  Are you also sure your entire 1.5.2 code is very
> recent?  Also note that 1.5.1 has a known package compromise and
> numerous security exploits.  If nothing works for you, you can try to
> debug yourself - comment out the right_main_after_header hook
> registration in setup.php and see if that fixes it.  If so, uncomment
> it and then start putting return; commands in filters.php in the
> start_filters() function until it breaks again.  But DON'T do these
> things until you've verified you are running the newest 1.5.2 code and
> all other factors have been eliminated.
> 

"What to scan" is set to "only unread messages".

I appreciate the attempt... sounds like it's just my installation and/or
server.  I'll try your suggestions and will start digging in and debug it
(thanks very much for the tips on how to debug the filters plugin).

I'll also do a full reinstall with at least the SVN snapshot I recently
grabbed, just to be safe (I recall doing this at least twice now in the last
year but better to be thorough).

--

-- 
View this message in context: http://www.nabble.com/Problems-with-1.5.2-versus-1.5.1-tp17957649p18024101.html

(Continue reading)

Paul Lesniewski | 20 Jun 09:19

Re: Problems with 1.5.2 versus 1.5.1

On Thu, Jun 19, 2008 at 11:57 PM, MartyMacGyver <martin <at> falatic.com> wrote:
>
>
> Paul Lesniewski wrote:
>>
>> I cannot reproduce this.  What is the "What to scan" option set to?
>> Please try downloading the Reset User Preferences plugin, save a copy
>> of your preferences and then reset them and try again from a blank
>> slate.  Have you modified the code in ANY way (even patches for
>> plugins, etc)?  Are you also sure your entire 1.5.2 code is very
>> recent?  Also note that 1.5.1 has a known package compromise and
>> numerous security exploits.  If nothing works for you, you can try to
>> debug yourself - comment out the right_main_after_header hook
>> registration in setup.php and see if that fixes it.  If so, uncomment
>> it and then start putting return; commands in filters.php in the
>> start_filters() function until it breaks again.  But DON'T do these
>> things until you've verified you are running the newest 1.5.2 code and
>> all other factors have been eliminated.
>>
>
> "What to scan" is set to "only unread messages".

Still cannot reproduce it...

> I appreciate the attempt... sounds like it's just my installation and/or
> server.  I'll try your suggestions and will start digging in and debug it
> (thanks very much for the tips on how to debug the filters plugin).
>
> I'll also do a full reinstall with at least the SVN snapshot I recently
> grabbed, just to be safe (I recall doing this at least twice now in the last

(Continue reading)

Return

Return to gmane.mail.squirrelmail.devel.

Advertisement

Search Archive

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane