Deltachat-android: Wrong Yandex Mail settings by default

Created on 6 Aug 2020  ·  17Comments  ·  Source: deltachat/deltachat-android

Delta Chat for Android.

imap.yandex.ru (incoming server) and smtp.yandex.ru (outgoing server) is always for [email protected], [email protected], [email protected] and [email protected]!
No others smtp and imap servers for Yandex Mail!

  1. But and with this custom imap settings Yandex Mail not work a long time ago in DC for Android...:(

(P. S. Yandex it is No.1 as free e-mail in Russia and No.2 as Web search.)

bug

Most helpful comment

I've pushed a fix for async-email/async-imap#35 and from my testing, the PR fixes the issue.
If you'd like to give a spin:

async-imap = { git = "https://github.com/avitex/async-imap", branch = "fix-auth" }

All 17 comments

IMAP protocol is on there, and e-mail clients for Android (AquaMail for example) is works with Yandex Mail.
(Oauth in DC also not work with Yandex Mail.)

From Yandex FAQ (quote):
"To configure the mail program via IMAP, you must specify the following data:

Incoming mail:
mail server address - imap.yandex.ru
connection protection - SSL;
port - 993.

Outgoing mail:
mail server address - smtp.yandex.ru
connection protection - SSL;
port - 465."

strict_tls is set true in https://github.com/deltachat/provider-db/blob/master/_providers/yandex.ru.md , I guess this line should be removed.

Why? Yandex has valid certificates.

@link2xt Ah, I thought this feature was valid only for STARTTLS. Sorry about that.

But something else that is mentioned on the Yandex IMAP configuration support site caught my eye:

If you are configuring email delivery from a mailbox such as “[email protected]”, your username is the first part of the address before the “@” sign.

That would be username_pattern = EMAILLOCALPART , right?

A bit off-topic, related bug.

But and with this custom imap settings Yandex Mail not work a long time ago in DC for Android...:(

I have just tested, with @yandex.ru and OAuth2 it works on Android, but you have to enable IMAP in Yandex Mail web interface first. Look into the logs for lines about bad IMAP response ([CLIENTBUG]), if it is there, then authentication actually failed, but it was not reported to you due to https://github.com/async-email/async-imap/issues/35

Sure providers database still should be fixed to make other aliases like @ya.ru work. I was just testing @yandex.ru first and found this async-imap bug.

providers database still should be fixed to make other aliases like @ya.ru work

@link2xt Actually the other domains are included in https://github.com/deltachat/provider-db/blob/master/_providers/yandex.ru.md .

hm, autoconfig directly from yandex reports that yandex._com_ should be used: https://autoconfig.yandex.com/mail/config-v1.1.xml

however, the autoconfig also reports that oauth2 should be used for authorisation - may it be that normal-login is not working at all? was there some change? unfortunately, my yandex test accounts are blocked or disabled, they want a mobile number now ... so i cannot really have a "quick look" ...

imapserver
smtpserver
^ My mail settings for @yandex.com in Aquamail for Android. All work. (IMAP is enabled in web settings of Yandex Mail.)

Telephone number is optional (is not required.)

Yeah, Oauth2 is broken too in DC for Yandex Mail.(at me).

thanks for the information. as @link2xt pointed out, we should add server-settings to the provider-db of yandex - if possible, can you check if imap.yandex.com - works or not? this is the server DC is using as that is announced from yandex itself (as we do not have an entry in provider-db)

I just checked, my Oauth2 setup for @yandex.ru is using smtp.yandex.com and imap.yandex.com in configured_ settings. So for me oauth2 works with yandex as expected, their autoconfig is correct.

Delta Chat for Android.

imap.yandex.ru (incoming server) and smtp.yandex.ru (outgoing server) is always for [email protected], [email protected], [email protected] and [email protected]!
No others smtp and imap servers for Yandex Mail!

I was wrong. Now works imap.ya.ru, imap.narod.ru, imap.yandex.com, smtp.ya.ru, smtp.yandex.com etc.

It's IMAP protocol was blocked by security reasons.in my other Yandex account. Sorry. I seen it just now. (Recommended close this ticket if no another bugs with Yandex Mail.)

It's IMAP protocol was blocked by security reasons.in my other Yandex account.

Real problem is that this error is not reported to the user: https://github.com/async-email/async-imap/issues/35

It still makes sense to add smtp.yandex.com and imap.yandex.com to provider database to speed up configuration, Yandex is very unlikely to change this as it will break all existing setups.

did a pr that adds yandex servers: https://github.com/deltachat/provider-db/pull/131

the real problem, https://github.com/async-email/async-imap/issues/35, however, stays open.

but there is nothing, we can do on that android-wise, however, we can keep this issue open to be reminded to the bug :)

Let's close this bug then.

I've pushed a fix for async-email/async-imap#35 and from my testing, the PR fixes the issue.
If you'd like to give a spin:

async-imap = { git = "https://github.com/avitex/async-imap", branch = "fix-auth" }

Merged 7 days ago into upstream async-imap. Yay! Thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

angelo-fuchs picture angelo-fuchs  ·  3Comments

gerroon picture gerroon  ·  3Comments

luisfsr picture luisfsr  ·  5Comments

BoFFire picture BoFFire  ·  4Comments

adbenitez picture adbenitez  ·  4Comments