Tamas Rudnai wrote :

> Most e-mail client uses some encodings to get around so they
> encode it when sending and decode it when receiving and
> because it is a standard all e-mail client will handle it.

In *this* case both sender and reveiver are batch jobs
running on OpenVMS ("VMS", "VAX/VMS", whatever) systems.

There are no such thing as a "standard e-mail client" here. The
content is generated as a plain textfile and sent using a
mail-command from the batch script.

> Or you can use those encodings  (quoted-printable or
> Base64 or uuencode for example). These work pretty well
> in all MTAs and clients.

Yes, tool used is basicly a Base64 encode/decode tool.
And since I changed the line lenght from 80 to 70, it
all works mutch better now.

Anyway, my point was that 80 char lines *do* get mangled
by smtp servers sometimes.

This system handles several 1000's of mails a day and
works just fine otherwise.

Jan-Erik.



-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist