0acb28645f
This change handles message parse errors by printing the error when the user tries to view the message. Specifically only handling unknown charset errors in this patch, but there are many types of invalid messages that can be handled in this way. aerc currently leaves certain messages in the msglist in the pending (spinner) state, and I'm unable to view or modify the message. aerc also only prints parse errors with message when they are initially loaded. This UX is a little better, because you can still see the header info about the message, and if you try to view it, you will see the specific error.
29 lines
822 B
Plaintext
29 lines
822 B
Plaintext
Subject: Confirmation Needed gUdVJQBhsd
|
|
Content-Type: multipart/mixed; boundary="Nextpart_1Q2YJhd197991794467076Pgfa"
|
|
To: <BORK@example.com>
|
|
From: ""REGISTRAR"" <zdglopi-1Q2YJhd-noReply@example.com>
|
|
|
|
--Nextpart_1Q2YJhd197991794467076Pgfa
|
|
Content-Type: multipart/parallel; boundary="sg54sd54g54sdg54"
|
|
|
|
--sg54sd54g54sdg54
|
|
Content-Type: multipart/alternative; boundary="54qgf54q546f46qsf46qsf"
|
|
|
|
--54qgf54q546f46qsf46qsf
|
|
Content-Type: text/plain; charset=utf-8
|
|
Content-Transfer-Encoding: Hexa
|
|
|
|
|
|
|
|
--54qgf54q546f46qsf46qsf
|
|
Content-Type: text/html; charset=utf-8
|
|
|
|
|
|
<CeNteR><a hRef="https://example.com-ap-southeast-example.com.com/example.com#qs=r-acacaeehdiebadgdhgghcaegckhabababaggacihaccajfbacccgaehhbkacb"><b><h2>Congratulations Netflix Customer!</h2></b></a><br>
|
|
<HeaD>
|
|
<ObJECT>
|
|
|
|
--Nextpart_1Q2YJhd197991794467076Pgfa--
|
|
|
|
|