no feedback, resolving.

Can you provide an example message?

Posible patch for function "_storeAttachment" in /horde/imp/lib/Compose.php



     /**

      * Stores the attachment data in its correct location.

      *

      * @access private

      *

      * @param object MIME_Part &$part     The MIME_Part of the attachment.

      * @param string $data                Either the filename of the

      *                                    attachment or, if $vfs_file is

      *                                    false, the attachment data.

      * @param optional boolean $vfs_file  If using VFS, is $data a filename?

      */

     function _storeAttachment(&$part, $data, $vfs_file = true)

     {

         global $conf;



       + // Not add attachment if $data is empty

       + if (empty($data)) {

       +     return PEAR::raiseError('No data provided');

       + }



         /* Store in VFS. */

         if ($conf['compose']['use_vfs']) {

Apache 1.3.29, php 4.3.7, Oracle 8.1.7, IMP(head)



When I press 'forward' to a message with this MIME structure:



0. multipart/mixed

    1.- multipart/alternative

        1.1.- text/plain

        1.2.- text/html

    2.- application/pdf

    3.- application/pdf





In the compose window(VFS with SQL driver) appears 3 attachments, 2 pdf's

and one 'application/octet-stream' with 0 bytes(the fisrt), if I change to

VFS file driver only shows the 2 pdf's(OK!).



The multipart/alternative part has "" in '$_contents", the difference is VFS

file driver returns PEAR_Error when function 'writeData' write 0 bytes in

'$data', but it creates a file with o bytes in vfsroot. On the other 
hand VFS SQL driver not return errors(appear a warnnig

in apache error_log) and add the 0 bytes part to '_cache[]' in the function

'_storeAttachment' in horde/imp/lib/Compose.php.



Is this a VFS or Compose error? It has sense add a 0 bytes "file" in

SQL/file VFS?