> >> >> I have started getting "unexpected EOF" when I do tar zxvf on > >> > attachments > >> >> that have been gzipped. This happens even if I save the > > attachment > >> >> directly from the message in the Sent folder on the machine it was > >> > created > >> >> on - so it has never even been sent anywhere. > >> >> > >> >> If I compare the original file before it was attached with the one > >> > that I > >> >> save from the attachment, the latter is one byte shorter. > >> > > >> > Note that you can create these kinds of 'mysterious' problems with > attachments when editing any of the SquirrelMail source files, > particularly plugin configuration files. If you have even one > > space, > >> > linefeed or other character before the "<?php" tag at the top or > > after > >> > the "?>" tag at the bottom of any such files, your attachments will > > all > >> > be corrupted in the manner that you describe. > >> > > >> I have now "solved" this problem by completely replacing the > >> .../squirrelmail/functions directory in my SM 1.4.1 installation with > > the > >> functions directory from the latest Development CVS 1.5. Not a > > solution > >> that I am entirely happy with, as it remains to be seen what other > problems this rather brutal remedy may cause. > >> From my researches I have managed to convince myself at least, that > > the > >> problem occurs with SM 1.4.1 and PHP 4.3.2 and is fixed in the > > development > >> version. > > > > Uhhhh... 1.5 is *not* stable and is *not* intended to be compatible with > 1.4. The two should not be mixed and matched, especially in a > > production environment. They will become increasingly different as new > development continues... I recommend you find another solution. > > > > - Paul > > I agree with you completely. The trouble is that, quite apart from my > anxiety about trying to splice PHP 4.2.x back into my Gentoo setup with > Apache 2, PHP 4..2.x is no longer supported (according to the php.net > site) and I have not had any success getting SM 1.4.1 to work with PHP > 4.3.x, possibly due to this "fread() problem". > > Any other suggestions would be welcome? > > Is anyone else using PHP 4.3.2 with SM 1.4.1. and not getting the problem > that I get with truncated attachments? >
If it's PHP's wonderful new fread functionality (argh), and we can verify it is as such, someone should look for an appropriate way to integrate the fix into SM 1.4. I seem to recall Marc having an issue with this, however... - Paul ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
