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.

Description of problem:
logwatch.pl base64 encodes multiple segments and concatenates the encoded parts instead of concatenating the segments and then encoding a single text block.  This creates imbedded "end" equal signs in the mime block which causes decode errors.

Version-Release number of selected component (if applicable):
7.4

How reproducible:
Any time any segment but the last has a length not divisible by three and encode = base64 was specified in the logwatch.conf file.

Steps to Reproduce:
1. specify encode = base64 in logwatch.conf
2. 
3.

Actual results:
invalid mime block in email.

Expected results:
valid mime block in email.

Additional info:

How can I actually reproduce this? Making some parts not divisible by 3 before encoding them still produces valid output.

Created attachment 1137033 [details]
naive fix

The naive fix works for me.  Without the fix I get invalid email, with the fix I get valid email.  Not knowing perl it is difficult for me to provide a test case.

https://sourceforge.net/p/logwatch/mailman/message/34952138/

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Created attachment 1333603 [details]
reproducer

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.

https://access.redhat.com/errata/RHBA-2018:0822