Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#2483 Attachments are truncated at 88K

open
nobody
5
2007-06-19
2007-06-19
Jamie F. Dahl
No

it does not matter what file extension/File type I receive, IF the attachment is larger then 88k the squirrelmail seems to munge up the file and truncate it at 88K.

I've confirmed this was SM related as thunderbird (and outlook) do not exhibit said behavior.

Is there some setting I have overlooked, or is this a real bug?

Thanks

Discussion

  • Jamie F. Dahl
    Jamie F. Dahl
    2007-06-19

    Logged In: YES
    user_id=1821636
    Originator: YES

    and I should note the following
    Apache/2.2.4 (FreeBSD) mod_ssl/2.2.4 OpenSSL/0.9.8e
    SM 1.4.11[svn]

     
  • Dave Steinberg
    Dave Steinberg
    2007-06-22

    Logged In: YES
    user_id=35019
    Originator: NO

    I had a similar issue with FreeBSD 5.4 and courier-imap. I never figured it out, but after upgrading to 6.2 and a new courier-imap, it went away. Can you try upgrading?

    PS - My bug is filed as # 1599087.

     
  • Logged In: YES
    user_id=620333
    Originator: NO

    We are trying to resolve the bug you brought to our attention.

    We need more information before we can proceed. Please see below
    for more information.
    PHP version -
    IMAP server -
    SqurrelMail version -
    Exact description of problem including
    file producing error -
    line number of error -
    error description -
    In what context did the error occur? (example: When I send a
    message with an attachment) -
    If the error occurs with certain message, include those with full
    headers.

     
  • Jamie F. Dahl
    Jamie F. Dahl
    2007-10-10

    Logged In: YES
    user_id=1821636
    Originator: YES

    PHP version (and apache info too)- Server Version: Apache/2.0.61 (FreeBSD) PHP/5.2.4 mod_ssl/2.0.61 OpenSSL/0.9.8e
    Server Built: Sep 17 2007 04:09:34

    IMAP server - courier-imap-4.1.3
    * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION] Courier-IMAP ready. Copyright 1998-2005 Double Precision, Inc. See COPYING for distribution information.

    I will take a screenshot and upload..
    SqurrelMail version - 1.4.10a (FreeBSD ports version) also tested with 1.4.11svn-nightly build

    Exact description of problem including:
    when viewing attachments (whether inline (image) or downloading (other formats)) any attachment larger then 90k will be truncated at either 83k or 88k. If you click the "download" option it only downloads the first 83k of the file, and for viewing inline (images), it will load about 80-90k worth of data, and truncate the rest, so given a file of 100k, it will draw the HxW size, and fill in however much data was crammed into 88k etc..and leave the rest out as gray space..

     
  • Jamie F. Dahl
    Jamie F. Dahl
    2007-10-10

    smaller file.

     
    Attachments
  • Jamie F. Dahl
    Jamie F. Dahl
    2007-10-10

    Logged In: YES
    user_id=1821636
    Originator: YES

    I'll follow this attachment w/ a print (pdf) of the "message details" (it's too big to paste here and not look like crud).

    File Added: bad-image.pdf

     
  • Logged In: YES
    user_id=620333
    Originator: NO

    Can you check all your apache configurations for LimitRequestBody?

     
  • Jamie F. Dahl
    Jamie F. Dahl
    2007-10-10

    Logged In: YES
    user_id=1821636
    Originator: YES

    jamied@www -->grep LimitRequestBody *
    vhosts.conf:LimitRequestBody 2147483647

    that parameter was not set, so after reading about it, I set it to some ungodly number, still did not change the behavior.
    FWIW, apache/php are now "current"..
    although I still need to upgrade the specific php modules as well (php_imap).

     
  • Logged In: YES
    user_id=620333
    Originator: NO

    The option doesn't have to be there. I was just making sure it was not there, and setting a low limit.

    We don't use the php_imap libraries, so they won't impact this issue.

    What are your settings in your php.ini for:

    error_reporting
    display_errors
    log_errors
    max_execution_time
    max_input_time
    memory_limit

     
  • Jamie F. Dahl
    Jamie F. Dahl
    2007-10-10

    Logged In: YES
    user_id=1821636
    Originator: YES

    47 jamied@www -->for i in error_reporting display_errors log_errors max_execution_time max_input_time memory_limit; do grep $i /usr/local/etc/php.ini; done
    ; error_reporting is a bit-field. Or each number up to get desired error
    ;error_reporting = E_ALL & ~E_NOTICE
    ;error_reporting = E_ALL & ~E_NOTICE | E_STRICT
    ;error_reporting = E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR
    error_reporting = E_ALL & ~E_NOTICE
    ; Eval the expression with current error_reporting(). Set to true if you want
    ; error_reporting(0) around the eval().
    ; instead (see below). Keeping display_errors enabled on a production web site
    display_errors = On
    ; Even when display_errors is on, errors that occur during PHP's startup
    log_errors = Off
    ; Set maximum length of log_errors. In error_log information about the source is
    log_errors_max_len = 1024
    max_execution_time = 60 ; Maximum execution time of each script, in seconds
    max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
    memory_limit = 128M ; Maximum amount of memory a script may consume (128MB)
    48 jamied@www -->