From: "Adam Sjøgren" <asjo@koldfront.dk>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: Resending email in Gnus, figuring out charset [solved]
Date: Wed, 31 Oct 2018 22:11:08 +0100 [thread overview]
Message-ID: <877ehxddoz.fsf_-_@tullinup.koldfront.dk> (raw)
In-Reply-To: <875zxhlvco.fsf@tullinup.koldfront.dk>
I did some more testing and noticed that the email where resend (S D r)
didn't grok the encoding had Content-Transfer-Encoding and Content-Type
header, but no MIME-Version header.
After adding a MIME-Version: 1.0 header, I don't get prompted about
characted with unknown encoding!
Thanks for the feedback spurring me on, Andreas and Eli.
Best regards,
Adam
--
"Accept failure gracefully." Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2018-10-31 21:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 19:19 Resending email in Gnus, figuring out charset Adam Sjøgren
2018-10-29 21:15 ` Andreas Schwab
2018-10-29 21:21 ` Adam Sjøgren
2018-10-30 6:23 ` Eli Zaretskii
2018-10-31 18:51 ` Adam Sjøgren
2018-10-31 18:59 ` Andreas Schwab
2018-10-31 19:42 ` Adam Sjøgren
2018-10-31 19:15 ` Eli Zaretskii
2018-10-31 19:43 ` Adam Sjøgren
2018-10-31 20:10 ` Eli Zaretskii
2018-10-31 20:22 ` Adam Sjøgren
2018-10-31 21:11 ` Adam Sjøgren [this message]
2018-10-29 21:32 ` Adam Sjøgren
2018-10-29 21:38 ` Adam Sjøgren
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=877ehxddoz.fsf_-_@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).