Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1826702[details]
attachment test files
Created attachment 1826702[details]
attachment test files
### Background:
We're running bunch of AIX systems and we have shell scripts generating some reporting CSV files (semi-colon delimited lists). Then we're using uuencode + mailx to send these reports to our sysadmins.
Our mail-server is MS Exchange on Azure/Office365 so some of us are using Microsoft OWA webUI and some are using Evolution-EWS clients.
### Issue description:
If the attached file is downloaded via Evolution it gets corrupted. It contains a bunch of garbage characters and can not be used. It is NOT an issue of the Libre-Office. Even if the file is opened via text-editor/vim/less it still has wrong content.
BUT if the SAME attachment of the SAME email is download via OWA it is perfectly fine and contains the expected content.
Meaning the source of the issue seems to be with Evolution itself (and not with uuencode/mailx or mailserver)
I am attaching three files:
- TEST_39_2021-09-27_int_SRC.csv - Is the test-generated file downloaded from one of the hosts (so NOT processed by uuencode/mailx)
- TEST_39_2021-09-27_int_OWA.csv - Is the file downloaded from the reporting mail via OWA - content is OK
- TEST_39_2021-09-27_int_EVO.csv - Is the file downloaded via Evolution client and which is "broken"
### Environment:
- OS: RHEL 8.4 (4.18.0-305.12.1.el8_4.x86_64)
- Desktop: KDE Plasma 5.18.4
- Qt ver: 5.12.5
- Evolution:
- evolution-3.28.5-16.el8.x86_64
- evolution-langpacks-3.28.5-16.el8.noarch
- evolution-ews-3.28.5-10.el8.x86_64
- evolution-ews-langpacks-3.28.5-10.el8.noarch
- evolution-data-server-3.28.5-15.el8.x86_64
- evolution-data-server-langpacks-3.28.5-15.el8.noarch
- evolution-mapi-3.28.3-3.el8.x86_64
- evolution-mapi-langpacks-3.28.3-3.el8.noarch
- evolution-help-3.28.5-16.el8.noarch
Reported to Gnome Gitlab as well but closed as the "version is too old". Could we get the Evolution bumped in the RHEL 8.4 repos please?
Update: Reopened as the report is still valid even for recent 3.42.0
Alex
From the upstream investigation, the attachment is not corrupted, it's only not decoded. The reason is that the:
Content-Transfer-Encoding: uuencode
is invalid according to the RFC 2045, it should be prefixed with "x-", thus:
Content-Transfer-Encoding: x-uuencode
With that change the Evolution decodes the attachment content.
I asked it upstream, but no answer there yet, thus I'll ask here as well:
Who does fill the Content-Transfer-Encoding header, please? Is it your script or the mailx? If your script, then you should fix it to follow the standards.
Created attachment 1827726[details]
reproducer
The attachment is a reproducer, just import it to Evolution and check its content in the message preview.
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 (evolution-data-server bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:1782