13 Jul 2011 00:20
[SM-ANNOUNCE] ANNOUNCE: SquirrelMail 1.4.22 Released
Paul Lesniewski <paul <at> squirrelmail.org>
2011-07-12 22:20:25 GMT
2011-07-12 22:20:25 GMT
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 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' {} \;
(Continue reading)
SquirrelMail has always been run by a
small group of volunteers, and we've never been paid for our efforts.
We do it because this is our passion; we do it for the love and the
fun. But running a high-profile project means that there is a
plethora of work from which no one gets much fun (or love). That's
taken its toll -- our numbers have dwindled and our visionary
initiatives for our next big release have had to take a back seat to
ongoing maintenance, such as responding to bug reports, looking over
plugin and patch submissions, fixing security vulnerabilities,
answering voluminous amounts of email on our mailing lists, and a slew
of other responsibilities. Oh, and then there's paying the bills,
family time, and cleaning the kitchen....
So it's time to ask our community to give back just a little bit. In
the best scenario, SquirrelMail should be able to support one or two
people working full time. To some, this may seem overly ambitious,
but we don't think so. Think of the good money that has been raised
RSS Feed