summaryrefslogtreecommitdiff
path: root/tests/samples/gpg-badsig.txt
diff options
context:
space:
mode:
authorKonstantin Ryabitsev <konstantin@linuxfoundation.org>2021-06-11 09:59:21 -0400
committerKonstantin Ryabitsev <konstantin@linuxfoundation.org>2021-06-11 09:59:21 -0400
commit0a1776fc9fdf8e03757f2ccc08f5267489472432 (patch)
treef7f4dd87d6781dcb99265b5a1dd4d9bc700679e0 /tests/samples/gpg-badsig.txt
parent723f4d79a6181b60f03f9573a394a85895f5cf03 (diff)
downloadb4-0a1776fc9fdf8e03757f2ccc08f5267489472432.tar.gz
Save mbox files with proper unixfrom
In order to avoid some of the more obscure charset encoding problems, we switched to using as_string() for generating messages before saving them in an mbox file. However, this uncovered a bug where the unixfrom was not actually generated and saved, despite as_bytes() and as_string() supposedly behaving identically. See: https://docs.python.org/3/library/email.message.html#email.message.EmailMessage.as_string This commit fixes the problem by properly setting the unixfrom and using the recommended (and hopefully less buggy) email.generator interface when saving mailboxes. Reported-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Diffstat (limited to 'tests/samples/gpg-badsig.txt')
0 files changed, 0 insertions, 0 deletions