Operating System - OpenVMS
1753701 Members
4886 Online
108799 Solutions
New Discussion юеВ

Re: Bug In MIME.EXE With NULL's?

 
SOLVED
Go to solution
Joseph Huber_1
Honored Contributor
Solution

Re: Bug In MIME.EXE With NULL's?

If a file may contain "unprintable" characters,
then use Quoted-Printable encoding (why else do You want MIME encode ?):

MIME> add/text/encode=Quoted file

or add a line for the file-extension in
SYS$COMMON:[SYSMGR]MIME$FILETYPES.DAT
specifying
thistyp, text/plain, Quoted-Printable

so that a simple ADD does it for *.thistyp .
http://www.mpp.mpg.de/~huber
Joseph Huber_1
Honored Contributor

Re: Bug In MIME.EXE With NULL's?

is NULL binary ?

Every thing in memory (or a file) is binary.
The question here is, TEXT in mail should be
ASCII codes 32-126 only, everything else should be quoted.
http://www.mpp.mpg.de/~huber
Wim Van den Wyngaert
Honored Contributor

Re: Bug In MIME.EXE With NULL's?

Nice Joseph. It works on 1.7.

WIm
Wim
Wim Van den Wyngaert
Honored Contributor

Re: Bug In MIME.EXE With NULL's?

MIME$FILETYPES.DAT must be modified after each upgrade ! I would go for the /enc.

Wim
Wim
Robert Atkinson
Respected Contributor

Re: Bug In MIME.EXE With NULL's?

Joseph, likewise, that works perfectly here too.

Many thanks for your help.

Rob.
Joseph Huber_1
Honored Contributor

Re: Bug In MIME.EXE With NULL's?

Wim, are You sure ?
Even if it is replaced by VMS upgrades, don't You have, as a system manager, a separate directory, where all the customized files live ? :-)

http://www.mpp.mpg.de/~huber
Wim Van den Wyngaert
Honored Contributor

Re: Bug In MIME.EXE With NULL's?

It's documented. They say that the file is only replaced when it is modified by HP. Otherwise the file is not in the upgrade kit. So you must re-apply the change (or the next system manager will post the same question over here).

Wim
Wim
Wim Van den Wyngaert
Honored Contributor

Re: Bug In MIME.EXE With NULL's?