Quoting Nethub Online nethubonl...@gmail.com:
Michael M Slusarz slusarz at horde.org writes:
Quoting Nethub Online nethubonline at gmail.com:
I guess IMP recognize it as text because no Content-Description, is it a
bug or need to use other way to recognize the file type?
No.
Quoting Nethub Online nethubonl...@gmail.com:
Sample A (sending via old version of Horde (Horde Groupware Webmail Edition
1.2.9)
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary==_4odon3t0zmn
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3
Zitat von Nethub Online nethubonl...@gmail.com:
Hi all,
In imp/config/mime_drivers.php, there is a limit_inline_size for both
'plain' and 'html', according to its description above this limit, the user
will only be able to download the part., it generate a link to let user
download the part,
Quoting Jan Schneider j...@horde.org:
Zitat von Nethub Online nethubonl...@gmail.com:
Hi all,
In imp/config/mime_drivers.php, there is a limit_inline_size for both
'plain' and 'html', according to its description above this limit, the user
will only be able to download the part., it generate
Michael M Slusarz slusarz at horde.org writes:
Quoting Jan Schneider jan at horde.org:
I think it uses the file name provide by the message part headers.
More specifically, it uses the file name provided by first the
'filename' parameter of Content-Disposition, then the 'name'
