Do you need to change the language of Office 365? Some how this is a little tricky as the language needs to be changed in two places:
In this blog post I explain how to change the language in Office 365 and an important gotcha when it comes to the names of default mailbox folders. Continue reading
I’m busy migrating from Hosted Exchange 2007 to Office 356. While setting up the mailboxes I thought it was time to solve one of my long time irritations that my current hosted Exchange setup does not support catchall for my mail domains. It turns out that this is not straight forward to setup as Microsoft does not support it.Yes I know there are a lot of people out there who think it is bad practice to setup a catch all mailbox. Personally I use it for convenience and I think it is more customer friendly for the non tech savvy people out there. And no I do not mind going through (a lot of) spam mail to find that little gem.
O well, I Googled around and found a great blog post that explains the basics how to setup a catchall email address. However the instructions did not work as is for me and I feel they are not complete. Let me rephrase that last statement: I think Office 365 has been updated since the post was published and therefore some parts no longer work as described. Anyway, I decided to write this blog post that should cover all aspects of setting up a catchall email address under the current version of Office 365, as of 24-11-2015 🙂 Continue reading
Setting up Office 365 I entered the SPF TXT record as specified by the instructions.
When I ran the verify functionality on the Office 365 admin console it indicated that the SPF TXT records could not be found. Continue reading
Setting up Lync for Office 365 I ran into a problem that the SRV records were not being recognized. The instructions in Office 365 are to define two SRV records for Lync. My provider is Linux based, so setting up the SRV records is a little bit tricky. Anyway the general DNS instructions of Office 365 expect every field of the SRV record to be a separate field. Continue reading
I pulled the Scalatra examples from Github and ran the Swagger example for Scalatra version 2.3. The example runs, but the API documentation is not generated completely. I was using the example as is. Continue reading
I am running Scala version 2.11.1 and Scalatra version 2.3.0 and had a strange problem that plain vanilla halt does not work when the trait JacksonJsonSupport is mixed in with my controller class. Here are two simpel code snippets to illustrate the problem. Continue reading
In SBT it is possible to automatically recompile and reload a web app when a source file is changed by using the following command:
container:start ~ container:reload /
The first command starts the web app container the second command watches for source file changes and reloads the web app container.
Seriously? Unsupported major.minor version 51.0 when compiling a Scalatra project? The complete error is “Caused by: java.lang.UnsupportedClassVersionError: org/eclipse/jetty/server/Handler : Unsupported major.minor version 51.0”. After some Googling I found the following statement “You are using different JDK versions to compile and run the application”. No way, that is not possible. Continue reading
Scalatra is a micro framework for Scala. Installation does not seem to be as straight forward as adding Scalatra to the dependencies of build.sbt. It requires a number of other tools to work: Conscript and giter8. Conscript is a tool for installing and updating Scala code. giter8, which depends on conscript, allows you to check out project templates directly from Github. It’s the recommended way to generate Scalatra project skeletons. These are quick installation instructions for Scalatra on Windows. Continue reading
Grrrr, just cloned some of my code from Github to my laptop. I initially worked on this code on my desktop. When I tried to compile it in sbt I got the following error sbt.ResolveException: unresolved dependency: com.typesafe.play#play-json_2.11;2.3.0: not found. It had been a while since I worked on the code so I was puzzled. It turns out there are problems with the Typesafe repository. As a workaround the repository needs to be added as a resolver to the build.sbt file.
resolvers += "Typesafe Maven Repository" at "http://repo.typesafe.com/typesafe/maven-releases/"
After this it compiled nicely. Sweet. Happy coding 🙂
Adventures of a space monkey 