Bug#985464: Libpst converts filename to rfc2231 format in outputted .msg files: reported upstream

2021-03-19 Thread Stuart C. Naifeh
Tags: upstream Reported upstream.

Bug#985464: Libpst converts filename to rfc2231 format in outputted .msg files

2021-03-18 Thread Stuart C. Naifeh
upstream > > On Thu, 2021-03-18 at 12:05 -0400, Stuart C. Naifeh wrote: > >> I suggest encoding the filename to rfc2231 into a separate temporary >> buffer, rather than in place, so that the internal attachment >> structure maintains the original, utf-8 encoded file name

Bug#985464: Libpst converts filename to rfc2231 format in outputted .msg files

2021-03-18 Thread Stuart C. Naifeh
Package: readpst, libpst4 Version: 0.6.75 Tags: patch Source: libpst When extracting an email with attachments from a pst to .eml and .msg files, the PR_ATTACH_LONG_FILENAME property for the attachments in the .msg file is encoded as a UTF-8 string in rfc2231 format (i.e., it’s prefixed with

Bug#775111: logwatch: unmatched entries from apparmor (lines without partent=...)

2015-01-11 Thread Stuart C. Naifeh
Package: logwatch Version: 7.4.1-2 Severity: normal Tags: patch Dear Maintainer, I am getting a number of unmatched entries in logwatch related to apparmor. Specifically, the are entries where apparmor is allowing access (apparmor=ALLOWED) and there is no parent=... in the log entry. The