SMTP에서 OAuth로 전환

[Pierpinna]

Hi,

Because of a new company policy need to switch our site email configurations from SMTP to oAuth. However, I can’t find that option in the admin panel.

Any help?

Thanks

[NateDhaliwal]

SMTP sends emails (daily digests, password reset), while OAuth authenticates (and logs in) users. I don’t think they are substitutes for each other, unless I’m understanding wrong…

[Pierpinna]

Due to this: Deprecation of Basic authentication in Exchange Online | Microsoft Learn

[NateDhaliwal]

If I understand correctly, I think a similar question has been asked a few years back, and this was the response:

Basic Auth Disabled in Office 365

Looks like there’s no need to switch to OAuth2. SMTP AUTH will still be available when Basic authentication is permanently disabled on October 1, 2022. So, you should be able to change to SMTP Auth by adding an additional env variable to app.yml. DISCOURSE_SMTP_AUTHENTICATION: cram_md5 In addition to that I think you will need to use the MD5 hash of the SMTP password as value of the DISCOURSE_SMTP_PASSWORD setting. Rebuild the Docker container after those changes and give it a try.

[Pierpinna]

Thank you for the reference to the previous discussion.
However, from our IT department, they tell me:

This response seems to be misleading. SMTP Auth is a parent category that includes both basic and modern auth (OAuth2). By the description of the configuration, you are still configuring basic username and password. Here is an explanation from the Microsoft forums:

“SMTP AUTH is usually recommended by most vendors/suppliers and is supported by most apps/devices. SMTP AUTH can be done using Basic and Modern Auth, depending on the vendor/app/device (but since MS is deprecating basic auth, it needs to be configured with Modern Auth)… Modern authentication is based on the Active Directory Authentication Library (ADAL) and OAuth 2.0.”

Definitive Guide to smtp auth vs basic auth vs oath auth vs oath2 vs. modern...

So while it is correct that Microsoft is not discontinuing SMTP Auth, it is true that one of the methods included in SMTP Auth will not be available (specifically using a username and password).

The suggested solution does not seem applicable as described. How can we proceed?

[Pierpinna]

Hey @NateDhaliwal , do you have any suggestions on how to proceed?

Thank you

[pfaffman (Jay Pfaffman)]

You’ll need to make a plugin or use a mail delivery service that uses smtp auth.

[Pierpinna]

Who could help with the creation of the plugin? Or do you know any service that uses SMTP authentication?

Thank you

[NateDhaliwal]

@Pierpinna

Who could help with the creation of the plugin?

You can post a topic on Marketplace, and hopefully hire a developer, for a fee.

[pfaffman (Jay Pfaffman)]

@Pierpinna

do you know any service that uses SMTP authentication?

Virtually all mail services use SMTP authentication. All of those mentioned in Configure VERP to handle bouncing e-mails, for example.

[lxbnks (Alex)]

https://auth-email.com으로 전환했습니다. 이 서비스는 OAuth 이메일 서비스에 자동으로 연결되므로, 일반 SMTP만 사용하면 됩니다.

[rogerreed]

@Pierpinna

안녕하세요,

새로운 회사 정책으로 인해 사이트 이메일 설정을 SMTP에서 oAuth로 전환해야 합니다. 하지만 관리자 패널에서 해당 옵션을 찾을 수 없습니다.

도움 주실 수 있을까요?

감사합니다

MailEnable은 Microsoft나 Google처럼 SMTP에 대한 OAuth를 지원하지 않습니다. 주로 기본 인증(Basic Authentication)을 사용합니다. 정책상 OAuth가 필요하다면 Microsoft 365나 Gmail과 같은 외부 SMTP 서비스로 전환하거나, OAuth를 지원하는 릴레이(Relay)를 사용해야 할 가능성이 높습니다.