From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] conversion of charsets in upas/fs
Date: Tue, 1 Feb 2005 11:29:32 +0100 [thread overview]
Message-ID: <58218e63961d40d19c91d9e10f0be666@voidness.de> (raw)
In-Reply-To: <87cb016c9bd81d2cce16b0219800bf01@voidness.de>
> The problem remained when I sent this test mail to the local smtp
> server But I found out, that all is fine when I move away my pipeto
> file.
>
> It seems as if /mail/lib/pipeto.lib introduces the problem somewhere.
> I hope to find it.
Ok, i took a mail, made by Russ' smtp dialogue script, and did
manually what pipeto.lib does with every mail.
% cd /mail/fs/mbox/124
% cat rawunix | sed '/^$/,$ s/^From / From /' > /tmp/msg
This file is already screwed. I compared to the original rawunix file
with xd:
term% diff <{xd -c rawunix} <{xd -c /tmp/msg}
21,23c21,23
< 0000140 a n u m l a u t : fc \n 04 04
< 0000150 \n
< 0000151
---
> 0000140 a n u m l a u t : c2 80 \n 04
> 0000150 04 \n
> 0000152
term%
0xfc represents 'ü' in iso-8859-15 but sed replaces it by 0xc2 and
0xc8. Why? It should only hide bogus 'From ' lines in the mail body.
Is sed allowed to replace 0xfc by something different here?
Heiko
next prev parent reply other threads:[~2005-02-01 10:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 13:57 Heiko Dudzus
2005-01-31 1:21 ` Kenji Okamoto
2005-01-31 14:05 ` Heiko Dudzus
2005-01-31 18:40 ` Russ Cox
2005-01-31 19:19 ` boyd, rounin
2005-02-01 8:24 ` Heiko Dudzus
2005-02-01 10:29 ` Heiko Dudzus [this message]
2005-02-01 17:11 ` Heiko Dudzus
2005-02-01 20:41 ` Sape Mullender
2005-02-01 20:45 ` boyd, rounin
2005-02-01 18:26 ` Russ Cox
2005-02-01 18:37 ` rog
2005-02-01 19:50 ` boyd, rounin
2005-02-02 10:59 ` Heiko Dudzus
2005-02-02 13:48 ` Russ Cox
2005-02-02 23:41 ` Heiko Dudzus
2005-02-01 1:42 ` Kenji Okamoto
2005-02-01 3:42 ` Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58218e63961d40d19c91d9e10f0be666@voidness.de \
--to=heiko.dudzus@gmx.de \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).