On Wed, Aug 28, 2002 at 05:24:44PM +0200, Sven Guckes wrote:
> > That is why I think it would be much better to have manual charset
> > override for headers, just like the one we have for bodies.
> > IMHO, this functionality should be implemented in MUA.
>
> this would only work around the proble
On Wed, Aug 28, 2002 at 09:03:14AM -0700, Sam Peterson wrote:
> Try keeping your locale to en_US.ISO8859-1. I think, provided
> LC_CTYPE allows for 8-bits, you should be able to set $charset to
> something different from LC_CTYPE, without problems. At least, I'm
> able to do this with $charset=e
Sven Guckes said:
> * Baurjan Ismagulov <[EMAIL PROTECTED]> [2002-08-28 10:18]:
>> I've looked at procmail a while ago for body
>> translation, but couldn't find a working solution.
>>
>> 1. All three inboxes I use are IMAP; how can I use procmail with it? I
>>can define a macro that would do
It has come to my attention...
...that Baurjan Ismagulov said on Wednesday, Aug 28 2002:
> Example: let's take a message encoded in iso-8859-1 and containing the
> character 'รง' (LATIN SMALL LETTER C WITH CEDILLA, octal code 347). The
> following table outlines how the message is displayed with di
* Baurjan Ismagulov <[EMAIL PROTECTED]> [2002-08-28 10:18]:
> I've looked at procmail a while ago for body
> translation, but couldn't find a working solution.
>
> 1. All three inboxes I use are IMAP; how can I use procmail with it? I
>can define a macro that would do what I want, but how woul
On Tue, Aug 27, 2002 at 01:37:30PM -0700, Sam Peterson wrote:
> > I'm using 1.4. I think LC_CTYPE and charset are set correctly in both
> > cases. BTW, why does Mutt use both of these variables? I would find
> > logical if charset have overridden LC_CTYPE. I can't see the rationale
> > behind the
On Tue, Aug 27, 2002 at 01:37:30PM -0700, Sam Peterson wrote:
> > My console can display koi8-r. I receive a mail encoded in windows-1251
> > with an unquoted header. Mutt converts the body to koi8-r, and I can
> > read the contents. However, Mutt doesn't know the header charset, so it
> > is disp
On Tue, Aug 27, 2002 at 03:44:08PM -0500, Aaron Schrab wrote:
> > message, how can one have Mutt set To: and/or Cc: fields automatically
> > (Mail-Followup-To: contains both sender and list addresses)? "r" and "L"
> > set To: only.
>
> Let me guess, you're trying this with a message you sent?
Y
At 21:23 +0300 27 Aug 2002, Baurjan Ismagulov <[EMAIL PROTECTED]> wrote:
> message, how can one have Mutt set To: and/or Cc: fields automatically
> (Mail-Followup-To: contains both sender and list addresses)? "r" and "L"
> set To: only.
Let me guess, you're trying this with a message you sent?
It has come to my attention...
...that Baurjan Ismagulov said on Tuesday, Aug 27 2002:
> Hello,
Hi,
> I often receive messages with either unquoted 8-bit headers (in lines
> like From:, To:, Subject:, etc.) or, worse, with characters quoted and
> wrong charset specified.
My condolences. This s
On Tue, Aug 27, 2002 at 08:06:00PM +0300, Baurjan Ismagulov wrote:
> P.S. Please cc to me, I'm not subscribed.
> I have "lists mutt-users" and "set followup_to" in my .muttrc, but
> I can't see any Followup-To: lines in the mail sent.
Oops, turns out that Mutt sets Mail-Followup-To: upon sending,
Hello,
this has been discussed in the past, but I couldn't find an adequate
solution for my particular problem.
I often receive messages with either unquoted 8-bit headers (in lines
like From:, To:, Subject:, etc.) or, worse, with characters quoted and
wrong charset specified.
Example 1:
My co
12 matches
Mail list logo
