<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;">
<p dir="auto">On 21 May 2025, at 9:11, leo wrote:</p>
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;">
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; border-left-color: #999999; color: #999999;">
<p dir="auto">You should be able to authenticate then no longer need the app specific password. Alternatively, go to the IMAP Account settings in MailMate and disable OAuth2 for both IMAP and SMTP. This should put you back on the app specific password use.</p>
</blockquote>
<p dir="auto">I disabled Oauth ā and now it all works perfectly. Iām happy again. š</p>
<p dir="auto"><em>However</em>, I am not sure whether it is a good decision with this update to <em>silently</em> switch people who have an app-specific password to a new authentication method they might not want.</p>
</blockquote>
<p dir="auto">Good point. It wasn't really intentional. MailMate just picks the best available option and that implicitly changed when I added OAuth2 for Fastmail.</p>
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;">
<p dir="auto">Does anything speak against app-specific passwords with Fastmail?</p>
</blockquote>
<p dir="auto">Well, it's a bit harder to use a stolen OAuth2 token than an app-specific password. It's also easier for the user to configure since the browser-part is better integrated.</p>
<p dir="auto">--<br>
Benny</p>
</div>
</div>
</body>
</html>