From: Sven Schober <sven.schober@uni-ulm.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Messages not displayed correctly
Date: Mon, 21 Jun 2010 11:12:56 +0200 [thread overview]
Message-ID: <1277110729-sup-6070@hysbald> (raw)
Hi Folks!
Two things:
1) Since some time (can't remember exactly since when, but it might
coincide with updating my index) a lot of messages don't get
displayed correctly any more. Instead, only the first line of the
message is displayed and then this notice:
***********************************************************************
An error occurred while loading this message.
***********************************************************************
I'm using commit 4e1e5c11fab83179ce611cc90d0b180c574eb3e0 on branch `next'.
The system log only shows:
[2010-06-21 11:02:47 +0200] WARNING: problem reading message AANLkTil-2QHApClKbIW7zMMYZ1mcjH6HmAxknYWYraNq@mail.gmail.com
for each message. Any ideas?
2) Is there any support in sup for s/mime-encryption using
certificates? I suspect not, but wanted to be sure before starting
to hack some `openssl smime' adapter, or something...
Ciao,
Sven
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
reply other threads:[~2010-06-21 9:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1277110729-sup-6070@hysbald \
--to=sven.schober@uni-ulm.de \
--cc=sup-talk@rubyforge.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