Bug 870405 - Cannot send mail with large message body
Cannot send mail with large message body
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openchange (Show other bugs)
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Matthew Barnes
Desktop QE
: Patch
Depends On:
Blocks: 895654
  Show dependency treegraph
Reported: 2012-10-26 08:04 EDT by Milan Crha
Modified: 2013-02-21 05:20 EST (History)
4 users (show)

See Also:
Fixed In Version: openchange-1.0-3.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 05:20:48 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
openchange-1.0-writestream.patch (8.00 KB, patch)
2012-10-26 08:04 EDT, Milan Crha
no flags Details | Diff

  None (edit)
Description Milan Crha 2012-10-26 08:04:54 EDT
Created attachment 633813 [details]

This is a "clone" of the upstream bug report:

Since OpenChange 1.0 users are unable to send messages with large message body and/or attachments, the WriteStream function fails. There was a problem due to changes in samba4, which discovered little issues in OpenChange's exchange.idl definitions. More info tin the upstream bug and in the OpenChange's devel mailing list:

This bug is affection also users of evolution-mapi.

Fedora packages (17, 18 and master) contain the attached patch already.
Comment 3 RHEL Product and Program Management 2013-01-07 07:33:05 EST
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Comment 4 Milan Crha 2013-01-08 13:15:40 EST
I just built openchange-1.0-3.el6 with the patch included.
Comment 7 errata-xmlrpc 2013-02-21 05:20:48 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.