4

我能够配置 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 Login 或 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
4

1 回答 1

3

最后,解决方案是使用正确的密码。由于 openmailbox 使用第三方电子邮件客户端的应用程序密码,因此我使用了错误的(原始)密码而不是应用程序密码。

于 2018-03-05T11:00:49.967 回答