Bug In MIME.EXE With NULL's?

[Robert Atkinson]

I'm trying to MIME encode a Comma Seperated file to be emailed to a user.

Some of the fields contain NULL characters, encased in quotes.

When MIME hits one of these, it truncates the record including the CRLF record terminator.

It this a bug?

Does anyone have a Perl script that I can use to search files for a NULL and send a warning?

Are there any other utilities available that can MIME encode a file?

Rob.

[Robert Atkinson]

I should add, I'm using the command 'MIME> ADD /TEXT' - perhaps this is why it's falling over the NULL?

Rob.

[Wim Van den Wyngaert]

Bob,

Just tried to mail a txt file with NULL, "NULL" and 'NULL' and it all arrived well (no trunc).

Mime 1.7 on VMS 7.3.

The file is ADDed without any options in mime.

Wim

[Wim Van den Wyngaert]

Same test with /text, same result.

Wim

[Volker Halle]

Rob,

confirmed with MIME V1.9 on OpenVMS Alpha V8.2. Maybe you need MIME> ADD/BIN file

Wim,

it's about a binary NULL character - can be created in TPU with Gold 0 Gold 3 (=SPECINS)

Volker.

[Robert Atkinson]

Can't use ADD/BIN, as it comes out as a stream style record (no CRLF record terminator).

Rob.

[Volker Halle]

Rob,

ADD

/BINARY

Sets Content-Type to "application/octet-stream" and
Content-Transfer-Encoding to "Base64". This format can
be used to represent an arbitrary binary data stream.

The binary NULL correctly arrives after an ADD/BIN and sending the created MIME mail file through VMSmail locally.

Volker.

[Wim Van den Wyngaert]

OK. Bad result on 1.7 too.
But this is what I expect of binary data.

Wim

[Robert Atkinson]

Is NULL really binary - it's part of the standard ASCII set?

Rob.

[Wim Van den Wyngaert]

All binary values are in the ascii set.

May be better to speek of printable.

Why not zip it first ?

Wim