Tickets :: [#13665] linked attachment with link_attach_size_hard

6.0.0-alpha10

5/14/25

Summary	linked attachment with link_attach_size_hard
Queue	IMP
Queue Version	6.2.2
Type	Bug
State	Assigned
Priority	2. Medium
Owners	slusarz (at) horde (dot) org
Requester	lukas.weiss (at) raiffeisen (dot) it
Created	11/05/2014 (3843 days ago)
Due
Updated	08/17/2015 (3558 days ago)
Assigned	08/17/2015 (3558 days ago)
Resolved
Milestone
Patch	No

08/17/2015 06:01:01 PM	Jan Schneider	State ⇒ Assigned

08/14/2015 06:53:11 AM	lukas (dot) weiss (at) raiffeisen (dot) it	Comment #6	Reply to this comment
You had disabled linked attachments but still had linked attachment limit options defined in conf.php. This has been fixed in IMP 6.2.8. For me this bug is not resolved yet, still the same error with imp 6.2.9. I had/have link_attachments = true. Is there anything else i have to set?

02/25/2015 03:53:11 AM	Git Commit	Comment #5	Reply to this comment
Changes have been made in Git (master): commit a701ad0e6dc8421b591ed4e0e441acb7818ed8ec Author: Michael M Slusarz <slusarz@horde.org> Date: Tue Feb 24 20:49:04 2015 -0700 [mms] Don't honor linked attachment limit configuration options if linked attachments are disabled (Bug #13665). imp/docs/CHANGES \| 9 +++++++++ imp/lib/Compose.php \| 4 ++++ imp/package.xml \| 13 +++++++++++++ 3 files changed, 26 insertions(+), 0 deletions(-) http://github.com/horde/horde/commit/a701ad0e6dc8421b591ed4e0e441acb7818ed8ec

02/25/2015 03:50:17 AM	Michael Slusarz	Comment #4 State ⇒ Resolved Assigned to Michael Slusarz	Reply to this comment
You had disabled linked attachments but still had linked attachment limit options defined in conf.php. This has been fixed in IMP 6.2.8.

02/25/2015 03:49:17 AM	Git Commit	Comment #3	Reply to this comment
Changes have been made in Git (FRAMEWORK_5_2): commit fdf4a24c9befd5ce08e5a98c1562c142417c7b95 Author: Michael M Slusarz <slusarz@horde.org> Date: Tue Feb 24 20:49:04 2015 -0700 [mms] Don't honor linked attachment limit configuration options if linked attachments are disabled (Bug #13665). imp/docs/CHANGES \| 2 ++ imp/lib/Compose.php \| 4 ++++ imp/package.xml \| 4 ++-- 3 files changed, 8 insertions(+), 2 deletions(-) http://github.com/horde/horde/commit/fdf4a24c9befd5ce08e5a98c1562c142417c7b95

02/17/2015 02:54:00 PM	benedetto (dot) vassallo (at) unipa (dot) it	Comment #2	Reply to this comment
[Show Quoted Text - 21 lines][Hide Quoted Text] hi, i set the link_attach_size_hard and link_attach_threshold both to 8 megabytes. if i want to send a mail with 2 attachments (3 mb + 7 mb), i get this php error: Call to a member function setRaw() on a non-object imp/lib/Compose.php on line 2895 i tried to debug it, but i don't understand how to fix it. i think it has something to do with this commit: https://github.com/horde/horde/commit/b90417d8b4a8cfeef56c6efab385963123cdec5a $storage->forceLinked was removed from IMP_Compose_Attachment_Storage_VfsLinked and i think these lines should not change the vfspath, if the attachment is forced to be linked? if (filesize($filename) < intval($conf['compose']['link_attach_threshold'])) { $this->_vfspath = self::VFS_ATTACH_PATH; } thanks for your help. I have the same problem here in University of Palermo. Please let me know when this issue is solved. Best regards

11/05/2014 09:02:13 PM	Michael Slusarz	Comment #1	Reply to this comment
hi, i set the link_attach_size_hard and link_attach_threshold both to 8 megabytes. if i want to send a mail with 2 attachments (3 mb + 7 mb), i get this php error: Call to a member function setRaw() on a non-object imp/lib/Compose.php on line 2895 i tried to debug it, but i don't understand how to fix it. i think it has something to do with this commit: https://github.com/horde/horde/commit/b90417d8b4a8cfeef56c6efab385963123cdec5a $storage->forceLinked was removed from IMP_Compose_Attachment_Storage_VfsLinked and i think these lines should not change the vfspath, if the attachment is forced to be linked? if (filesize($filename) < intval($conf['compose']['link_attach_threshold'])) { $this->_vfspath = self::VFS_ATTACH_PATH; } thanks for your help.