mbsync身份验证失败
Posted
tags:
篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了mbsync身份验证失败相关的知识,希望对你有一定的参考价值。
我能够配置mbsync和mu4e以使用我的Gmail帐户(到目前为止一切正常)。我现在正在使用mu4e-context来控制多个帐户。我无法从我的openmailbox帐户检索电子邮件,但收到此错误
Reading configuration file .mbsyncrc
Channel ombx
Opening master ombx-remote...
Resolving imap.ombx.io... ok
Connecting to imap.ombx.io (*.*.10*.16*:*9*)...
Opening slave ombx-local...
Connection is now encrypted
Logging in...
IMAP command 'LOGIN <user> <pass>' returned an error: NO [AUTHENTICATIONFAILED] Authentication failed.
在其他帖子中,我看到人们建议使用AuthMechs登录或PLAIN,但mbsync无法识别该命令。这是我的.mbsyncrc文件
IMAPAccount openmailbox
Host imap.ombx.io
User user@openmailbox.org
UseIMAPS yes
# AuthMechs LOGIN
RequireSSl yes
PassCmd "echo ${PASSWORD:-$(gpg2 --no-tty -qd ~/.authinfo.gpg | sed -n 's,^machine imap.ombx.io .*password \([^ ]*\).*,\1,p')}"
IMAPStore ombx-remote
Account openmailbox
MaildirStore ombx-local
Path ~/Mail/user@openmailbox.org/
Inbox ~/Mail/user@openmailbox.org/Inbox/
Channel ombx
Master :ombx-remote:
Slave :ombx-local:
# Exclude everything under the internal [Gmail] folder, except the interesting folders
Patterns *
Create Slave
Expunge Both
Sync All
SyncState *
我正在使用Linux Mint,我的isync是版本1.1.2。提前感谢您的任何帮助
编辑:我已运行调试选项,我已将isync升级到版本1.2.1这是调试返回的内容:
Reading configuration file .mbsyncrc
Channel ombx
Opening master store ombx-remote...
Resolving imap.ombx.io... ok
Connecting to imap.ombx.io (*.*.10*.16*:*9*)...
Opening slave store ombx-local...
pattern '*' (effective '*'): Path, no INBOX
got mailbox list from slave:
Connection is now encrypted
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Openmailbox is ready to
handle your requests.
Logging in...
Authenticating with SASL mechanism PLAIN...
>>> 1 AUTHENTICATE PLAIN <authdata>
1 NO [AUTHENTICATIONFAILED] Authentication failed.
IMAP command 'AUTHENTICATE PLAIN <authdata>' returned an error: NO [AUTHENTICATIONFAILED] Authentication failed.
我的.msyncrc文件现在包含这些选项
SSLType IMAPS
SSLVersions TLSv1.2
AuthMechs PLAIN
答案
最后,解决方案是使用正确的密码。由于openmailbox使用第三方电子邮件客户端的应用程序密码,因此我使用了错误的(原始)密码而不是应用程序密码。
以上是关于mbsync身份验证失败的主要内容,如果未能解决你的问题,请参考以下文章
Spring boot Ldap 身份验证失败,LDAP 错误代码 49 - 80090308 数据 52e
谷歌的 Firebase UI 身份验证失败并显示消息(代码:10 消息:10)