gmane.mail.squirrelmail.announce

Re: [SM-ANNOUNCE] ANNOUNCE: SquirrelMail 1.4.22 Released

Paul Lesniewski — 2011-07-14T15:41:51

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...


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.

[SM-ANNOUNCE] ANNOUNCE: SquirrelMail 1.4.22 Released

Paul Lesniewski — 2011-07-12T22:20:25

Greetings all,

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 comple

[SM-ANNOUNCE] ANNOUNCE: SquirrelMail 1.4.21 Released

Paul Lesniewski — 2010-07-23T06:08:21

Greetings,

The SquirrelMail Team is pleased to announce the release of
SquirrelMail version 1.4.21.  This is primarily a maintenance release
which addresses a smattering of small issues and adds some fine-tuning
of recent changes.  It also closes two relatively low-risk security
issues.

Before this release, for environments with highly active users, the
number of security tokens could have bloated user session (and
preference) files to an unacceptable size, hurting overall
responsiveness.  This release scales back the default validity period
of security tokens from 30 days to two days, which should fix this
problem in most cases.  The administrator is always free to change
this value by specifying $max_token_age_days in
config/config_local.php.

There are also fixes for minor issues related to header folding,
faster and more resilient display of encoded subjects, quoting of
encoded addresses upon reply, provision of a subject when using
forward-as-attachment, and a few other tidbits.

This release also inc

[SM-ANNOUNCE] ANNOUNCE: SquirrelMail 1.4.20 Released

Paul Lesniewski — 2010-03-07T03:00:40

Greetings,

The SquirrelMail Team is pleased to announce the release of
SquirrelMail version 1.4.20.  This release makes final the changes
implemented in our last two release candidates and adds several
smaller fixes and feature improvements.

Of those new fixes and improvements not included in our last release
candidate, the most notable fix is that for the formerly broken search
page, but we've also fixed sorting in the Sent folder, handling of
complex mailto: addresses, display of multibyte subjects, quoting of
encoded headers, automatic installation address detection (especially
useful for lighttpd environments), a privacy issue related to DNS
prefetching of email content, and added unread links in the message
view and a Gmail IMAP configuration option.

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

Due to the security fixes included in our last two release candidate
packages, we advise all users of SquirrelMail versions 1.4.19 and

[SM-ANNOUNCE] ANNOUNCE: SquirrelMail 1.4.20 Release Candidate 2 NowAvailable

Paul Lesniewski — 2009-08-18T01:00:29

Hello,

The SquirrelMail Team is pleased to bring you the second release
candidate ahead of our next SquirrelMail version: 1.4.20-RC2.  Hot on
the coattails of 1.4.20 release candidate 1, we received some helpful
feedback from our friends at Secunia Research and have followed up
with another release candidate.  The risk of using the 1.4.20 release
candidate 1 package instead of this one is very low, but we encourage
the community to help test code that we hope to release as officially
stable in the near future.  Those who can upgrade to release candidate
2 are encouraged to do so!

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

This release can be downloaded from the SquirrelMail website:

   http://squirrelmail.org/download

Package md5sums
===============
94015fb018cb2165fdfb3c41fd2b8065  squirrelmail-1.4.20-RC2.tar.bz2
03523e8c7ad9d630988d5001c5743b69  squirrelmail-1.4.20-RC2.tar.gz
0fbceec5b9775e72be2b42d197761bc0  squirrelmail-1.4.2

[SM-ANNOUNCE] ANNOUNCE: SquirrelMail 1.4.20 Release Candidate 1 NowAvailable

Paul Lesniewski — 2009-08-12T10:47:01

Greetings,

The SquirrelMail Team is pleased to bring you the first release
candidate ahead of our next SquirrelMail version: 1.4.20RC1.  Because
of the somewhat invasive nature of some of the changes we have
recently made, we are issuing a "release candidate" before we
officially move to version 1.4.20.  While we have been very careful to
ensure the stability of SquirrelMail, this version, 1.4.20 release
candidate 1, has undergone limited testing, and we'd like to have more
feedback before we make version 1.4.20 final.

The most notable changes for this version are the addition of two
security mechanisms that fight cross-site request forgeries (CSRF),
the removal of some deprecated PHP functions, some minor fixes in the
filters plugin, and increased user privacy.  For more complete
details, see the ReleaseNotes and ChangeLog files included in this
release (in the doc/ directory).

Due to the security issues fixed herein, we'd like to advise all users
of SquirrelMail software to upgrade.  However, because th