Hi, I have the same problem on 2 FreeBSD 4.x servers.

If I try to open a message with some (not all) JPG's it returns a blank page.

I don't have any c-client installed on my systems.



Thank you.

No segfaults appear in Apache logs (where they normally go on very 
rare occasion when they do happen).  Upgraded to c-client 2004g (the 
latest) and still have this problem (was using 2002e (debian)).



I have figured out the problem.  The problem seems to be a 750KB JPG 
file (and in the other e-mail probably a similarly large jpg or bmp 
file).  I can create additional jpg files in the 500-800KB range and 
have the same issue.



My first thought was memory limit, but the memory limit was already at 
64MB.  I have upped it to 80M and now all is well with these messages. 
  Sorry for the false alarm here.



This leads to a feature suggestion (as with 5MB digital camera images 
these days, this could grow as a problem if a <1MB file fills 80MB).   
I imagine there's some code to create a thumbnail or get image 
information that is resulting in the image being decompressed in 
memory, and the memory is being exhausted in those cases.  Maybe a 
configurable option -or- auto-detection based on the current memory 
limit as to what is a reasonable image to decode, and otherwise just 
leave it intact?



Sorry for the alarm again (though maybe having this here will help 
another).  I'd be very curious about that feature request though, as 
e-mails and images are only getting bigger.



Cheers,!

Try to update c-client.  Or at least enable logging.  See if your 
server is segfaulting.  Most likely, this is a malformed message that 
is not being handled by your version of c-client - which means this is 
almost 100% guaranteed not an IMP issue.

So far I've only seen this on messages from one or two avid outlook 
users who love to place attachments inline into their messages and 
whatnot.  The message window just appears blank- no errors in PHP or 
apache logs-  Just a blank page returned to me (no headers, no 
anything.  0 bytes).



I've traced the problem down to the buildmessage() function call on 
line 231 of imp/message.php.  If I add comments around this section in 
imp/message.php, the message loads perfectly.



if (!$imp_contents->buildMessage()) {

     _returnToMailbox(null, 'message_missing');

     require IMP_BASE . '/mailbox.php';

     exit;

}



I've attempted to trace down the particular problem in buildMessage 
and the horde libraries, but can't seem to quite pinpoint it, but in 
any case, it probably shouldn't be just exiting out.



PHP 5.1, Apache 2.  This seems to be the only issue I'm experiencing with it.