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
> 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
>
> With that, problem returned.

OK, this is helpful.  Someone can look at this.

>  If I delete that filter or disable the filters
> plugin and things are fine (but lacking the filter functionality which is
> the main reason I prefer SquirrelMail in the first place).

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.

>  Otherwise, any
> folder with messages looks just like Inbox (except Sent, which looks like
> inbox except all the "From" fields read as if they are from me).
>
> Again, I'm looking for some tips here: what can I test or change or redo
> that might help matters (or which would provide more detailed debugging
> info)?  I figured it'd be best to ask those who know the code far better
> than myself for a little guidance on this.  I think it's probably something
> simple, but I'm at a loss to think what it might be (assuming the filters
> plugin IS working OK for others).

Someone will look at this and hopefully reply on this thread soon.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
-----
squirrelmail-devel mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [email protected]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel