I can try and explain why, but you'll probably just laugh.
Our mail hub, upon receipt of a message with the header:
| Content-Type: text/plain; charset=X-roman8
[apparently] decides it can't understand the charset, and
delivers the msg with:
| This message uses a character set that is not supported
| by the Internet Service. To view the original message
| content, open the attached message. If the text doesn't
| display correctly, save the attachment to disk, and then
| open it using a viewer that can display the original
| character set.<< message.txt >>
Where the message.txt attachment simply contains something like:
| Received: from xxxx.xxxx.com ([147.145.31.100]) by \
xxx-xxxxxx.xx.xxxxxx.com with SMTP \
(Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
| id FTKVB7R6; Sun, 7 Mar 1999 21:42:21 -0600
| Return-Path: <su...@yyyy.xx.xxxx.com>
| Received: from [nnn.nn.nnn.58] by xxxx.xxxx.com with ESMTP; \
Sun, 7 Mar 1999 19:45:49 -0800
| Received: (from user@localhost) by yyyy.xx.xxxx.com (8.7.1/8.7.1)
\
id VAA01772 for Some...@xxxx.com; Sun, 7 Mar 1999 21:46:38
-0600 (CST)
| Date: Sun, 7 Mar 1999 21:46:38 -0600 (CST)
| From: Some User <su...@yyyy.xx.xxxx.com>
| Message-Id: <1999030803...@yyyy.xx.xxxx.com>
| To: Some...@xxxx.com
| Subject: test
| MIME-Version: 1.0
| Content-Type: text/plain; charset=X-roman8
| Content-Transfer-Encoding: 7bit
|
| GRRRRRR...
|
This is driving me crazy...
Thanks,
-SteveR
That's a mail user agent problem (mutt, elm, pine, dmail)
>Where the message.txt attachment simply contains something like:
>
> | Received: from xxxx.xxxx.com ([147.145.31.100]) by \
> xxx-xxxxxx.xx.xxxxxx.com with SMTP \
> (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I think we located the problem here...
--
Ralf Hildebrandt http://www.stahl.bau.tu-bs.de/~hildeb (0)531/391-3366
Institute for Steel-Structures, Technic. Univers. of Braunschweig, Germany
"Those who do not understand UNIX are condemned to reinvent it -- badly."
-- Henry Spencer
> On Sun, 07 Mar 1999 22:18:04 -0600, Steve Ralston <Steve....@lsil.com> wrote:
> >Does anyone know if it's possible to configure mail(x)
> >on HP-UX (running sendmail) such that the header line:
> > | Content-Type: text/plain; charset=X-roman8
> >can be changed to:
> > | Content-Type: text/plain; charset=us-ascii
>
> That's a mail user agent problem (mutt, elm, pine, dmail)
And the original poster *is* asking about a MUA (mail[x]).
Probably you need to check your locale settings. You might
try explicitly including this header and hoping that mail(x)
doesn't replace it.
>
>
> >Where the message.txt attachment simply contains something like:
> >
> > | Received: from xxxx.xxxx.com ([147.145.31.100]) by \
> > xxx-xxxxxx.xx.xxxxxx.com with SMTP \
> > (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> I think we located the problem here...
Yep, I think you need to replace your mail hub software.
~frank
--
* I am Pentium of Borg. Division is futile. You will be approximated. *
* PGP ID: C001AA75 -|- fcu...@iconnet.net *
>> >Does anyone know if it's possible to configure mail(x)
Shit! I overlooked the (x) after mail -- normally users don't discern mail from sendmail!
>> > | Received: from xxxx.xxxx.com ([147.145.31.100]) by \
>> > xxx-xxxxxx.xx.xxxxxx.com with SMTP \
>> > (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> I think we located the problem here...
>
>Yep, I think you need to replace your mail hub software.
Reason: The MTA shouldn't meddle with the content of the mail!
Perhaps there's some magic config option in the Exchange Server
("Exchange Server" is what you should do :) ) that might fix this.
You're not saying whether you want this site-wide or just for
yourself. Either way, Procmail could be a solution (although more
general than you asked for ... it doesn't understand MIME at all but
it sure can manipulate headers). It's a general mail filter which
you'd run at delivery time on all your mail (for other reasons as
well) via your .forward file (or you could config Sendmail to use it
as your MDA).
Another program which might be able to do the actual rewriting, which
does understand MIME, is Emil (but I get the feeling nobody is using
it much anymore).
One could reasonably argue that whoever is sending messages encoded as
Roman-8 (especially if as a matter of fact the actual message is 7-bit
clean) is ultimately the biggest problem.
The following Procmail rule will attempt to fix messages only if there
is no 8-bit data in the message body:
:0fhw # The octal codes should be replaced with actual ASCII chars!
* ^Content-Type:\<*text/plain;\<*charset="?x-roman8"?
* B ?? ! [\200-\377]
| formail -I "Content-Type: text/plain; charset=us-ascii"
The first condition says Content-type:, optional whitespace,
text/plain;, optional whitespace, charset=x-roman8 (with the string
possibly being quoted). The second examines the body (B ??) and
verifies that no one line (!) contains a non-ASCII character ([...]).
As indicated in the comment, Procmail doesn't understand \nnn escapes,
so you'll have to (figure out how to) enter the non-ASCII characters
literally (or kludge your way; it's not that hard or expensive).
Hope this helps,
/* era */
Please set followups when posting to a large number of groups. I've
set them to comp.mail.misc (but I don't expect any followups on this).
--
* Sign the European spam petition! <http://www.politik-digital.de/spam/en/> *
.obBotBait: It shouldn't even matter whether <http://www.iki.fi/~era/>
I am a resident of the state of Washington. <http://members.xoom.com/procmail/>
>Does anyone know if it's possible to configure mail(x)
>on HP-UX (running sendmail) such that the header line:
> | Content-Type: text/plain; charset=X-roman8
>can be changed to:
> | Content-Type: text/plain; charset=us-ascii
>?
<snip>
Add :
set charset=us-ascii
to /usr/share/lib/mailx.rc
Makes it good for all outgoing mailx mail.