From: bm@bjornmichelsen.com (Bjorn Michelsen)
Subject: [sup-talk] Saving status of merged threads with '#' on next branch
Date: Thu, 16 Apr 2009 11:53:31 +0200 [thread overview]
Message-ID: <1239875483-sup-5697@snowstorm> (raw)
In-Reply-To: <1239816596-sup-2531@entry>
Excerpts from William Morgan's message of on. april 15 19:33:24 +0200 2009:
> > I haven't replied earlier because I've been trying to figure out what
> > causes the strange From: address.
>
> Is the weird encoding also present in the files in ~/.sup/sent.mbox? If
> so, it's could be Rubymail... AFAICT, Rubymail doesn't do anything with
> rfc2047, but I could have missed it.
No, everything is encoded correctly in ~/.sup/sent.mbox
> If not, are you using some funky sendmail?
I'm using sSMTP at the moment. Maybe it has something to do with the
following bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341952#10 ?
--
Mvh.
Bj?rn Michelsen
MOB: +47 934 55 474
next prev parent reply other threads:[~2009-04-16 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 20:44 =?UNKNOWN?Q?Bj=C3=B8rn?= Michelsen
2009-04-09 15:39 ` Mark Alexander
2009-04-09 18:02 ` William Morgan
2009-04-15 15:58 ` Bjorn Michelsen
2009-04-15 17:33 ` William Morgan
2009-04-16 9:53 ` Bjorn Michelsen [this message]
2009-04-21 13:28 ` William Morgan
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=1239875483-sup-5697@snowstorm \
--to=bm@bjornmichelsen.com \
/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