SquirrelMail 1.4.22 Released

propcgamer

Verified User
Joined
Dec 27, 2005
Messages
148
The SquirrelMail Team is pleased to announce the release of SquirrelMail version 1.4.22. This release contains a large number of performance enhancements, stability fixes and a few bug/security fixes.

The most important thing to note when upgrading to version 1.4.22 is that due to a fix made that standardizes the folder list display, administrators who had their configuration file set to work around this issue in the past will need to update their configuration. This will commonly affect those using Courier IMAP, but could affect others as well.

If you have $default_sub_of_inbox set to FALSE in your main configuration (or, using the configuration tool, see "3. Folder Defaults" ===> "12. Default Sub. of INBOX"), and you find after upgrade that your special folders (e.g., Trash, Drafts, Sent) are no longer listed at the top of your folder list, please change that value to TRUE.

Also, if you find that this upgrade prevents users from logging in with an error such as "ERROR: Could not complete request. Query: CREATE "Trash" Reason Given: Invalid mailbox name.", you will need to correct the user preference values for the problem folders. You can do so with commands such as the following for file-based preferences (adjust the data directory location as needed):

find /var/lib/squirrelmail/data/ -name *.pref -exec sed --in-place 's/trash_folder=Trash/trash_folder=INBOX.Trash/g' {} \;
find /var/lib/squirrelmail/data/ -name *.pref -exec sed --in-place 's/draft_folder=Drafts/draft_folder=INBOX.Drafts/g' {} \;
find /var/lib/squirrelmail/data/ -name *.pref -exec sed --in-place 's/sent_folder=Sent/sent_folder=INBOX.Sent/g' {} \;

Or, for database-based preferences:

UPDATE userprefs SET prefval = 'INBOX.Trash' WHERE prefkey = 'trash_folder' AND prefval = 'Trash';
UPDATE userprefs SET prefval = 'INBOX.Drafts' WHERE prefkey = 'draft_folder' AND prefval = 'Drafts';
UPDATE userprefs SET prefval = 'INBOX.Sent' WHERE prefkey = 'sent_folder' AND prefval = 'Sent';

MAKE SURE to back up your user preferences before doing any of the above!

This release also addresses several security issues, including some harsh but hard to exploit XSS bugs, a general clickjacking vulnerability, and a small problem with message sanitizing.

If only for the clickjacking protection, we recommend that users of previous versions of SquirrelMail upgrade at their earliest convenience.

For more complete details, see the ReleaseNotes and ChangeLog files included in this release (in the doc/ directory).

Now to wait for custombuild to be updated :D
 
Last edited:
How bout make a skin that doesnt look like it was made in 1991?
 
How bout make a skin that doesnt look like it was made in 1991?

It's actually what the "old timer" users like. Many good applications failed by loosing their traditional users and not be able to get new at the same time. Remember the program "GetRight"?

So redesign is a tricky thing. I personally prefer the design to NOT change unless I want to. That's why I keep using Windows XP (with the "Classic" 95/98 theme). It works and works good for me. Why changing the UI when it will not bring any more productivity in my job?
 
Also, in that same announcement, they're asking for donations and help for the upcoming Web 2.0 version of SquirrelMail.
 
Re: [SM-ANNOUNCE] ANNOUNCE: SquirrelMail 1.4.22 Released

Another small update from the SquirrelMail team:

Hello all,

We're sorry for the annoyance, but there were two important typos in
the update information that was included in the announcement of
SquirrelMail 1.4.22's release two days ago...

> Also, if you find that this upgrade prevents users from logging in
> with an error such as "ERROR: Could not complete request. Query:
> CREATE "Trash" Reason Given: Invalid mailbox name.", you will need to
> correct the user preference values for the problem folders. You can
> do so with commands such as the following for file-based preferences
> (adjust the data directory location as needed):
>
> find /var/lib/squirrelmail/data/ -name *.pref -exec sed --in-place
> 's/trash_folder=Trash/trash_folder=INBOX.Trash/g' {} \;
> find /var/lib/squirrelmail/data/ -name *.pref -exec sed --in-place
> 's/trash_folder=Drafts/trash_folder=INBOX.Drafts/g' {} \;
> find /var/lib/squirrelmail/data/ -name *.pref -exec sed --in-place
> 's/trash_folder=Sent/trash_folder=INBOX.Sent/g' {} \;

These last two commands use "trash_folder" where they should have used
"draft_folder" and "sent_folder". So the correct commands should be:

find /var/lib/squirrelmail/data/ -name *.pref -exec sed --in-place
's/draft_folder=Drafts/draft_folder=INBOX.Drafts/g' {} \;

find /var/lib/squirrelmail/data/ -name *.pref -exec sed --in-place
's/sent_folder=Sent/sent_folder=INBOX.Sent/g' {} \;

Thanks to Fernando Gozalo for spotting these typos.
 
errors after upgrade

I keep getting the following after upgrade.

Warning: Variable passed to each() is not an array or object in /var/www/html/squirrelmail-1.4.22/functions/mime.php on line 1594

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/squirrelmail-1.4.22/functions/mime.php:1594) in /var/www/html/squirrelmail-1.4.22/functions/page_header.php on line 31
 
a warning is not an error.

Edit php.ini and change the behavior of display_errors and error_reporting
 
Back
Top