Am 2007-05-01 19:50 +0200 schrieb Alain Bench:
> Inline PGP encrypted mail written in Latin-9, and labelled Latin-9:
> Fine. But for Mutt, this is like the square root of a negative: It is
> not supposed to exist.
Yea, this is default enigmail setup I suppose, also this inlined pgp is
enabled
Hi Stefano,
On Tuesday, May 1, 2007 at 21:24:55 +0200, Stefano Sabatini wrote:
> "Part of this message has not been signed." message, and the "s" flag
> keeps downcased
Feature, introduced in Mutt 1.5.6 by Thomas. Previously, partially
signed messages were considered yet more suspiciously:
On date Wednesday 2007-05-02 00:25:47 +0200, Alain Bench muttered:
> Hi Stefano,
>
> On Tuesday, May 1, 2007 at 21:24:55 +0200, Stefano Sabatini wrote:
>
> > "Part of this message has not been signed." message, and the "s" flag
> > keeps downcased
>
> Feature, introduced in Mutt 1.5.6 by Th
Hi list,
I am getting a few messages with odd characters in it such as:
"won\264t" and "\250reply\250"
The first being an apostrophe and the second being quotes (the messages
view fine in squirrelmail).
I thought I had found a solution in the archives and added TRANSLIT as
follows:
set charset
Moin fellow mutters,
to help newbies reach their solutions faster, I've added the
following text to the welcome msg for subscribers. Please review and
report improvements, or even better edit the pages directly.
-- QUOTE BEGIN --
If you have any question related to mutt usage, then pleas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, May 3 at 08:10 AM, quoth Roland Hill:
>I thought I had found a solution in the archives and added TRANSLIT
>as
>follows:
>
>set charset="iso-8859-1//TRANSLIT"
>
>.but this hasn't fixed the problem.
>
>Can anyone offer a solution or p
On Wed, 02 May 2007 or thereabouts, Kyle Wheeler came forth with:
> On Thursday, May 3 at 08:10 AM, quoth Roland Hill:
> >I thought I had found a solution in the archives and added TRANSLIT
> >as
> >follows:
> >set charset="iso-8859-1//TRANSLIT"
> >.but this hasn't fixed the problem.
> >C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, May 3 at 09:04 AM, quoth Roland Hill:
>> On Thursday, May 3 at 08:10 AM, quoth Roland Hill:
>>> I thought I had found a solution in the archives and added TRANSLIT
>>> as
>>> follows:
>
>>> set charset="iso-8859-1//TRANSLIT"
>
>>>
On Wed, 02 May 2007 or thereabouts, Kyle Wheeler came forth with:
> What is the charset of the email you're looking at? It may be
> mislabelled (which you may be able to use charset_hook to fix).
Kyle,
I just checked 3 posts from the sender whose messages I am having the
display issues with.
T
On 03May2007 09:53, Roland Hill <[EMAIL PROTECTED]> wrote:
| On Wed, 02 May 2007 or thereabouts, Kyle Wheeler came forth with:
| > What is the charset of the email you're looking at? It may be
| > mislabelled (which you may be able to use charset_hook to fix).
|
| Kyle,
| I just checked 3 posts f
On Thu, 03 May 2007 or thereabouts, Cameron Simpson came forth with:
> | I just checked 3 posts from the sender whose messages I am having the
> | display issues with.
> | The mailer never changes, yet the charset has been:
> | us-ascii
> | utf-8
> | iso-8859-1
> | .with the later 2 giving d
11 matches
Mail list logo
