 So let's move on to the next talk the always lovely Anna from my engineering team. She's going to talk about mail She was also in a keynote presentation yesterday. Anna. Here's here's the mic Thank you Presentation just a sec full screen All right. Hello. I'm gonna quickly talk about the IMAP integration we have done for mail So this is the RFC 647 and defines the integration of the IMAP protocol with a male client So you have all seen this screenshot. This is what it looks like. You can accept the client and so on invitations from a calendar in mail now and This is a bit of the technical background now Let me first get into the commonly used terms that we're going to be talking about today We have the organizer which is the person that sends or counsels an invitation We have the attendee which is the person who receives an invitation and the V event is the text file that contains all the information about the event The parsing happens in the mail So you receive an email and the content header will tell you what type of messages is so it can be one of three Which is a request a reply or a cancel now a request and a cancel are sent from an organizer and the reply sent from an attendee an organizer will either send you an invitation which you can accept with the previous dialogue or He will send you he or she will send you a cancel of a previous event that you have been invited to The attendee sends a reply and in this reply The really important part is to not share data that only the organizer will receive this email So let me get into the technical considerations who is allowed to do what this is the really interesting part So the organizer has to be the one that sends the cancer. How do we check this? Well, we go through the V event and if you receive a reply or a cancel We make certain checks on the attendee certain checks on the organizers. This has been a really Interesting and fascinating piece of code to write because there's just so much stuff to do So first you have to check the email address then you have to check the reply to header Which can also be used to define that this is an email from an organizer because sometimes you have system emails So it is still very important that the immigrants Processed from the system email so set of reply to header and you should be good to go And then you have a really really nice feature that is a party crasher It is actually called that in the scheduling RFC. They're called party crashers. We also have a comment in the code I really love that and you are not allowed to party crash with IMIP So really important to check if the attendee that is sending you a reply is actually in the original event because otherwise I could just send a reply to any old email, you know a shot in the dark and invite myself to your CEO's Stakeholder meeting or whatever and then be accepted and be able to take part in this event Maybe I get a talk link or whatever, you know So yeah, it's a good thing to have a security consideration like that And then of course you have to write the data to the back end now This is the classic right to the calder back and in our case It has been a bit of a challenge to implement this with the Saber library at the moment because of all sorts of considerations on how to Actually get the calder back end in the code Since we're from writing from mail to the calder back end But all in all it has been a super interesting challenge So if you want to take a look at the code or like talk to me feel free to I will be here all day And this has basically my talk. So thank you Thank you Anna. Thank you so much