Tuesday, November 09, 2021

Microsoft makes its own calendar UNDO!


Finally Microsoft does something to fix the terminated user problem of ghost meetings.

Remove-CalendarEvents -Identity user@domain.com -CancelOrganizedMeetings -Confirm:$false -verbose

Arm yourselves with knowledge!

Sunday, October 31, 2021

Kerio Mail Contacts and Office 365 Migration

Our latest version of Kerio migration code adds two options to the XML file to deal with autocomplete contacts.

  • Set the ‘migratesuggestedcontacts’ switch to FALSE if you don’t want to migrate them.
  • If 'migratesuggestedcontacts’  is TRUE, the contact subfolder named in the migratesuggestedcontacts_o365foldername will be created (if it doesn’t exist) and those contacts added to the folder.



Tuesday, October 26, 2021

BusyMac and Kerio Bugs and Migration to Office 365

We found some weird calendar stuff in Kerio when using BusyCal


This (really weird) addition to the iCalendar format was causing us some problems with the recurrence pattern until we coded around it.

Apparently it's been reported as a bug in in their forum since December 2020.  https://github.com/jens-maus/node-ical/issues/67

But rather than waiting for someone to fix a moribund client to moribund server we coded around it to make it easier for folks to get into Office 365.

Friday, October 22, 2021

Turning off EWS Throttling in Office 365

Microsoft must have realized this was an issue – they finally made it easier to temporarily change EWS Throttling under admin control.

And by "easier" I mean it is "possible if you know exactly what you are looking for."

So to remove EWS Throttling

Login to Exchange Admin 

Click Support and follow with New service requests.

In the search field, search for Increase EWS Throttling Policy

Select that from the list

Click Run Tests – it will first tell you are throttled (big surprise)

Click Changing EWS Settings – select 30/60/90 days

Run Tests again.  – Should now be good to go.

Thursday, September 30, 2021

Multiple Domains in a Kerio Calendar Migration

You know how it is -- you've had your legacy system for YEARS and sometime in there you changed domains from say OLDCOMPANY.com to NEWCOMPANY.com or something like that.

And now as you are migrating into Office 365 you wonder if you can take all that over and have it work in calendars the way it used to.

Have no fear -- you can do that.  Just put both in as in the screen shot on your configuration page.


Wednesday, August 18, 2021

Kerio Calendar Data Weirdness

 One of those things we always worry about is data integrity.

We've seen weird stuff.

And now it's Kerio's turn to provide us with weird.

Take a look at this raw ICS file from some recent field data:

I'll cut to the chase.  The END date (line 14) of this recurring appointment is later than the UNTIL date in the RRULE (line 15).  So trying to insert this Microsoft Exchange Web Services called us very bad do-bees.   

Not hard to generate odd situations with a variety of clients on a technologically moribund server.

Wednesday, August 11, 2021

Block Mail to Recipients Outside of your Organization

We recently announced that we've started work on a  Kerio Server Migration to Office 365.  One of our clients gave us test data from a few departed/terminated users to test our code.  It's easy to test in our Exchange on-prem sandbox to ensure no "external" email gets sent to their users -- we unplug the Ethernet connection to the Router. It's a little more complicated in Office 365, but not all that difficult.  Here are the steps:

In the Exchange Admin Center, under Mail Flow, Rules, click the "+" sign to create a new rule.

  • Name the rule.  We called it "Block Mail sent to External Email"
  • Select the option from Apply this rule pulldown: "The Recipient is Located...."
  • Select the option "Outside The Organization" from the subsequent pulldown that the recipient is located 
  • Select "Reject the message with the explanation" from the pulldown "Do the Following..."
  • Enter a message (optional):  We entered "The message was not sent. The Recipient is located outside the company."
  • We chose to Enforce the rule, and finally
  • Saved it

  Here is a screen shot:

So now let's say a user tries to send email outside your domain.  They will be informed that is an unsanctioned action with this message: