| Newsgroups |
gmane.mail.blat |
| Message-ID |
<[email protected]> |
Thanks for that. But then I have no idea why my installation then basically is working on my PC with Port 587? I found some hints on the net pointing to Port 587 not necessary requiring encryption via SSL or other.
Encryption would be nice_to_have, but I rather send unencrypted email than none at all.
That said, we need a way to install blat to be rolled out to about 200 or 300 clients of our POS system. I wont be able to make the installations all myself, and neither our clients nor my staff does possess the knowledge to install and configure a plethora of additional utilities. What would be needed is:
A batch file that is executed by our POS at the End of A Day. That one exists.And is working. (Needs a bit of tweaking for error handling, but I should be able to fix this with the examples posted on the blat.net page.
Distribute blat.exe and the other files, plus text files that will be filled with recipients email addresses and further email subject etc. information,all into one folder to be copied by the Installer of our POS Program on a version update. And I here I would like to have either a batch file or a Windows reg file that takes care of the registration of smtp server smtp user name password port number or attempts and all that.
My clients and staff would then need to:
One time run the batch file / reg file.
Fill email addresses into the empty provided recipients.txt, ccrecipients.txt, bccrecipients.txt and subject.txt files.
Anything that requires much more manual setup and configuration would be beyond the scope of both my clients and my staff.
The Documentation on Blat concerning installation on command line seems to be either misleading or incomplete. I tried a few times and almost every time got not the expected results. There is a way with letter preceding the entries, another way with more verbose strings, and finally one way where the parameters are entered without a prefix. None of these seem to work, especially in my case where we need to specify SMTP credentials. Also I feel a little bit more secure to have the sensitive smtp password encrypted in the Windows registry, than in verbose form in a distributed text file