Tickets :: Comment on [#1947] Attachments limitations only work when between IMP's attach_size_limit and PHP's post_max

* Your Email Address
* Spam protection	Enter the letters below: . ,.__..__.. ..__ \./ [__]\| \|\| \|[ __ \| \| \|\|__\|\|__\|[_./
Comment	> We have limited the IMP attachment size with > $conf['compose']['attach_size_limit'], and we've set a slightly > larger size limit in php's post_max_size. When a user attempts to > attach a file that's between the two sizes, IMP produces the expected > message saying that it can not attach the file because it's too big. > If the user tries to attach a file larger than post_max_size, though, > php produces an error, but IMP does not detect that the attachment > size is too large and warn the user. Instead, the compose screen is > wiped and returned to its virgin state. > > > > I suspect that this happens because horde is using the superglobal > arrays $_POST and $_FILES to maintain email state. See > http://www.php.net/manual/en/ini.core.php#ini.post-max-size > > > > The only workaround from a configuration perspective is to make > post_max_size ludicrously large so that a user could never attempt to > attach a file that big. Unfortunately, this means that other PHP > applications can also take advantage of that size limit. > > > > Perferably imp/horde would warn the user and keep state any time the > attachment size exceeded attach_size_limit, not just when it's > between attach_size_limit and post_max_size.
Attachment
Watch this ticket