Sending higher volumes of emails via 0365 – Update HVE Accounts

High Volume Email for Microsoft 365

As we have reported many times Microsoft do not allow\want the sending of high volumes of emails through a standard O365 user account, making it difficult sometimes with back office systems such as Formate eVo.

To be fair Microsoft have offered authenticated SMTP as a step forward, but whilst it expands the boundaries, it doesn’t offer a real break through. Microsoft also offer a chargeable Azure Comms service which allows the bulk sending of emails, but it is far from simple;

Overview of Azure Communication Services email – An Azure Communication Services concept article | Microsoft Learn

We ourselves have had good success sending via 3rd party services such as MailGun, or SMTP2GO, and this remains our chosen solution.

However there now might another option coming! Microsoft are previewing HVE (High Volume Emailing) accounts.

Public Preview: High Volume Email for Microsoft 365 – Microsoft Community Hub

High Volume Email for Microsoft 365 still has limitations, isn’t universally available at present but may push the boundaries still further – Might be something worth checking out.

Service Release 24.1 (24.1.24088.11215)

New Patch Release – Please see release notes in Dashboard Update Utility Headlines: Updated MS and Google Libraries for oAuth2 Email connections Reviewer Improvements with large record collections

Microsoft SharePoint – User Poll

Microsoft have announced the final removal of basic authentication to access MS SharePoint Library’s and sites.

Microsoft have announced the final removal of basic authentication to access MS SharePoint Library’s and sites. It appears this will affect MS SharePoint provided as part of O365 first, with legacy SharePoint sites being granted a stay until 2026.

At this point frankly timelines are a little unclear, but at present we will only support basic authentication and whilst we will review supporting modern authentication via oAuth, it is by no means certain we will do so.

Please let us know if you use Formate eVo’s MS SharePoint functions, via the support email address or your account manager as your input may affect our decision making. Thanks

Poll will close – 01/05/2024

Service Release 23.6 (23.6.23326.11557)

New Patch Release – Please see release notes in Dashboard Update Utility Headlines: New: Ability to exclude a font when extracting text from a PDF. Behaviour Change: Tidy up of XML field names when displayed in Layout Text item, text properties Memory Optimisation.

v23.5 Feature Release – JSON and TASKFIRE()

New Feature Release – Please see release notes in Dashboard Update Utility

Headlines:

JSON supported as a new spoolfile type, with dedicated scripting commands.

Taskfire() allows a second task to be triggered from the first. Task type and scripting commands added.

XMLfromString() – allows a fully formed XML data structure to be read from a variable into a document model, such as a response from a web service accessed via a plug-in. (equivalent JSON command also available.)

Try/Catch Exception handling coding structure added to scripting engine

+ Various minor bug fixes

MS Visual Studio demo project added to help with development of custom Plug-ins.

Fonts are Special! Part 2 Distribution

Font use and availability can be affected by how they are installed and how they are licensed. In these 2 posts will we comment upon their installation, and their distribution.

Fonts for use in eVo generated documents should be installed for “All Users”, and the license should allow for embedding or distribution within a document such as a PDF. In this, the second of these, we will look at distribution.

If you look at the details of fonts in the Font Folder, or look at the details of Font’s Properties you will see an entry for “FONT EMBEDDABILITY”

This determines if the of font is licensed to be distributed by being embedded in a parent document, such as a PDF. Fonts need to be embedded in a document, such as a PDF to ensure it is displayed as intended on a designation device that may not have that font installed. This is explained here, better than I could;

Font redistribution FAQ – Typography | Microsoft Learn

About font license restrictions – Microsoft Support

But basically, unless it says restricted, you can embed and therefore distribute the font purely for the purpose of correct display of the parent document. Such as;

Print and Preview – allows a recipient to view and print the document (no change or edit is licensed)

Edit – document can be printed, viewed and edited by recipient.

Anything with “Restricted”, will have its own license which should be consulted, as a fee may be payable to allow distribution, or it might be prohibited.