On 2002-07-27 08:00, Rocco Rutte <[EMAIL PROTECTED]> wrote:
> There's no real solution for use on your side. Personally I
> use a mailfilter which corrects broken encodings but there's
> no mutt-only solution I know of.
Could you post your filters (or a link)? Thanks.
--
Luke
Hi,
* jennyw [02-07-27 13:52:23 +0200] wrote:
> I've been noticing I get some messages where the subject
> begins with =?US-ASCII?Q??=.
First of all, in this case the encoding is stupid since it
only wasts bandwidth. The default for use in headers is
us-ascii (us-ascii and ascii is no difference
Hi,
* jennyw [02-07-27 13:53:03 +0200] wrote:
> On Fri, Jul 26, 2002 at 11:37:46PM +0200, Michael Tatge wrote:
> > try setting rfc2047_parameters. And read section 6.3.189
> > of the manual.
> I tried this, but no dice.
Clear. It only affects encoding in MIME parameters which is
not allowed (bu
On 26 Jul 2002 20:41, jennyw wrote:
> of mutt. Also, how did you figure out the real name of the charsets?
> There's no way I would have guessed that US-ASCII was really CP1251.
Oh sorry, forgot about this part. us-ascii has nothing to do with
cp1251. But because in cp1251 the latin letters ar
On 26 Jul 2002 20:41, jennyw wrote:
> I also have /usr/share/i18n/charmaps/CP1251.gz. However, when I use your
> hooks, I still get the =?us-ascii ... I'm using Debian 3.0, by the way.
The snip from my .muttrc was thought as an example only, because cp1251
refers to cyrillic encoding and my lo
On Fri, 26 Jul 2002, jennyw wrote:
> I've been noticing I get some messages where the subject begins with
> =?US-ASCII?Q??=. I looked this up on google (took some time
> because a ton of things come up when you just look for the string) and
> finally found RFC 1342, which said that this was non-a
* jennyw <[EMAIL PROTECTED]> [2002-07-26 11:22 -0700]:
> I've been noticing I get some messages where the subject begins with
> =?US-ASCII?Q??=. I looked this up on google (took some time
Can you send us the whole string? =?US-ASCII?Q??=
Nicolas
On Fri, Jul 26, 2002 at 11:37:46PM +0200, Michael Tatge wrote:
> try setting rfc2047_parameters. And read section 6.3.189 of the manual.
I tried this, but no dice. By the way, RFC 2047 seems to refer to
attachments. I'm having trouble with the subject header, so maybe it
doesn't apply?
Thanks!
Velko,
I also have /usr/share/i18n/charmaps/CP1251.gz. However, when I use your
hooks, I still get the =?us-ascii ... I'm using Debian 3.0, by the way.
Do you know where I can read more about charsets? This is one of those
things where I can't tell if the system is misbehaving or if it's mutt
jennyw ([EMAIL PROTECTED]) muttered:
> I've been noticing I get some messages where the subject begins with
> =?US-ASCII?Q??=.
try setting rfc2047_parameters. And read section 6.3.189 of the manual.
HTH,
Michael
--
We are Pentium of Borg. Division is futile. You will be approximated.
(seen in
I've been noticing I get some messages where the subject begins with
=?US-ASCII?Q??=. I looked this up on google (took some time
because a ton of things come up when you just look for the string) and
finally found RFC 1342, which said that this was non-ascii text, and that
the character set is wha
On 26 Jul 2002 21:22, Velko Hristov wrote:
> But, sorry, I don't know what you have to do in order to get it work.
> Probably you should check if this encoding is installed on your system
> and if so - try setting charset=us-ascii in your .muttrc. Only guessing,
> anyway.
The charset information
12 matches
Mail list logo
