[Tickets #9783] Re: incorrect attachment size

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/9783
------------------------------------------------------------------------------
  Ticket             | 9783
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | incorrect attachment size
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-05-14 05:29) wrote:

> Can you say why? Doesn't this just change the results of method  
> calls, not signature, etc.?

No.  getSize() and getBytes() (or whatever they are called) in  
Horde_Mime_Part returns the size of the current state of the contents  
- regardless of whether it is base64 encoded or quoted-printable or  
binary or 7 bit or whatever.  We can't start returning approximate  
sizes from that function because that is simply broken behavior.

And the only place we know the current encoded state of the contents  
is internally inside Horde_Mime_Part.  So nothing can be worked around  
externally.  And can't extend Horde_Mime_Part in IMP to add this  
feature either.