From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Saving status of merged threads with '#' on next branch
Date: Tue, 21 Apr 2009 06:28:41 -0700 [thread overview]
Message-ID: <1240320083-sup-2514@entry> (raw)
In-Reply-To: <1239875483-sup-5697@snowstorm>
Reformatted excerpts from Bjorn Michelsen's message of 2009-04-16:
> No, everything is encoded correctly in ~/.sup/sent.mbox
Then this is almost definitely your MTA, not Sup. But you could also try
sending a message to yourself with another MUA and see what happens.
(Probably what will happen is that the MUA will RFC2047-encode your
headers, and sSMTP will see that and leave them alone, and this problem
will be hidden. So the right answer is really for Sup to RFC2047-encode
headers in outgoing email.)
> 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 ?
The problem could be someone trying to fix that bug (which is basically
"we should add RFC2047 support"). Somehow it's not picking up your
locale settings.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-04-21 13:28 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
2009-04-21 13:28 ` William Morgan [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=1240320083-sup-2514@entry \
--to=wmorgan-sup@masanjin.net \
/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