Many Warnings with Viewing Mail

Bug #1072804 reported by Bill
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
squirrelmail (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I just upgraded to Ubuntu 12.10, and I get a lot of php warnings when viewing any message:

Strict Standards: Non-static method Message::parseStructure() should not be called statically in /usr/share/squirrelmail/functions/mime.php on line 36

Strict Standards: Non-static method Message::parseBodyStructure() should not be called statically in /usr/share/squirrelmail/class/mime/Message.class.php on line 296

Warning: Cannot modify header information - headers already sent by (output started at /usr/share/squirrelmail/functions/mime.php:36) in /usr/share/squirrelmail/functions/page_header.php on line 31

$ lsb_release -rd
Description: Ubuntu 12.10
Release: 12.10

$ apt-cache policy squirrelmail
squirrelmail:
  Installed: 2:1.4.23~svn20120406-1
  Candidate: 2:1.4.23~svn20120406-1
  Version table:
 *** 2:1.4.23~svn20120406-1 0
        500 http://us.archive.ubuntu.com/ubuntu/ quantal/universe amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Bill (bill-launchpad) wrote :

Upon further usage, these errors only appear to happen when viewing a new message (potentially due to changing the message status from unread to read. I also tested, and it does not happen when clicking the "unread" link nor when reading a message that was unread by clicking on that link.

Revision history for this message
Thijs Kinkhorst (kink) wrote :

This is because of newly added strict notices in PHP 5.4. They are warnings intended for developers only, and thus have no effect on the application.

It's recommend by PHP that production instances do not enable these strict standards warnings and especially do not output them to the browser. I recommend that you update your PHP configuration accordingly.

Revision history for this message
Bill (bill-launchpad) wrote :

I can update the settings, but wouldn't it make more sense to patch the warnings? Also, if the messages are only intended for developers and developers are typically more sophisticated users, wouldn't it make sense to change the settings in the package itself instead of relying on all non-developers to change the settings from developer-suggested to user-suggested settings?

Revision history for this message
Karl-Martin Skontorp (karlmartinskontorp) wrote :

This seems to be related to bug #3491925 in the SquirrelMail bug tracker. Accessible here: http://sourceforge.net/tracker/index.php?func=detail&aid=3491925&group_id=311&atid=100311

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in squirrelmail (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel Ahlenius (ubuntu-on) wrote :

This bug does not just generate warning, but remove the whole subject and parts in the body... Without a subject you cannot open the emails. It renders the current package unusable...

Patches are available at their site, above...
http://sourceforge.net/tracker/index.php?func=detail&aid=3491925&group_id=311&atid=100311

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.