Alan :
I've never seen the message, but I'm pretty sure I know the problem. The
list server has been configured to accept only the standard 64 character
ASCII character set. This ensures maximum portability among users of
different computer systems (and is pretty common on USENET and such). So,
any attempt at sending binary, HTML, MIME, or even just funny characters
(like the British pounds sterling symbol) through the list server results
in a (usually inaccurate) translation to the 64 character set.
I've never used Communicator 4.01, but there should be a selection
somewhere to indicate that the recipient can accept only plain text. All
automatic translations (to MIME, etc.) should be disabled, and best is
probably the 'warn me before sending' selection, if you have it.
If you can't find it, let me know & I'll try to find a copy of 4.01 so I
can give you more specifics.
I also note some funny characters after your signature, so it's possible
your signature file is the culprit. Try removing the Ctrl-Z at the end.
I posted this to the list, as it's not an uncommon problem.
Randall
On Monday, March 29, 1999 12:52 PM, Alan Myers [SMTP:reagntsj@ricochet.net]
wrote:
>
> Listers,
>
> Is anyone getting messages from me that include a server warning about
> "autoconverted character set, etc."? One lister dropped me a note about
> this and we've e-mailed back & forth directly with no problem. It seems
> to occur only when passing through the list server.
>
> Maybe someone a bit more technical about this stuff than me can tell me
> what I might check on my end, to see if I have something set wrong. I'm
> using Netscape Communicator 4.01, 128 bit encryption version. I pretty
> much left it set at the default settings. My internet connection is a
> bit unusual, being a radio modem for portable computers, but seems to be
> pretty standard in every other way.
>
> Feel free to drop me a line direct & keep free of unnecessary clutter!
> ;-)
>
> TIA
>
> Alan Myers
> San Jose, Calif.
> '62 TR4 CT17602L
> --
> MZ?
|