Application: LWBlat GUI
Category: Utilities
Description: A portable GUI front-end for (the also portable) Blat (a console utility e-mail sender).
Download [1.03MB download / 1.84MB installed]
(MD5: e44e99fdbbc91bb7b405aae05d13ab9e)
Release Notes:
Development 1.4.3 Test 15 (2024-11-09)
- Added on-screen status indicator
- Made sent/failed popup message automatically close after a few seconds due to the new status indicator
- Fixed automated Shutdown to consider the chosen seconds and only work after successful sending
Development 1.4.2 Test 14 (2024-10-10)
- Fixed simulator height to match new simulator
Development 1.4.1 Test 13 (2024-10-10)
- Renamed remote file to match its new name
- Automated version and date
Development 1.4.0 Test 12 (2023-05-07)
- Added simulator mode for those without private SMTP servers (as modern public ones require SSL and OAuth which Blat doesn't support), so that various settings can be tested to see how a message would have been received had it used those settings
Development 1.3.5 Test 11 (2021-12-16)
- Small internal upgrades
Development 1.3.4 Test 10 (2020-08-22)
- Small internal upgrades
Development 1.3.3 Test 9 (2018-05-25)
- Updated both the launched program and the PortableApps Application Template
- Moved to PortableApps.com Format Specification (3.5)
Development 1.3.3 Test 8 (2017-05-26)
- Support by default for Blat being used in a subfolder
Development 1.3.3 Test 7 (2017-05-24)
- Internal enhancements
Development 1.3.3 Test 6 (2014-07-19)
- Updated both the launched program and the launched GUI front-end, and also upgraded the Portable Installer and Launcher
Development 1.3.2 Test 5 (2013-06-08)
- Updated both the launched program and the launched GUI front-end
Development 1.3.1 Test 4 (2010-02-09)
- Updated the program (GUI front-end) itself
Development 1.3 Test 3 (2010-01-26)
- Prepared help.html
Development 1.3 Test 2 (2010-01-13)
- Updated the program (GUI) itself
- Reverted to HKCU
Development 1.2 Test 1 (2010-01-10)
- Initial release
- Migrating INI settings (while not modifying them as the GUI uses relative folders)
- Migrating Blat's own registry settings (if used)
- Uses HLKM (in end cases) - will revert to HKCU it in the next release
- 64-bit version not included
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
It seems fully working for me.
Good luck with the next release
Release Team Member
[<li> tags need to come inside a <ul> tag - mod Chris]
Anyone at all.
Anyone willing to test?
I've known about Blat for a long time but never tried it until this
week after building a custom MinGW version of Lynx and needing a
mailer.
Didn't know about LWBlat 'til today.
Quick test and it worked fine. A simple mail was sent and received.
The GUI is chock full of options which is nice.
I'll be keeping this one around as it's nice to not bring up
a full-fledged email program just to send out a quick note.
I'll do more testing later, trying out each of the options.
Nice work.
You're welcome to use the new version to finish your testing.
The naming scheme for portableapp format is confusing as the direct link for the format points to LWBlatGUIPortable_0.2.4_English.paf, which installs version 1.3.1
I don't see why it doesn't follow same scheme, as in LWBlatGUIPortable_1.3.1, just my opinion.
"Development Test X"s are supposed to start from 1.
I wanted the installer's version to match the tests, regardless of the actual program's version.
Am I wrong about this?
No I don't think there's anything wrong about it IMO. Once testing is done and the installer is ready for release you can feel free to match the installer with the program's version.
Right now it's not something I feel is an issue.
For starters dev test number is supposed to reset to 1 each time you update the base app, and should only ever increment by whole numbers.
Also having the app version in the installer's filename will tell your users exactly what they are installing. Using some iteration of the package version doesn't mean much to end users.
Thus we use the format AppNamePortable_AppVersion_Development_Test_DevTestNumber_Language/Multilingual.exe because it carries meaningful information about the app itself, not meta-information that they have to take extra steps to decipher.
Regardless, if you've got no aspirations to having it released officially you are welcome to call it what you want, but for the sake of existing PortableApps users, and the PortableApps spec, that is the format we use.
Okay, I see. Shows how much I know. Disregard my "it doesn't matter" comment.
I will admit the version numbers did kind of throw me off at first.
It's easy enough to not realize.
The spec only goes into the format of version numbering, and the meaning behind the relationship isn't exactly obvious until someone explains it.
Pretty sure I had a few confusing moments when I was starting to develop, until I found a thread somewhere around here that explained it.
On the website, it's 1.3.2. Why the discrepancy?
Think this is ready to be official?
Sometimes, the impossible can become possible, if you're awesome!
I referred to it as a test because I assumed I have to wait for you to make it official.
That also explains the discrepancy - I saw in other listings here that test versions' numbers always look different than real versions' numbers.
So if you're ready, tell me how to proceed and I'll call it after the real version (which already got updated, BTW).
We use the same versioning for Dev Tests as for stable. They follow a specific pattern to ensure that when we switch from dev test to stable, users get the update. So, for LWBlat Portable 1.3.3, it would have a PackageVersion of 1.3.2.99 and a name of 1.3.3 Dev Test 1. That way when it's official, it would be 1.3.3.0 and platform users get the update.
One question... what do you think the rate of abuse would be for Blat? If it's high, releasing it may be counterproductive as it may make our apps more likely to be blocked by institutions. If it's low and people mostly use Blat for testing mail configurations and the like, it shouldn't be an issue.
Side question... why is the icon ClamWin's? Does LWBlat GUI not have an icon? If not, we can use one from the Oxygen set. I can handle that for release.
Sometimes, the impossible can become possible, if you're awesome!
By "name of" do you mean "DisplayVersion"? Or do you just mean what I write in the forum when I post a new test version?
Whatever your reply is, I think these helpful tips should be documented.
Clamwin's icon is probably the launcher's default. Please show me what do you prefer. Can I also use it for the non PortableApps version?
As for Blat, its license forbids it to be used for spam. But license aside, it has been around since the late 1990s. Its latest update is from earlier this year. It has its own website and little community. It's not a secret buried in the dark web waiting for people like you and I to expose it to the world for what it is.
Plus just like my program is a front-end for Blat, the program Blat itself is a front-end for handling server communications.
Just like https://portableapps.com/apps/internet/putty_portable
I've fixed the versioning, BTW.