From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: Resending email in Gnus, figuring out charset
Date: Mon, 29 Oct 2018 22:38:56 +0100 [thread overview]
Message-ID: <871s88saa7.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87muqwsalr.fsf@tullinup.koldfront.dk>
Adam writes:
> Hm, no problem on _that_ message for me either. But I _do_ get the
> problem on this message, in an nnml:-group:
Ok, that one was broken in encoding. Let me try again:
== =
X-From-Line: imap Mon Oct 29 19:42:52 2018
Return-Path: <nobody@koldfront.dk>
X-Original-To: asjo
Delivered-To: asjo@virgil.koldfront.local
Received: by virgil.koldfront.dk (Postfix, from userid 65534)
id D06F4801C1A5C; Mon, 29 Oct 2018 19:36:28 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.11.0 virgil.koldfront.dk D06F4801C1A5C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=koldfront.dk;
s=mail; t=1540838188;
bh=WfvGOpyTtxwaOiJs88bePPtVIyRpvI5bQ0iBkXqesDk=;
h=Subject:To:Date:From:From;
b=HkDDxc7mpghKKTNijxksOQWYPo0E1JuQ9d83X4FalaMqWQheWC0THN8bpSf9K8a3k
tPjg2W0qUoAxSV0JtMzYSGbiLnhQTMx2Z+8beY1aC3jkbuAxKrXJKOcACO1tesioTG
SbmzB/Ohp6RD0Kz0F8j8BV4V25YoUH51qFkNufuQ9884RliLKy3ScjPyqXQvMqLSLO
G8G28pKa9en6dGlmyL2GsQ3n7xqDyiuKykYNaIOVExKRppGKwOF1BvGzRxwz03NjV0
jAIwUpicR4L1+xyWzkneZy11Og5x/G5rhfD5eUua1ADQmpRC0I8BcQYdf1A09L5SIj
quqBBXX9MWPmg==
Subject: Output from your job 210
To: asjo@koldfront.dk
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Gnus-Mail-Source: imap:mail.koldfront.dk:INBOX
Message-Id: <20181029183628.D06F4801C1A5C@virgil.koldfront.dk>
Date: Mon, 29 Oct 2018 19:36:28 +0100 (CET)
From: nobody@koldfront.dk (nobody)
Lines: 12
Xref: tullinup feedbase:211
2018-10-29 19:36:28 feedbase.blog.cfcs
1/3 Center for Cybersikkerhed indvier i dag nyt Cybersituationscenter (Abonnér på seneste nyheder fra FE) new article
2/3 Halvdelen af danskerne genbruger passwords (Abonnér på seneste nyheder fra FE) new article
3/3 Forsvarets Efterretningstjeneste på Kulturnat 2018 (Abonnér på seneste nyheder fra FE) new article
→ New: 3, updated: 0 (updates ignored: 0), crossposted: 0, seen: 0
Total - new: 3, updated: 0 (updates ignored: 0), crossposted: 0, seen: 0
== =
This one should be correct (inserted the file from disk).
Best regards,
Adam
--
"You shouldn't let poets lie to you." Adam Sjøgren
asjo@koldfront.dk
prev parent reply other threads:[~2018-10-29 21:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 19:19 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 ` Resending email in Gnus, figuring out charset [solved] Adam Sjøgren
2018-10-29 21:32 ` Resending email in Gnus, figuring out charset Adam Sjøgren
2018-10-29 21:38 ` Adam Sjøgren [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=871s88saa7.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).