Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#15232 - [squirrelmail] 1.4.19-1 annoying little problem

Attached to Project: Arch Linux
Opened by David Rosenstrauch (darose) - Tuesday, 23 June 2009, 16:26 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 25 June 2009, 15:10 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Paul Mattal (paul)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I'm seeing an annoying little problem since the upgrade to squirrelmail 1.4.19-1: when I'm looking at a subfolder, and press the button to mark a message read or unread, after squirrelmail refreshes I'm back at the root folder (Inbox). Very annoying!

Anyone know cause or fix?


Additional info:
* package version(s)

1.4.19-1

* config and/or log files etc.

- Squirrelmail using Dovecot IMAP (but with courier-like mailbox structure - i.e., all boxes are children of INBOX)
- the following SM plugins are installed:
1. filters
2. vkeyboard
3. mini
4. spam_buttons
5. compatibility
6. quicksave
7. timeout_user



Steps to reproduce:

* start reading messages in a sub-folder (e.g., INBOX.Testing) by clicking on the "Testing" folder in the left pane
* "Current Folder: Testing" is displayed at the top of the right pane
* select the first message in the Testing mailbox
* press the "Unread" button
* "Current Folder: INBOX" is displayed at the top of the right pane

i.e., although the message does get marked unread, squirrelmail should not return me to INBOX. It should remain in the Testing mailbox.


This task depends upon

Closed by  Roman Kyrylych (Romashka)
Thursday, 25 June 2009, 15:10 GMT
Reason for closing:  Not a bug
Comment by Paul Mattal (paul) - Thursday, 25 June 2009, 04:07 GMT
Are you sure it was introduced in .19? If so, it is traceable to one of about 150 lines that differ between .18 and .19.
Comment by David Rosenstrauch (darose) - Thursday, 25 June 2009, 14:46 GMT
Crap. I downgraded to .17 and the problem is showing there too. WTF?!?!? I have no idea *what's* causing the problem, frankly: squirrelmail? dovecot?

But the problem is definitely here - and reproducible at will.

Any suggestions?
Comment by David Rosenstrauch (darose) - Thursday, 25 June 2009, 14:55 GMT
ugh ... it's a plugin issue

Will post more details as I learn them.
Comment by David Rosenstrauch (darose) - Thursday, 25 June 2009, 14:58 GMT
It's the spam_buttons plugin.

You can close this bug. Sorry for the noise.

Loading...