#54 v3.2.19, -base64 param : bad body text

[Adam Sova]

If I run these from powershell cmd (on v3.2.19), I get:

test1 ( body is OK, shows 1 )

.\blat.exe -body "1" -f me@my.com -to you@my.com -subject "test1" -html -ur -ss -noh2 -hdrencq -nomps -mime -8bitmime -try 3 -serverSMTP myserver -port 25 -charset UTF-8

test2 - with base64 param ( bad body, shows MQ== (I assume base64 encoded - it should encode only binary attachmet files, right? not body )

.\blat.exe -body "1" -f me@my.com -to you@my.com -subject "test2" -html -ur -ss -noh2 -hdrencq -nomps -mime -8bitmime -base64 -try 3 -serverSMTP myserver -port 25 -charset UTF-8

[Chip]

Blat is operating as intended, as verified with the very old version 1.9.4. Here is the background...

Under limited circumstances, some folks need(ed) to send binary files as the message body and not as attachments. Email is not typically configured to handle direct binary files as message bodies, since email is historically only seven bit and was originally built for US ASCII character set. The -base64 option was added to version 1.6 (date unknown) to allow sending binary files at a time before the program was capable of sending attachments. Version 1.9.4 continued that tradition of encoding the message body with base64 when using -base64 option, in order to be backward compatible with the earlier version and the needs of users trying to send binary files as the message body.

In today's world, use of -base64 is essentially unnecessary, except for a specific set of unknown users (who may no longer need this). I do not want to remove the -base64 option because I do not know if anyone actually needs this option.

Snippet from version 1.9.4 Readme.txt:

version 1.6
- Added support for mailing of binary files (mime base64 encoding)
which will make it possible to mail ANY file.

--
Chip

[Adam Sova]

Ok Cip, I didn't know that. I will just omit -base64 param then. Without it blat encodes attachments in base64 anyway so it's ok on my side here :)