Dave Vaklyes

Deleting the PID folder (I did send it to 360Works support) did the trick. All plugins are now installed and enabled. Thanks! Dave

So I deleted all the plugins and ran my install script again. I have attached a zip of the six 360Works log files created in tmp during the process of installing and attempting to enable. (They still did not enable.) I followed the link to the 360Works page you referenced, and recreated the support files. My Java is version 8 update 211. btw - I installed FM18 and the plugins on my 15" MacBookPro running 10.13.6, and the plugins enable just fine. But I have NO Java control panel on that computer. Hope the logs tell you something. Thank you, Dave 360Works tmp Logs.zip

I have two main Macs - an iMac 5K running Mojave 10.14.4, and a 17" MacBook Pro running High Sierra 10.13.6. I had the FileMaker 18 Beta installed, with all the preupdate 360Works plugins, on both computers, and they ran just fine. (I did have to force the OS to accept them) So today I deleted the beta (folder and the 18 folder in ~Library/Application Support, and the plugins. I downloaded the updated plugins from 360Works, and installed the just released FileMaker 18. Then I installed all my usual plugins (360Works, MBS, BaseElements) In the iMac with Mojave all is well. All the plugins installed and were enabled. On the MacBook Pro with High Sierra, MBS and BaseElements enabled just fine, but none of the 360Works plugins would. Not when installed, and not when I went to Preferences:Plugins and tried to check them on. Reboot the computer and/or reboot FileMaker does not help. Any thoughts? Dave

Yes, they are. In the text section: Content-Transfer-Encoding: quoted-printable In the HTML section: Content-Transfer-Encoding: 7bit So something is not working. I attached the script steps I'm using to test this with. I am using plugin version 3.1, on FileMaker 17 (and higher). Same result on both FM Versions. Dvaklyes-email-script.txt

I tried the EmailSetHeader, but couldn't get it to work. Then I had a "Doh" moment when I realized that by setting that header the plugin does the base64 encoding. So I removed my base64 encode, and now it still doesn't work. The value of Content-transfer-encoding is not getting set. My code sequence is: Set Variable [ $resultSetup ; Value: EmailConnectSMTP( "email.XXXXXXXXXXXXXX.com:465"; "server@XXXXXXXXXXXXXX.com" ; "XXXXXXXXXXXXXXXXXXXXXXX" ; "forceTrust=1" ;"ssl=1" ) ] Set Variable [ $result ; Value: EmailCreate( "xxxxxxxxx@XXXXXXXXXXXXXX.com" ; $email ; MailingBlasts for MCC::blastSubject ) ] Set Variable [ $result ; Value: EmailSetHeader( "reply-to" ; "xxxxxxxxx@XXXXXXXXXXXXXX.com" ) ] Set Variable [ $result ; Value: EmailSetBody( $TEXT; "plain" ) ] Set Variable [ $result ; Value: EmailSetHeader( "Content-transfer-encoding" ; "base64" ) ] Set Variable [ $result ; Value: EmailSetBody( $HTML; "html" ) ] Set Variable [ $result ; Value: EmailSetHeader( "Content-transfer-encoding" ; "base64" ) ] Set Variable [ $result ; Value: EmailSend ] Set Variable [ $emailResult ; Value: EmailLastError ] Set Variable [ $result ; Value: EmailDisconnect ] Also tried it with "Content-Transfer-Encoding" if case-sensitivity was an issue. And with the EmailSetHeader before the EmailSetBody. Thoughts? Dave

Short question - Is there a way to change the Content-Transfer-Encoding when setting the body of an email? Back story - Every week we send an email blast to our folks which is an HTML eCard provided by our podcast provider (VoiceAmerica). We get the eCard as a text file with the HTML code, open the file and put the code into a field. We use EmailSetBody to attach the field to the email as HTML. For almost everyone of the 11,000+ who receive the eCard it opens just fine. But for folks with a gmail.com address, who are using the Gmail web interface, or the iOS Gmail app, the body of the message does not display. Downloading the message as a .eml shows that the HTML is in the message. Open the message with any non-google email reader and the HTML shows just fine. If VoiceAmerica sends the message, Google readers show it just fine. But VoiceAmerica is sending both the text and HTML sections with the content base64 encoded, with the header Content-Transfer-Encoding: base64. I can get the fields base64 encoded, but how do I set the Content-Transfer-Encoding header to base64? Dave

The requirements for DocuBin say "An internet connection (DocuBin works offline with some limitations)" What limitations?