You need to do what the documentation tells, apply SHA256WithRSA to your message (that JSON). SHA256WithRSA gets the message and your private key as parameters. You then add the resulting byte string

Hi Adam. You do not need to do anything on Magic side. Encryption is from your client to IIS. You need to configure SSL/TLS (https) correctly in your IIS which is a bit more than just allowing the pro

For me this sounds as if you did not configure the relay for outgoing mail properly.

Which browser do you use to see it working on Windows Server 2008 ? Maybe you have to activate TLS 1.2 on that system. You could check what the TLS version is for your connection with a network monito

If you are logged in as Supervisor you can use functions UserAdd and GroupAdd to modify the security file.

Can you check if mgfreeimage.dll and freeimage.dll are actually there (reside in the directory of your Magic installation) ? Other than that I cannot see a reason why Magic should not be able to load

How do you create your JSON. There should be no HTML tags if you write them with JSON templates to a Blob or use String functions. Do you have HTML templates ??

And now, since you did that exercise you can use Elasticsearch for quite everything and have Kibana for nice visualizations and dashboards. Here's an example of a logstash plugin for Google Analytics.

Integrating Google Analytics with Elasticsearch to access from Magic XPA is maybe a good idea anyways. Should help a lot.

Thats not the .net way and the author explicitely asks for no .net replies ;). Its C++ / WinSDK

I can imagine that the Web Client is better than you think, Craig ^^. Still I would not want to have that tight coupling either and would rather learn Angular where I then could have Magic on the back

Your path is ok for a 64-Bit version of Magic, it is however not relevant for a FileCopy operation anyways. Magic implements that natively and does not need a command shell to execute that operation.

Finally ^^ Thanks for that information. Still, Stunnel solves the problem without any changes required in the appliction.

Hi Hershel, Magic's SMTP/IMAP functionality does not support SSL/TLS and that's the only option with office365 You can workaround with stunnel. Check here for a start: https://www.winsysadminblog.com/

You can. Magic & Unicode has some minor caveats but basically its a nice solution and porting is easy. Now I do not do any Magic anymore but before all my Magic applications were Unicode since very lo

Hi Mike, I too do not really know what made your initial UTF8FromAnsi approach fail, I would have to look into the conversion result in an hex editor. You should not do it on the whole blob but only o

Hi Mike, UTF8FromAnsi should work, you then however need to set the I/O Properties to ANSI. Did you do that ? If I/O Properties is UTF-8 (If this is an option - I do not remember) then you would not u

Hi Mike. It's obviously ANSI what you do write to your XML, not Unicode / UTF-8. You have to set the charset in your XML header accordingly to charset=iso-8859-1 That does however not mean that the re

Let us know your results. Magic's problem with encrypted email communication is discussed here quite frequently and that stunnel is a nice solution. When I have some time I'll do a sample configuratio

Here is some information regarding the idea with the tunnel. Your user has to install that on his desktop. Then Magic will work fine with smtp.office365.com . https://www.winsysadminblog.com/2019/02/u