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 …
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. …
With the retirement of Formate eVo 9.7 in 2023, the last of the version’s authored by Trilogic Ltd will no longer have active support. It has therefore been decided to also retire the online license activation endpoint used by Formate eVo in version 9.7 and before.
Unfortunately we cannot say precisely when this will cease, as it is not managed by ourselves, but activation will continue to be available via email to our Helpdesk*$
Going forward a number of options are available;
Update your Formate eVo installations to eVo 21 or higher – if you do this please take note of the release notes about the steps necessary as you will need to go to version 21 and then update to a later version if required. if in doubt please contact the helpdesk
Contact the Helpdesk for guidance on how to manually amend the activation URLs held in the settings database.
Use the alternate “Activate by Email” option available*
*UK Office Hours $ An un-activated eVo (9.7) instance will run for 48 hours before function will be restricted. v21 and above this period is extended to 14 days.
Outlook is trying to retrieve data from Microsoft Exchange server outlook.office365.com”
This is a fairly common message to O365 Administrators and users, telling you that the O365 mailboxes are being slow to respond. Symptoms can include a user’s Outlook client freezing temporarily, or being very slow. In some extreme cases Outlook clients need to be restarted.
Please bear in mind, if Formate is connected to an O365 mailbox, it is considered a simple user and will see similar events, possible breaking the connection, but certainly interrupting processing.
Based upon Microsoft Articles published 13.12.2022
We are asked many questions about sending emails via O365 online Exchange.
The first thing to remember is that you and your colleagues sending emails from Outlook, or via an attached web client is very different to a back office system such as Formate eVo sending emails. The second is that strictly speaking online Exchange or O365 is not a 100% like for like replacement of your old on premise Exchange server. Due to the nature of the beast there are usage rules enforced by Microsoft.
The key Microsoft thought is
“Exchange Online isn’t suited to accommodate bulk-mailing scenarios” .
The webpage referenced below has excellent additional information, and some possible alternatives if needed.
Looking at some of the rules;
30 emails in a minute, or 10000 total recipients a day, can all come into play if you are sending several thousands Statements at the end of the month. Even if only sending 60-70 invoices, the 30 in a minute could be a factor.
Formate has minimum send intervals etc which can be used to throttle sending, or multiple connections could be used. But it is good to be aware of Microsoft’s limits and views on the subject.
Microsoft impose the following limits as standard (although we find that application is more variable than defined here). Some limits are hard, and some more flexible.
With thanks to Microsoft; (Article published 13/12/2022)
1 After the recipient rate limit is reached, messages can’t be sent from the mailbox until the number of recipients that were sent messages in the past 24 hours drops below the limit. For example, a user sends an email message to 5000 recipients at 09:00 AM, then sends another message to 2500 recipients at 10:00 AM, and then sends another message to 2500 recipients at 11:00 AM, hitting the limit of 10,000 messages. The user won’t be able to send messages again until 09:00 AM the next day. 2 You can customize recipient limits between 1 and 1000 for existing mailboxes and for new mailboxes that will be created in the future. Edit the recipient limit on existing mailboxes individually or in bulk using the Exchange admin center and customize the default setting for new mailboxes via Remote PowerShell. For more information, see Customizable recipient limits in Office 365. 3 These numbers can vary slightly since the limit is based on number of characters so the number of email addresses will vary depending on how long they are. As a rule of thumb, it is safer to assume that the limit of smtp addresses in ProxyAddresses is approximately 300 addresses to leave room for future growth of the object and its populated attributes. 4 When outbound message volumes surpass the message rate limit, any excess in message submission will be throttled and successively carried over to the following minutes. This will typically not block the sender’s account, but Exchange Online isn’t suited to accommodate bulk-mailing scenarios. For this use case, options 2 and 3 here are recommended instead.
As part of introducing a new UnZip feature and script command – UnZipper(), will also be taking the opportunity to introduce a new Zip command – Zipper(), as the mirror.
Zipper() will replace the current Zip() command. Whilst Zipper() is slightly less feature rich around encryption, don’t worry we have a plan for that, and we aim to maintain all the features of Zip(), just structured in a different way.
Zipper(), and UnZipper() will be with you shortly, and there will be at least a 6 month overlap before the existing Zip() command is depreciated.
We will also announce the feature work around, in a few weeks.
Effective October 1, 2022, Microsoft will disable Basic authentication for Outlook, EWS, RPS, POP, IMAP, and EAS protocols in Exchange Online. If you’re using Basic authentication in your eVo e-mail connection setup with the mentioned protocols, it may fail with errors on or after October 1, 2022.
To avoid this, you will need to use our MS Office Modern Authentication connection. We also strongly recommend an update so that you have the latest edition of the connection as it has been evolving due to ongoing changes within MS O365,