From mboxrd@z Thu Jan 1 00:00:00 1970 From: wmorgan-sup@masanjin.net (William Morgan) Date: Tue, 21 Apr 2009 06:28:41 -0700 Subject: [sup-talk] Saving status of merged threads with '#' on next branch In-Reply-To: <1239875483-sup-5697@snowstorm> References: <1239177702-sup-8165@snowstorm> <1239299963-sup-5933@entry> <1239810733-sup-5572@snowstorm> <1239816596-sup-2531@entry> <1239875483-sup-5697@snowstorm> Message-ID: <1240320083-sup-2514@entry> 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