Chip

I can look into this. I see this can lead to problems for some use cases, where the raw text to be sent does not actually have the header lines that Blat is being told to not add. Might it be better if Blat tried to identify those header lines to be suppressed within the raw message body, and remove them if found, thus allowing Blat to build its header lines normally? Chip

With the above stunnel configuration, I would tell Blat to connect to 127.0.0.1:27, where the semicolon (:) separates the IP address from the port number. Stunnel is configured to listen to port 27, and when a connection request is received from Blat on that port, it will establish an encrypted session with Gmail, allowing Blat to be none-the-wiser while sending your emails.

The issue is that you are trying to connect to Google through an encrypted session port. How I have been able to get this done is to use stunnel to provide that encrypted session support. I was going to post a link to message threads that discuss this very topic, but I am not finding them just yet. Essentially, you would need to tell Gmail to allow less secure applications to access your account (there is a setting for this), and then install the free tool called stunnel. With this done, you point...

When using -mime and using 8-bit encoding, your umlaut character can be send as-is. When using -mime, but using 7-bit encoding, your umlaut should be encoded. If your SMTP server allows 8-bit mime encoding, then Blat will use that. Changing the mime function to always encode values greater than 0x7F is easy, I just need to disable one line in an "if" condition. As a quick test, if you use -charset utf-7, this should give you want you want. Please give this a try. Chip

I actually use smtp4dev for testing my output before going live. This creates both a .txt file for the session, and .eml file of what it receives. I have two versions of this program -- v2.1.1.0 and v3.1. The earlier version is simpler to use and locate the output. The newer version supports SMTPUTF8, but it does not support creating files the way the older version does. The newer version stores the received emails to a SQLite database. This makes it less useful for my purposes than the older ve...

When last I checked, OAuth requires HTTPS support, which brings in a whole other area of problems. Adding https support necessitates openssl for SSL/TLS support, security certificates, and more. Plus, this moves the needle away from providing SMTP services to only supporting HTML services where Google can more easily inject advertisements and tracking (etc.). HTML is not conducive for simple e-mail transport.

I just ran Blat v3.2.24 three times. The first time was without the -log option. The second time was with -log, but no filename. The third time was -log "" (empty string). Here are my results: F:\BLAT\BLAT3224>x64\Release\blat.exe - -body "1" -base64 -u me -pw me -to myself -s "testing base64 on message body" -p smtp4dev Blat v3.2.24 (build : Feb 9 2022 21:19:39) 64-bit Windows, Full, Unicode Sending stdin.txt to me@localhost Subject: testing base64 on message body Login name is me@localhost F:\BLAT\BLAT3224>x64\Release\blat.exe...

None that I am aware of. Blat.dll should be self contained. Are you having troubles getting it to run?