From e5b0725824ac9ccf218732238e4b3b525fa6ad46 Mon Sep 17 00:00:00 2001 From: Koni Marti Date: Wed, 21 Sep 2022 00:27:58 +0200 Subject: charset: handle unknown charsets more user-friendly Do not throw an error when the charset is unknown; the message entity can still be read, but log the error instead. Reported-by: falsifian Signed-off-by: Koni Marti Acked-by: Robin Jarry --- worker/mbox/worker.go | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'worker/mbox/worker.go') diff --git a/worker/mbox/worker.go b/worker/mbox/worker.go index 067147e0..c5c70821 100644 --- a/worker/mbox/worker.go +++ b/worker/mbox/worker.go @@ -15,7 +15,6 @@ import ( "git.sr.ht/~rjarry/aerc/worker/handlers" "git.sr.ht/~rjarry/aerc/worker/lib" "git.sr.ht/~rjarry/aerc/worker/types" - gomessage "github.com/emersion/go-message" ) func init() { @@ -179,7 +178,7 @@ func (w *mboxWorker) handleMessage(msg types.WorkerMessage) error { break } - fullMsg, err := gomessage.Read(contentReader) + fullMsg, err := lib.ReadMessage(contentReader) if err != nil { reterr = fmt.Errorf("could not read message: %w", err) break -- cgit