Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(wrong-type-argument wholenump nil) [mu4e bug] #2561

Closed
3 tasks done
ndw opened this issue Sep 28, 2023 · 3 comments
Closed
3 tasks done

(wrong-type-argument wholenump nil) [mu4e bug] #2561

ndw opened this issue Sep 28, 2023 · 3 comments
Labels
bug mu4e specific for mu4e

Comments

@ndw
Copy link

ndw commented Sep 28, 2023

Describe the bug

If I attempt to view the message included below, I get this stack trace:

Debugger entered--Lisp error: (wrong-type-argument wholenump nil)
  mail-decode-encoded-word-region(32 454)
  article-decode-encoded-words()
  run-hooks(gnus-article-decode-hook)
  mu4e--view-render-buffer((:path "/Users/ndw/Maildir/ExampleCorp/INBOX/cur/problem-mess..." :size 747 :changed (25877 38006 0) :date (25874 32443 0) :flags (seen) :from ((:email "you@example.org" :name "You")) :message-id "SOMETHINGELSEWASHERE.eurprd07.prod.outlook.com" :priority normal :subject "THIS IS THE PROBLEM MESSAGE" :to ((:email "me@example.org")) :maildir "/ExampleCorp/INBOX" :docid 207679 :meta (:path "0d7:z" :level 0 :date "n65127ebb" :data-tstamp (0 0 0) :root t :thread-subject t)))
  mu4e-view((:path "/Users/ndw/Maildir/ExampleCorp/INBOX/cur/problem-mess..." :size 747 :changed (25877 38006 0) :date (25874 32443 0) :flags (seen) :from ((:email "you@example.org" :name "You")) :message-id "SOMETHINGELSEWASHERE.eurprd07.prod.outlook.com" :priority normal :subject "THIS IS THE PROBLEM MESSAGE" :to ((:email "me@example.org")) :maildir "/ExampleCorp/INBOX" :docid 207679 :meta (:path "0d7:z" :level 0 :date "n65127ebb" :data-tstamp (0 0 0) :root t :thread-subject t)))
  mu4e~headers-view-handler((:path "/Users/ndw/Maildir/ExampleCorp/INBOX/cur/problem-mess..." :size 747 :changed (25877 38006 0) :date (25874 32443 0) :flags (seen) :from ((:email "you@example.org" :name "You")) :message-id "SOMETHINGELSEWASHERE.eurprd07.prod.outlook.com" :priority normal :subject "THIS IS THE PROBLEM MESSAGE" :to ((:email "me@example.org")) :maildir "/ExampleCorp/INBOX" :docid 207679 :meta (:path "0d7:z" :level 0 :date "n65127ebb" :data-tstamp (0 0 0) :root t :thread-subject t)))
  mu4e--server-filter(#<process  *mu4e-server*> "\37618b\377(:view (:path \"/Users/ndw/Maildir/ExampleCorp/IN...")

How to Reproduce

Put the message below into your Maildir and try to view it.

Environment

Emacs 29.1 on macOS Ventura.

Checklist

  • you are running either an 1.8.x/1.10.x release or master (otherwise please upgrade)
  • you can reproduce the problem without 3rd party extensions (including Doom/Evil, various extensions etc.)
  • you have read all of the above

Please make sure you all items in the checklist are set/met before filing the ticket. Thank you!

Here's the smallest message I could construct that reproduced the problem.

Return-Path: <you@example.org>
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=h8saLk8Cmxhn+nvprp0wReN0oICRSsmmMVpR/Xn3Ccd93md41DRmKc571vhbl+rDpeq1ACaeRUGH2OJg/uQywOOhPBcQfPju0foqoB7Ww05z7GauJXRC8Z9pII1EBEFoCHKg9cAoiI7LTb8Yfa9KWdC6J/ioOzS0F3g3VTm4Q4GLFeYWPQY9a8HzDP6RebF4K4ZkGrCwa3kSDgAAXEgP6r0R212IHSiXbzCXhlrPB17M8UJYT0yo+200lDhG7MLspwB2Y0pdFtf2PAIbI3y8qpR0YJiyHhTn+q6g80Z5QvDRUBH7Lgs9iBJAvhX3O/LSxnzlw/a0gKGWR7pu8mPViA==
From: You <you@example.org>
To: me@example.org
Subject: THIS IS THE PROBLEM MESSAGE
Date: Tue, 26 Sep 2023 06:48:27 +0000
Message-ID:
 <SOMETHINGELSEWASHERE.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="utf-7"
Content-Transfer-Encoding: quoted-printable

Some message goes here

The problem appears to be in the ARC-Seal header. I won't be surprised if you conclude that it's encoded incorrectly, but since we discussed it in email, I thought I'd complete the loop and open the report.

Thanks for your help!

@ndw ndw added bug mu4e specific for mu4e new labels Sep 28, 2023
@djcb
Copy link
Owner

djcb commented Oct 2, 2023

Thanks! I can reproduce. I have a fix (workaround) for the development branch, and I'll backport it to 10.x.

@djcb djcb removed the new label Oct 2, 2023
@djcb djcb closed this as completed in 4d11abd Oct 5, 2023
@eslgastal
Copy link

Hello @djcb . Was this fix backported to 1.10 ?

eslgastal pushed a commit to eslgastal/mu that referenced this issue Apr 17, 2024
We can't do much about them; still attempt to show the message.

Fixes djcb#2561.
@djcb
Copy link
Owner

djcb commented Apr 18, 2024

@eslgastal: I've just done so.

djcb added a commit that referenced this issue Apr 18, 2024
We can't do much about them; still attempt to show the message.

Fixes #2561.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug mu4e specific for mu4e
Projects
None yet
Development

No branches or pull requests

3 participants