Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #230399 > unrolled thread
| Started by | Nate Bargmann <n0nb@n0nb.us> |
|---|---|
| First post | 2021-01-07 03:50 +0100 |
| Last post | 2021-02-06 03:10 +0100 |
| Articles | 7 — 3 participants |
Back to article view | Back to linux.debian.user
neomutt on Bullseye not retaining multipart/alternative MIME on forward Nate Bargmann <n0nb@n0nb.us> - 2021-01-07 03:50 +0100
Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward David Wright <deblis@lionunicorn.co.uk> - 2021-01-07 18:10 +0100
Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward Nate Bargmann <n0nb@n0nb.us> - 2021-01-08 01:50 +0100
Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward Nate Bargmann <n0nb@n0nb.us> - 2021-01-08 01:50 +0100
Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward Nate Bargmann <n0nb@n0nb.us> - 2021-01-29 02:20 +0100
Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward darb <mlist@darb.xyz> - 2021-02-06 02:10 +0100
Re: neomutt on Bullseye not retaining multipart/alternative MIME on forward Nate Bargmann <n0nb@n0nb.us> - 2021-02-06 03:10 +0100
| From | Nate Bargmann <n0nb@n0nb.us> |
|---|---|
| Date | 2021-01-07 03:50 +0100 |
| Subject | neomutt on Bullseye not retaining multipart/alternative MIME on forward |
| Message-ID | <Butx8-ri-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi All.
Last month I upgraded this desktop from Buster to Bullseye. It was a
fresh installation since something went wrong on that particular day
with 'apt dist-upgrade'. Oh well.
Anyway, with the current neoumtt package whenever I forward an email
that is MIME encoded and has an HTML attachment wrapped in a
multipart/alternative MIME block, the HTML attachment is dropped. The
message I am forwarding is to a local hobbyist mailing list and I was
notified by one of the list members a few weeks back that he could not
open the HTML mail as usual and my investigation has revealed the
problem began with the newest version of neomutt. My ~/.mutt/muttrc is
unchanged since March 27, 2020 and this feature had worked without issue
for years until the upgrade to the neomutt version in Bullseye.
Here are the attachment views from the last message I forwarded prior to
the upgrade to Bullseye and the first one afterward.
This is the attachment view from my Sent folder of the forwarded message
as neomutt on Buster created the forwarded message:
I 1 <no description> [multipa/mixed, 7bit, 84K]
I 2 ├─><no description> [text/plain, quoted, us-ascii, 0.2K]
I 3 └─>The ARRL Letter for November 19, 2020 [message/rfc822, 7bit, 83K]
I 4 └─><no description> [multipa/alternativ, 7bit, 81K]
I 5 ├─><no description> [text/plain, quoted, iso-8859-1, 27K]
I 6 └─><no description> [text/html, quoted, utf-8, 53K]
I 7 signature.asc [applica/pgp-signat, 7bit, 0.6K]
This is the attachment view from my Inbox folder of the same message as
received on November 19:
I 1 <no description> [multipa/alternativ, 7bit, 81K]
I 2 ├─><no description> [text/plain, 7bit, iso-8859-1, 26K]
I 3 └─><no description> [text/html, quoted, utf-8, 54K]
Due to Thanksgiving in the USA, the next message was on December 3,
after upgrading to the version of neomutt in Bullseye. Here is the
attachment view from my Sent folder:
I 1 <no description> [multipa/mixed, 7bit, 31K]
I 2 ├─><no description> [text/plain, quoted, us-ascii, 0.2K]
I 3 └─>The ARRL Letter for December 3, 2020 [message/rfc822, 7bit, 30K]
I 4 └─><no description> [text/plain, quoted, utf-8, 27K]
I 5 signature.asc [applica/pgp-signat, 7bit, 0.6K]
Notice the "multipa/alternativ" and "text/html" are omitted.
Here is the attachment view from my Inbox folder for the same December 3
message which is identical to the November 19 messagei in terms of MIME
blocks:
I 1 <no description> [multipa/alternativ, 7bit, 82K]
I 2 ├─><no description> [text/plain, 7bit, iso-8859-1, 27K]
I 3 └─><no description> [text/html, quoted, utf-8, 54K]
I cannot discern a change in the received messages MIME blocks, so the
issue must reside with neomutt in my estimation.
I can "bounce" the message to one of my private accounts and the HTML
attachment is received just fine and can be viewed in Evolution. When I
try to bounce the message to the list it must get dumped by the mail
handling system along the line as it never even appears in the
moderation queue, so this isn't an option.
As for MIME handling in my muttrc I have:
set mime_forward="ask-no"
# unset mime_forward_decode
which are unchanged for years, and, yes, I do answer the question with
'y' when I want to forward with MIME attachments.
My scanning of the neomutt documentation hasn't revealed anything. I
thought I'd ask here before subscribing to their mailing list.
TIA
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
[toc] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2021-01-07 18:10 +0100 |
| Message-ID | <BuGXo-K1-9@gated-at.bofh.it> |
| In reply to | #230399 |
On Wed 06 Jan 2021 at 20:41:50 (-0600), Nate Bargmann wrote:
> Last month I upgraded this desktop from Buster to Bullseye. It was a
> fresh installation since something went wrong on that particular day
> with 'apt dist-upgrade'. Oh well.
>
> Anyway, with the current neoumtt package whenever I forward an email
> that is MIME encoded and has an HTML attachment wrapped in a
> multipart/alternative MIME block, the HTML attachment is dropped. The
> message I am forwarding is to a local hobbyist mailing list and I was
> notified by one of the list members a few weeks back that he could not
> open the HTML mail as usual and my investigation has revealed the
> problem began with the newest version of neomutt. My ~/.mutt/muttrc is
> unchanged since March 27, 2020 and this feature had worked without issue
> for years until the upgrade to the neomutt version in Bullseye.
>
> Here are the […]
[…]
> My scanning of the neomutt documentation hasn't revealed anything. I
> thought I'd ask here before subscribing to their mailing list.
I'm not a neomutt user. Looking at the changelog, the only hint
I see is:
2020-11-20 Richard Russon <rich@flatcap.org>
[…]
* Upstream
- Add $count_alternatives to count attachments inside alternatives
Might that have added a regression?
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | Nate Bargmann <n0nb@n0nb.us> |
|---|---|
| Date | 2021-01-08 01:50 +0100 |
| Message-ID | <BuO8x-3Tq-3@gated-at.bofh.it> |
| In reply to | #230430 |
[Multipart message — attachments visible in raw view] — view raw
My apologies as I neglected to say that I set the variable to 'yes' and restarted neomutt and forwarded the latest message and the HTML attachment was dropped as before with this version. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
[toc] | [prev] | [next] | [standalone]
| From | Nate Bargmann <n0nb@n0nb.us> |
|---|---|
| Date | 2021-01-08 01:50 +0100 |
| Message-ID | <BuO8x-3Tq-5@gated-at.bofh.it> |
| In reply to | #230430 |
[Multipart message — attachments visible in raw view] — view raw
Well, that looked promising, David. Thanks for catching that. It appears that the count_alternatives variable is intended for counting the attachments a message has and showing that number in the index view. Its documentation leads to: https://neomutt.org/guide/mimesupport.html#attachments which states nothing about forwarding but rather about counting the number of attachments inside a multipart/alternative MIME block to display the count. I suppose next I shall follow up with the neomutt mailing list. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
[toc] | [prev] | [next] | [standalone]
| From | Nate Bargmann <n0nb@n0nb.us> |
|---|---|
| Date | 2021-01-29 02:20 +0100 |
| Message-ID | <BCqC5-ur-3@gated-at.bofh.it> |
| In reply to | #230399 |
[Multipart message — attachments visible in raw view] — view raw
Well, yesterday I finally got around to filing a bug on the neomutt GitHub issue tracker: https://github.com/neomutt/neomutt/issues/2788 The developers quickly bisected to the bug and the fix has been applied: https://github.com/neomutt/neomutt/commit/396a61b106ea16a8ea528a86fff5e0ab141df2fc I then filed a wishlist Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981306 in the hopes that the fix can make it into Bullseye. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
[toc] | [prev] | [next] | [standalone]
| From | darb <mlist@darb.xyz> |
|---|---|
| Date | 2021-02-06 02:10 +0100 |
| Message-ID | <BFkgN-1HK-3@gated-at.bofh.it> |
| In reply to | #230399 |
On 06/01/21 08:41PM, Nate Bargmann wrote: >Last month I upgraded this desktop from Buster to Bullseye. It was a >fresh installation since something went wrong on that particular day >with 'apt dist-upgrade'. Oh well. > >Anyway, with the current neoumtt package whenever I forward an email >that is MIME encoded and has an HTML attachment wrapped in a >multipart/alternative MIME block, the HTML attachment is dropped. The >message I am forwarding is to a local hobbyist mailing list and I was >notified by one of the list members a few weeks back that he could not >open the HTML mail as usual and my investigation has revealed the >problem began with the newest version of neomutt. My ~/.mutt/muttrc is >unchanged since March 27, 2020 and this feature had worked without issue >for years until the upgrade to the neomutt version in Bullseye. For anyone following along this was fixed in the latest neomutt release 20210205 [1] [1] - https://github.com/neomutt/neomutt/releases/tag/20210205 -- darb <mlist@darb.xyz>
[toc] | [prev] | [next] | [standalone]
| From | Nate Bargmann <n0nb@n0nb.us> |
|---|---|
| Date | 2021-02-06 03:10 +0100 |
| Message-ID | <BFlcS-2f6-5@gated-at.bofh.it> |
| In reply to | #231429 |
[Multipart message — attachments visible in raw view] — view raw
* On 2021 05 Feb 19:02 -0600, darb wrote: > For anyone following along this was fixed in the latest neomutt release > 20210205 [1] I was going to follow up that version 20201127+dfsg.1-1 landed in my update for Bullseye today and the forwarding issue is fixed in this latest Debian version. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web