I often used the BLAT.EXE to debug email sending, as each ISP seems to have slightly different interpretations of what is required to logon in username (dloyd or dloyd@isp.com) and ports and AUTH LOGIN vs. username. With the -debug and new -superdebug options, you can get a verbose text file that gives you some clues on what you might need to set up.
Then you can cycle through the variations of this: http://www.blat.net/syntax/syntax.html
If the client is already using this ISP for their email, it can be helpful to review the settings of one of their mail clients.
ISPs *usually* post their email client settings somewhere on their support site, and these can provide valuable clues. You might discover you need to use TLS or a non-standard port in order to connect.
On Thu, Jun 28, 2018 at 1:31 PM, Desmond Lloyd desmond.lloyd@gmail.com wrote:
Good Morning all,
Have been using Blat here at work for years. Essentially modifying the code as the need arose. now have a client that I would like to use it on, but for some reason it always returns a code 1 in the new environment but works fine here at work...
Would someone please look at the sample below to see what I might be missing?
LPARAMETERS lcsubject, lcbody, lcrecipient, lcfrom, lccopyto
lcFrom = 'dlloyd@wow.com'
*lcfrom = 'dlloyd@test.com'
lcSubject = 'Email Test'
set Safety off
lcBody = 'This is a Test of an automated email system. Third Test. Would you Please reply if received'+ CHR(13) + CHR(10) + CHR(13) + CHR(10)
lcRecipient = 'desmond.lloyd@gmail.com'
STRTOFILE(lcbody, "Body.txt")
lcstring = 'C:\Body.txt -s "' + lcsubject + '" -to ' + lcrecipient + ' -f '
- lcfrom + ' -u '+'dlloyd'+' -pw '+'password'+ ' -server '+'192.168.999..62'
dll_name = "blat.dll"
DECLARE INTEGER Send in &dll_name STRING blatstring
lnresult = send(lcstring)
IF lnresult > 0
wait window 'Result: '+alltrim(str(lnREsult))
ENDIF
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]