Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: ding@gnus.org
Subject: Re: Attachments broken since some time
Date: Sun, 24 May 2020 09:26:37 +0200	[thread overview]
Message-ID: <877dx1iyj6.fsf@gnu.org> (raw)
In-Reply-To: <87pnatbzwk.fsf@mat.ucm.es> (Uwe Brauer's message of "Sun, 24 May 2020 08:38:51 +0200")

Uwe Brauer <oub@mat.ucm.es> writes:

>> for some time, running the current Emacs master and the Gnus version
>> coming with it, it seems that all attachments are broken for me.
>> Below is a message from emacs-devel with a png image attachment.  I
>> get a gnus button but only a box is displayed (see screenshot).
>
> I can confirm this. I am using, because of a problem with signed and
> encrypted smime message, GNU emacs master from august.
>
> The strange thing is that text files, such as tex or matlab files work
> fine, images, don't.

Well, in my case it was the result of a configuration I did myself
without actually knowing what the consequences where.  I've set for my
nnimap select methods

(add-to-list 'gnus-secondary-select-methods
  '(nnimap "Fastmail"
    (nnimap-address "imap.fastmail.com")
    (nnimap-fetch-partial-articles "\\(text\\|image\\)/")))
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

which means that Gnus won't download non-text and non-image parts.
However, the buttons will still be there, just the parts will be empty.
Before acting on them, you need to fetch the complete article using `A
C'.

In Emacs master, I enhanced that so that now the buttons read like

  [name --- type (not downloaded, A C to fetch.)]

for those parts.

Bye,
Tassilo


      reply	other threads:[~2020-05-24  7:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  7:39 Tassilo Horn
2020-05-15  8:32 ` Adam Sjøgren
2020-05-15  9:11 ` Andreas Schwab
2020-05-15  9:50   ` Tassilo Horn
2020-05-15 10:11     ` Robert Pluim
2020-05-15 14:14       ` Tassilo Horn
2020-05-24  6:38 ` Uwe Brauer
2020-05-24  7:26   ` Tassilo Horn [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877dx1iyj6.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).