On 2007-09-19 08:26:04 +0200, Rocco Rutte wrote:
> * Kyle Wheeler [07-09-18 09:27:06 -0500] wrote:
>> There's also option 3) refuse to send the mail, and display an error
>> message. I prefer this option. I don't like the idea of mutt being a
>> potential source of bad email.
>
> With messages cr
Hi,
* Kyle Wheeler [07-09-18 09:27:06 -0500] wrote:
On Tuesday, September 18 at 09:03 AM, quoth Mutt:
On the other hand, the question is what to do when all charsets in
$send_charset fail and $charset does not match an officially assigned
charset name, like in your case.
The options are 1)
On 2007-09-18 09:30:14 -0500, Kyle Wheeler wrote:
> It just occurred to me... given that your $charset is UTF-8, what's the
> purpose of //TRANSLIT? All possible characters are displayable in UTF-8, so
> //TRANSLIT shouldn't actually be providing any benefit (that I'm aware of).
> Is there somet
On Sunday, September 16 at 01:30 PM, quoth Vincent Lefevre:
On 2007-09-14 10:29:34 -0500, Kyle Wheeler wrote:
On Friday, September 14 at 03:10 PM, quoth Mutt:
And Mutt has problems if the subject contains such a character too.
See the generated Subject header:
Subject: Re: [Mutt] #2956: =?UTF-
On Tuesday, September 18 at 09:03 AM, quoth Mutt:
On the other hand, the question is what to do when all charsets in
$send_charset fail and $charset does not match an officially
assigned charset name, like in your case.
The options are 1) go ahead with a charset possibly not supported on the
On 2007-09-18 11:02:59 +0200, Rocco Rutte wrote:
> On the other hand, the question is what to do when all charsets in
> $send_charset fail and $charset does not match an officially assigned
> charset name, like in your case.
>
> The options are 1) go ahead with a charset possibly not supported on
Hi,
* Vincent Lefevre [07-09-18 02:11:02 +0200] wrote:
On 2007-09-17 17:09:55 +0200, Rocco Rutte wrote:
* Kyle Wheeler [07-09-17 09:39:02 -0500] wrote:
If mutt is generating this, then something is wrong... perhaps mutt
should recognize and strip out //TRANSLIT strings?
Yes, but that's ano
On 2007-09-17 17:09:55 +0200, Rocco Rutte wrote:
> * Kyle Wheeler [07-09-17 09:39:02 -0500] wrote:
>> If mutt is generating this, then something is wrong... perhaps mutt
>> should recognize and strip out //TRANSLIT strings?
>
> Yes, but that's another issue (it already has a table of valid characte
[ could somebody please fix trac to not mangle folded subjects? :) ]
Hi,
* Kyle Wheeler [07-09-17 09:39:02 -0500] wrote:
On Monday, September 17 at 10:38 AM, quoth Vincent Lefevre:
On 2007-09-16 11:59:33 -0500, David Champion wrote:
Subject: Re: [Mutt] #2956: =?UTF-8//TRANSLIT?Q?Reci?=
On Monday, September 17 at 10:38 AM, quoth Vincent Lefevre:
On 2007-09-16 11:59:33 -0500, David Champion wrote:
Subject: Re: [Mutt] #2956: =?UTF-8//TRANSLIT?Q?Reci?=
=?UTF-8//TRANSLIT?Q?pient_address_broken_if_containing_?=
=?UTF-8//TRANSLIT?Q?=C5?= character (UTF-8 code: 0xc5 0x
On 2007-09-16 11:59:33 -0500, David Champion wrote:
> > >> Subject: Re: [Mutt] #2956: =?UTF-8//TRANSLIT?Q?Reci?=
> > >> =?UTF-8//TRANSLIT?Q?pient_address_broken_if_containing_?=
> > >> =?UTF-8//TRANSLIT?Q?=C5?= character (UTF-8 code: 0xc5 0xA0)
> >
> > I do not set $send_charset. M
> >> Subject: Re: [Mutt] #2956: =?UTF-8//TRANSLIT?Q?Reci?=
> >> =?UTF-8//TRANSLIT?Q?pient_address_broken_if_containing_?=
> >> =?UTF-8//TRANSLIT?Q?=C5?= character (UTF-8 code: 0xc5 0xA0)
>
> I do not set $send_charset. My $charset contains //TRANSLIT, but this
> one is correct.
I
On 2007-09-14 10:29:34 -0500, Kyle Wheeler wrote:
> On Friday, September 14 at 03:10 PM, quoth Mutt:
>> And Mutt has problems if the subject contains such a character too.
>> See the generated Subject header:
>>
>> Subject: Re: [Mutt] #2956: =?UTF-8//TRANSLIT?Q?Reci?=
>> =?UTF-8//TRANSLIT?Q
On Friday, September 14 at 03:10 PM, quoth Mutt:
And Mutt has problems if the subject contains such a character too.
See the generated Subject header:
Subject: Re: [Mutt] #2956: =?UTF-8//TRANSLIT?Q?Reci?=
=?UTF-8//TRANSLIT?Q?pient_address_broken_if_containing_?=
=?UTF-8//TRANSLIT
14 matches
Mail list logo
