 Dave asks, we previously used Pop3 with an email address and Outlook as a team email address. Each user, so three of them, would be able to read and send from the email address and also maintain our inbox with read or unread messages separately. Now that Pop3 can't be used with Outlook, we are exploring shared email address, but need each user to be like before, that when user A reads the email, it does not show as red on user B or user C's inbox until they read it. Each user needs to be mutually exclusive of the inbox status. Microsoft is telling me that it's not possible. Is this true? If so, ideas on how to work around that and stay in Outlook. Well, from my standpoint, it's just keep doing what you've been doing. Pop3 is not going away. What's going away is basic authorization for Pop3, which that means that you need to now use modern authorization, which means 2FA, MFA, whatever you want, and an app-specific password, and you should be right back in business with everything. Well, that was easy. Okay. There you heard it. It's basic auth that's going away, not Pop3, not IMAP, that the protocols themselves are just fine. They've been around a long time and they'll continue to be around for a long time. What is going away is straight username password authentication, good old-fashioned basic auth. It's gone. You now need modern auth and that's OAuth2. Anyway, you get to OAuth2 is either you've got something that negotiates OAuth with things to with the server itself, which unfortunately, to my knowledge, no Pop client does. Outlook does for the newer versions of Outlook. I'm not sure if it's 28, if it goes back as far as 2016. I believe it does, however, but any event for an IMAP account, Outlook will support and will work with OAuth2, which means you don't need to use apps-specific passwords and stuff like that with Gmail accounts. Unless it's a Pop account, unfortunately, nothing does OAuth2 from the Pop standpoint from there. You've got to go with modern auth, which in the case of a Pop account, means an app with creation-specific password. Let's go. When I first read this question, I'm like, wait, what? Because I host my own domains. I have several businesses and I use Pop3 to get that email into Outlook so I can manage it. I was like, wait, what? It's gone away? I had a little moment. Thank you, Hal, for giving me a little piece of point. You know what it comes down to, is exactly what you're using, the configuration you're using, and what the end result is, and understanding what all of it means. Microsoft uses a lot of jargon, things that they say, hey, this is going away, this is going away, that puts a lot of people on edge. Sherry, you and I have been on like, you know, those edge steps. It's making sure you fully understand what Microsoft is changing. Definitely read into the details. Do some follow-up on it, because in this instance, how is 100 percent correct? Not a lot is really changing, as long as these things are handled, which majority of the time they already are if you're using that functionality. So you just have to really deep dive into it and understand what Microsoft is saying, and not just take it for the five words they use in a title kind of scenario. The five words that I understand. I don't know that. Oh, awesome. Exactly. Yeah, all that, blah, blah, blah. Stop presenting, like, you know, don't listen to that. Read deep into it a little bit more, because how is 100 percent correct? There's no reason why they should be impacted whatsoever.