Test cornercase encountered in practice: a user claims a timezone different to that of the system and creates a calendar item in various formats
This test currently fails, because when we convert the time between the user and the system timezone, we are too strict and allow only the "long" timestamp format "%Y-%m-%d %H:%M:%S"