Febooti Command line email v4.1 is available now. Among updated OpenSSL libraries, we have made improvement related to iOS. One of our users have reported that iPhone uses CID image caching using CID from HTML email provided from email client. Checking relevant RFCs indeed confirmed, that image CIDs must be globally unique (unique in email itself is not enough). We switched to GUID, so chance of collision is almost impossible, even if all 7,000,000,000 of world population would send emails using our Command line email tool simultaneously.
Note to developers and users who use .eml files: If you develop similar software — that sends emails that can land in the iOS/iPhone inbox, then extra care should be taken, because if possible attacker can guess your next image CIDs, she/he can take advantage of that fact and poison iOS email client cache with some SPAM images that will appear in your sent HTML email message.
Download latest version: 32-bit / 64-bit
Read history: change log
More information: Command line email
After more than 1/2 year of development, we have released Automation Workshop v1.2 (see list of changes). The most exciting new feature is Automatic backup.
We implemented automatic backup using our own Automation Workshop actions, namely, Zip files Action, Export registry Action, and a couple other. This means that Automatic backup is acting like regular Automation Workshop task — it writes in Service log file (success and failures), it can be easily extended or changed, users can even implement they own backup tasks easily.
Also, it is interesting to note that our internal automated test cases have just passed more than 1500 items. We are using a special kind of test driven development. Of course if we split all test cases into smaller peaces, there will be far more than 15,000 items, but in our metrics it is more that 1500, and each of the test case has taken [on average] more than 1 hour to build. So it is approaching a one year of full time work (WYE).
And one more thing, in 753 days Extended support for Windows XP will end. For our users this means, that after this date we will stop releasing fixes for Automation Workshop on Windows XP. Windows Server 2003 support will end about year later. Both Windows XP and Server 2003 are based on the same codebase, so most probably Automation Workshop will run on Windows XP a year after Extended support ends.