Content-transfer-encoding setting in mutt
Felix Karpfen
emails adequately.
However, I have just received an email, that defeats mutt (vim can
handle it!). The relevant details are:
,----[ tfe.txt ]-
| Content-Type: text/plain; charset="iso-8859-1"
|
| Content-Transfer-Encoding: quoted-printable
| X-MIME-Autoconverted: from 8bit to quoted-printable by post.webmailer.de id
| +j9I9Omt6013509
|
`----
Can mutt be coaxed to come to the party?
Felix Karpfen
--
Felix Karpfen
Public Key 72FDF9DF (DH/DSA)
Alain Bench
On Thursday, October 20, 2005 at 6:21:42 AM +1000, Felix Karpfen wrote:
> I have just received an email, that defeats mutt (vim can handle it!).
How does this defeat look like?
Bye! Alain.
--
How To Ask Questions The Smart Way
<URL:http://www.catb.org/~esr/faqs/smart-questions.html>
g.mohan...@gmail.com
Iam new to this mutt
My problem is here we are having exchange server running we want
configure mail client in solaris wather this mutt and pine will work
and one more think i want to be clear it should be accessable in
command line pls any one help me very urgent i gone through the all the
douments in the net still iam unable if any one provide me step by step
notes it will really help full
pls..............
thnks
Felix Karpfen
(<slrndldfo2.k0...@M.oreka.invalid>):
> Hello Felix,
>
> On Thursday, October 20, 2005 at 6:21:42 AM +1000, Felix Karpfen wrote:
>
>> I have just received an email, that defeats mutt (vim can handle it!).
>
> How does this defeat look like?
If I knew how to copy and paste the mutt-display, I would. But my
copy attempts give a normal output i.e. they automatically switch the
"7bit, quoted-printable" back to the "8bit" in which the message was
written.
By the same token, simply pressing "Control-E" in mutt does not work
either. That (correctly) displays the "Content-Type" as "text/plain
charset=iso8859-1". But the actual message (in mutt) is littered with
ANSI escape codes.
The following sample may show something - although the problem is
somewhat different. The "Control-E' routine does not work on that
either'
,----[ g_mess2.txt ]-
| This is a multi-part message in MIME format.
|
| ------=_NextPart_000_003D_01C5D497.49714F40
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: quoted-printable
| Dear Mr. Karpfen,
|
| we will send you by mail the microwave cookbook of R=D6MERTOPF in =
| German. Hope it will assist you.
|
| Kind regards
| R=D6MERTOPF Keramik GmbH
|
|
| i.V. Dorothee Ackermann=20
| =20
| =20
| =20
| ---------------------------------------------------
| R=D6MERTOPF Keramik GmbH
`----
Alain Bench
> If I knew how to copy and paste the mutt-display, I would. But my copy
> attempts give a normal output i.e. they automatically switch the
> "7bit, quoted-printable" back to the "8bit" in which the message was
> written.
Try to describe precisely what you see, and where (I assume pager?).
Also from where, with what, and to where do you copy/paste so text gets
QP decoded?
> the actual message (in mutt) is littered with ANSI escape codes.
What do you call "ANSI escape codes"? Things like "=D6" and "=20"?
Or perhaps things like "\326"? Or like "^[[36;41m"?
> The following sample may show something - although the problem is
> somewhat different.
But you again didn't describe this different problem. If you can't
paste so we see the problem, try to put it in words. We can't guess what
you see anormal in Mutt. I can only confirm this displays OK here. Well,
not exactly: The line "Dear Mr. Karpfen," does not appear in Mutt,
unless I toggle weed.
BTW the way you copied us samples is unfortunately a little bit
useless and misleading, because of over-trimming of course, and also
because of insertion or deletion of some spaces and empty lines. Every
detail may be important: Copy [C] the first and second messages to a
temporary mailbox /tmp/mysterious.mbx, gzip it, and send it attached to
me personally. My Reply-To is valid.
Bye! Alain.
--
When you post a new message, beginning a new topic, use the "mail" or
"post" or "new message" functions.
When you reply or followup, use the "reply" or "followup" functions.
Do not do the one for the other, this breaks or hijacks threads.
Felix Karpfen
(<slrndlinnh....@othin.ninehells.com>):
>>> On Thursday, October 20, 2005 at 6:21:42 AM +1000, Felix Karpfen
>>> wrote:
>>>
>>>> I have just received an email, that defeats mutt (vim can handle
>>>> it!).
>> `----
>
> Show the rest of the message, especially the Content-type: header from
> the main message headers.
>
I sent the full message plus (what I thought to be) the relevant headers.
However, by pressing "v" on the displayed message, the following
additional information emerged:
,----[ headers.txt ]-
| I 1 <no description> [multipa/alternativ, 7bit, 2.5K] |
| I 2 \u251c\u2500><no description> [text/plain, quoted, iso-8859-1, 0.5K]
| I 3 \u2514\u2500><no description> [text/html, quoted, iso-8859-1, 1.6K]
|
`----
> This segment, when surrounded by an appropriately forged structure,
> renders correctly on my mutt 1.5.6i.
So the question that I _should_ have asked is:
What is the "appropriately forged structure"?
I thought that I was asking a simple question. Which <was|is>:
How do I persuade "mutt" to correctly display messages that include
characters which need 8 bits.
However, nothing is ever simple - as the mangling of the above copied
headers.txt shows. The mangled characters, presumably needing 8 bits,
were displayed correctly in "mutt", but got mangled during pasting into
"vim". And, to make a bad story worse, it appears that my 8-bit characters
- which display correctly in "vim", get mangled on the way to "mutt".
My current version of "mutt" was installed by Debian Sarge and is:
Mutt 1.5.6+20040907i (CVS)
For the record, the combination of "Pan newsreader + vim" does not have
this problem; neither does "Kmail + vim". The mailers in both
packages display "ö" as it was typed in vim. According to "mutt", the
typed character is "\366". All three programs are configured to use "vim"
as their editor.
Felix Karpfen
(<slrndlo6ve...@othin.ninehells.com>):
> On Mon, 24 Oct 2005 07:07:55 +1000, Felix Karpfen wrote:
>>
>> For the record, the combination of "Pan newsreader + vim" does not have
>> this problem; neither does "Kmail + vim". The mailers in both packages
>> display "ö" as it was typed in vim. According to "mutt", the typed
>> character is "\366". All three programs are configured to use "vim" as
>> their editor.
> That suggests to me that Mutt is likely rendering the character
> correctly in 8-bit and it IS _your pager_ rerendering that output in octal
> for the copy operation, as another poster suggested.
The problem is with the Pager.
But not due to _my_ .muttrc file.
Nothing changes if I replace that by the supplied "sample.muttrc-tlr"
file.
Furthermore, when I use Ximian Evolution 2.0 to view the contents of
my "mbox" file, _all_ the entries display correctly. From which I
deduce that my "mta" is doing what it should.
And the next step is...?
Alain Bench
> display "ö" as it was typed in vim. According to "mutt", the typed
> character is "\366".
Solution: Set your system locale correctly.
Both your German problem mails are well formed Latin-1 QP mails, one
straight text/plain, the other plain/html alternative. They're both
perfectly displayed.
- Your problem has nothing to do with Content-Transfer-Encoding.
- "\366" has nothing to do with an "ANSI escape code".
- Your strange copy/paste method has mangled your quotes.
For next times, you really should describe the symptoms from the
beginning, state straight facts, not your interpretation of facts, give
accurate context informations, and reply to questions people ask you.
Bye! Alain.
--
When you want to reply to a mailing list, please avoid doing so from a
digest. This often builds incorrect references and breaks threads.
Felix Karpfen
(<slrndlrj97...@othin.ninehells.com>):
> On Tue, 25 Oct 2005 15:38:02 +1000, Felix Karpfen wrote:
>>
>> The problem is with the Pager.
>
> :set ?pager
>
> if "builtin", use something else. If not builtin, make it so.
Use "something else" may be difficult. None of my pagers do any
better than "builtin".
Maybe the environment is unfriendly to 8-bit characters.
For the record, my current (relevant?) settings are:
LANG=en_GB
LANGUAGE=en_AU:en_US:en_GB:en
Felix
Felix Karpfen
(<slrndlulg1.37...@M.oreka.invalid>):
> On Monday, October 24, 2005 at 7:07:55 AM +1000, Felix Karpfen wrote:
>
>> display "ö" as it was typed in vim. According to "mutt", the typed
>> character is "\366".
>
> Solution: Set your system locale correctly.
Easier said than done.
The suggested default setting worked (for eight-bit characters) in
Debian Woody; it did not work in Debian Sarge. Finding an appropriate
setting for "Sarge" was a challenge.
"mutt" identified the existence of the problem - of which I had been
blissfully ignorant till I got some German mails.
Alain Bench
> The suggested default [locale] setting worked (for eight-bit
> characters) in Debian Woody; it did not work in Debian Sarge. Finding
> an appropriate setting for "Sarge" was a challenge.
Congratulations for the success! Note that the good locale setting
should normally be the same between Woody and Sarge: It depends more on
the terminal used than on the distribution version. Now perhaps one of
the Debians was misinstalled. I thought Sarge's Mutt was 1.5.9-2, not
your 1.5.6 CVS?
Bye! Alain.
--
Give your computer's unused idle processor cycles to a scientific goal:
The Folding@home project at <URL:http://folding.stanford.edu/>.
Scott Lurndal
>Okay, next question: what program is doing the copy/paste? We know it's
>not mutt, so it may be screen, or your terminal program or some magic
>abstraction even further out, or...?
If he's running a unix/linux/X11-based system, then the X server handles the
cut and paste via cut buffers internal to the X server - it is completely
independent of all applications; I use it with mutt all the time. The question
is how does the source application (from which the copy (left mouse button)
is grabbed) represent the characters (ISO-8859-1? UTF-8? ASCII?) and how does
the destination application (to which the paste (middle button) is targetted)
represent the characters. They must be the same, as X does no character
set translations during cut and paste operations.
scott