Re: [SM-USERS] SM adding a carriage return to the first line of image attachments

[p d. t. <pdo...@an...>]

> porthos:/etc/squirrelmail# uname -a
> Linux porthos 2.4.23 #2 Tue Dec 2 08:47:53 PST 2003 i686 unknown
> porthos:/etc/squirrelmail# cat /etc/debian_version 
> 3.0
> 
> porthos:/etc/squirrelmail# nc localhost 143
> * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
> THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE] Courier-IMAP
> ready. Copyright 1998-2003 Double Precision, Inc.  See COPYING for
> distribution information.
> 
> porthos:/etc/squirrelmail# dpkg -l|grep php
> ii  php4           4.1.2-6woody3  A server-side, HTML-embedded scripting langu
> ii  php4-pear      4.1.2-6woody3  PEAR - PHP Extension and Application Reposit
> ii  php4-pgsql     4.1.2-4        PostgreSQL module for php4
> 
> The problem I am having I am able to reproduce under version
> 1.2.6-1.3, 1.4.2-1 and 1.5.0-1.
> 
> The weird thing is that sometimes it causes errors and other times it
> works fine.  The problem happens when trying to view an image
> attachment (jpeg is all that I've tried).  Sometimes I just get a
> broken image and other times I get the following error message:
> The image "www.domain.com/squirrelmail/src/download.php?startMessage=1&passed_id=1&mailbox=INBOX&ent_id=2"
> cannot be displayed because it contains errors.
> 
> It appears to be causing this error because something is adding a
> carriage return to the very top of the image file.  By downloading the

You probably introduced an empty line into one of your plugin 
configuration files.  Make sure any and all php files you edit do not 
have ANY whitespace before the initial <?php tag and the closing ?> tag!

  - Paul

> image file and running cmp on it against the original it shows me
> this.  If I download it and try and open it up in XV all I get is
> binary, but if I open the file up in vi, dd the top line and then save
> the file I then can open it up in XV or any other image viewer w/o a
> problem.
> 
> 
> I'm am not seeing any errors being written to any of the system logs
> or apache logs.
> 
> 
> I have another server here with essentially all the same software,
> installed from debian packages that I can't reproduce the error on. 
> The only difference I see between the two is the version of php that's
> running.  On the server that I am not able to create this error it's
> running:
> ii  php4           4.3.7-1.dotdeb A server-side, HTML-embedded scripting langu
> ii  php4-cgi       4.3.7-1.dotdeb A server-side, HTML-embedded scripting langu
> ii  php4-pear      4.3.7-1.dotdeb PEAR - PHP Extension and Application Reposit
> ii  php4-pgsql     4.3.7-1.dotdeb PostgreSQL module for php4
> 
> I am considering upgrading to those versions of php on the problematic
> server but I need to make sure first that it won't break the web sites
> that are running on there.  Before I go and do that I would like to
> get some opinions on whether or not that could be the problem.
> 
> Any help would be really appreciated.