<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Feature Request: Manual Configuration Guide or Resources in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/feature-request-manual-configuration-guide-or-resources/m-p/82926#M31664</link>
    <description>&lt;P&gt;For context: My school uses a 2-step authentication via Duo Security to sign into their email server. The automatic configuration didn't realize this and as a result the authentication method was left on "normal password", when it should've been on "Oauth2". This simply configuration issue ended up being a massive hurdle for me because as a person who's very inexperienced with email I was unable to find what the issue was, and I misdiagnosed the problem as my school's email server not supporting IMAP.&lt;BR /&gt;&lt;BR /&gt;I would like to see some sort of resources (even if it's just a link to a webpage) to help guide people through the manual configuration should they need to go through it. I feel that in my specific case a lot of headache could've been saved if it was pointed out to me somewhere that if I'm authenticating via a 2-step authentication service I should change authentication to "Oauth2".&lt;/P&gt;</description>
    <pubDate>Wed, 08 Jan 2025 18:41:22 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2025-01-08T18:41:22Z</dc:date>
    <item>
      <title>Feature Request: Manual Configuration Guide or Resources</title>
      <link>https://connect.mozilla.org/t5/discussions/feature-request-manual-configuration-guide-or-resources/m-p/82926#M31664</link>
      <description>&lt;P&gt;For context: My school uses a 2-step authentication via Duo Security to sign into their email server. The automatic configuration didn't realize this and as a result the authentication method was left on "normal password", when it should've been on "Oauth2". This simply configuration issue ended up being a massive hurdle for me because as a person who's very inexperienced with email I was unable to find what the issue was, and I misdiagnosed the problem as my school's email server not supporting IMAP.&lt;BR /&gt;&lt;BR /&gt;I would like to see some sort of resources (even if it's just a link to a webpage) to help guide people through the manual configuration should they need to go through it. I feel that in my specific case a lot of headache could've been saved if it was pointed out to me somewhere that if I'm authenticating via a 2-step authentication service I should change authentication to "Oauth2".&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jan 2025 18:41:22 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/feature-request-manual-configuration-guide-or-resources/m-p/82926#M31664</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-01-08T18:41:22Z</dc:date>
    </item>
  </channel>
</rss>

