Hello!

When I open this email,

  https://issues.guix.gnu.org/issue/58454/raw/2

which can be downloaded in mbox format from this address,

  https://debbugs.gnu.org/cgi/bugreport.cgi?mbox=yes;msg=11;bug=58454 

aerc panics with the following backtrace,

  https://paste.sr.ht/~unmatched-paren/b7f9138af8e43503916c54f72697c544b58d7bcb

    -- (

On Wed Oct 12, 2022 at 9:39 AM CEST, ( wrote:
> which can be downloaded in mbox format from this address,
>
>   https://debbugs.gnu.org/cgi/bugreport.cgi?mbox=yes;msg=11;bug=58454 
>
> aerc panics with the following backtrace,
>
>   https://paste.sr.ht/~unmatched-paren/b7f9138af8e43503916c54f72697c544b58d7bcb
>

Hi, thanks for reporting this!

As the panic report indicates the message part is not properly encoded
as "quoted-printable" as defined in RFC 2045. There are two instances
where the byte 0x0c is not properly escaped as "=0C" (0x0c stands for
the form feed control character). If those lines are removed, it works
fine.

Aerc relies on the go-message package to read messages which itself
relies on the Golang stdlib package "mime/quotedprintable" package to
decode the quoted-printable data. And that's where the reported error in
the panic is from:
https://cs.opensource.google/go/go/+/refs/tags/go1.19.2:src/mime/quotedprintable/reader.go;l=131

Throwing a panic is probably not the best way to handle this error and I
can try to propose a user-friendlier approach.