Well here's a little update... Turns out this new installation is not being able to use Horde's VFS for storing attachments, that's why the message came up empty in the first place.
At Horde's conf.php I have $conf['vfs']['params']['vfsroot'] = '/tmp'; $conf['vfs']['type'] = 'file'; And apparently horde is dropping files there at /tmp successfully. But if at IMP's config I have $conf['compose']['use_vfs'] = true (Should we use the Horde VFS system for storing uploaded attachments?) then I get an error message stating that it "couldn't create VFS directory". If I change that parameter to false, the attachments work. What am I doing wrong here? And if it's not storing uploaded attachments in the VFS, where are they being stored? I hope it's not in RAM memory. Well now back to the forwarding issue... Having set use_vfs to false, attachments work again, if I click "entire message" it gets forwarded as an attachment a la rfc822 like Chuck said. "Body only" works properly. But "attachments only" is forwarding the attachments plus the original text in the body of the new message too. I believe that's what Eric thought would be useful, but I'm getting it already! Shouldn't this option forward *only* the attachments, without the original text, as the name said? Thanks. -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED]
