From: nospam@dev.null (Alexey Pustyntsev)
To: info-gnus-english@gnu.org
Subject: Re: unreadable message
Date: Fri, 03 Oct 2008 14:33:40 +1100 [thread overview]
Message-ID: <E1KlbQC-00019B-Oo@sycore.org> (raw)
In-Reply-To: <20081002160838.596DE9CE6D@sycore.org> (info-gnus-english-request@gnu.org's message of "Thu, 02 Oct 2008 12:01:40 -0400")
Hi Reiner!
> Are you saying it happened *during* composing a message, *before*
> sending it? If so, I have no idea why this might happen.
It happened immediately after the C-c C-c command was issued. I
didn't see anything strange during composing a message.
>
> But the excerpt below looks like an archived (outgoing) article:
Yes, it does. Considering accidental archiving to be a likely cause
of the weirdness, what do you think might have triggered it when my
default settings were unchanged (gnus-message-archive-group is nil)
and the other messages were OK? Typing a wrong command doesn't seem
to be probable.
> Using "Content-Transfer-Encoding: base64" (what you called
> "encrypted") happens when there are many 8bit characters
> (`mm-qp-or-base64'). There's nothing wrong with that.
<joke>
That's all very well, except that some Gnus users may accidentally
lose their lengthy 8-bit character messages, which are, of course,
extremely intelligent and valuable :)
</joke>
Is there a chance to restore the message if it was archived like that?
--
Rgds
Alexey
Today is Sweetmorn, the 57th day of Bureaucracy in the YOLD 3174
next parent reply other threads:[~2008-10-03 3:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081002160838.596DE9CE6D@sycore.org>
2008-10-03 3:33 ` Alexey Pustyntsev [this message]
[not found] <20081205170521.82FB8B3A9B@sycore.org>
2008-12-07 13:09 ` Alexey Pustyntsev
[not found] ` <mailman.2130.1228657054.26697.info-gnus-english@gnu.org>
2008-12-07 13:53 ` Adam Sjøgren
[not found] <20081122170614.43FA5AF4EA@sycore.org>
2008-12-03 12:52 ` Alexey Pustyntsev
[not found] <20081119120241.18DB3AE3A7@sycore.org>
[not found] ` <1682991423.20081121000628@mail.ru>
2008-12-03 9:12 ` Alexey Pustyntsev
[not found] <20081120170954.CEF57AEB9D@sycore.org>
2008-11-21 4:26 ` Alexey Pustyntsev
[not found] ` <87k5ah83de.fsf@marauder.physik.uni-ulm.de>
2008-12-04 19:53 ` Reiner Steib
[not found] ` <mailman.913.1227239500.26697.info-gnus-english@gnu.org>
2008-11-21 18:38 ` Adam Sjøgren
[not found] <20081118170628.3744BADFB1@sycore.org>
2008-11-19 3:41 ` Alexey Pustyntsev
[not found] <20081108164035.A7A80AA94F@sycore.org>
2008-11-08 19:22 ` Alexey Pustyntsev
[not found] ` <mailman.3140.1226170065.25473.info-gnus-english@gnu.org>
2008-11-17 19:29 ` Adam Sjøgren
[not found] <20081030170648.D58A5A7629@sycore.org>
2008-11-08 6:05 ` Alexey Pustyntsev
[not found] ` <mailman.3101.1226122268.25473.info-gnus-english@gnu.org>
2008-11-08 12:24 ` Adam Sjøgren
[not found] <20081003161005.9293E9D50B@sycore.org>
2008-10-29 4:02 ` Alexey Pustyntsev
[not found] ` <mailman.2329.1225250763.25473.info-gnus-english@gnu.org>
2008-10-29 19:58 ` Adam Sjøgren
2008-11-08 15:50 ` poppyer
[not found] <20080924160707.CC00B99F3C@sycore.org>
2008-10-01 6:54 ` Alexey Pustyntsev
2008-10-01 7:02 ` Alexey Pustyntsev
2008-10-01 17:47 ` Reiner Steib
2008-09-14 2:50 Alexey Pustyntsev
2008-09-23 19:26 ` Reiner Steib
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=E1KlbQC-00019B-Oo@sycore.org \
--to=nospam@dev.null \
--cc=info-gnus-english@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).