Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support IMAP4 Login Referrals #111

Open
lberezy opened this issue Mar 28, 2019 · 1 comment
Open

Support IMAP4 Login Referrals #111

lberezy opened this issue Mar 28, 2019 · 1 comment

Comments

@lberezy
Copy link
Contributor

lberezy commented Mar 28, 2019

I'm wondering if support for RFC 2221 (IMAP4 Login Referrals) is planned?

It's possible to slightly work around this now by checking the error message thrown upon login or authenticate and parsing the message manually, but it seems like this could be a useful integration.

The current real-world case that prompted this question is a dovecot cluster, where a user's home mailbox exists on another server.
This will result in either:

  • No Response: [REFERRAL imap://test%40mail1.example.com;AUTH=*@mail2.example.com/] after authentication against the other cluster member.
  • Or No Response: [REFERRAL imap://test%40mail1.example.com;AUTH=*@/] in the case where the authentication is handled by another cluster member, but the server is unavailable (e.g. due to maintenance).
@jonhoo
Copy link
Owner

jonhoo commented Apr 1, 2019

Ah, interesting! It's not something I've looked at or planned, but it seems like a useful feature. I'd be happy to review a PR if you want to try to write something up? I don't think it should be too difficult :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants