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

LOGINDISABLED capability: MUST not allow LOGIN #32

Closed
1 of 2 tasks
Tracked by #49
nevans opened this issue Nov 23, 2021 · 0 comments · Fixed by #307
Closed
1 of 2 tasks
Tracked by #49

LOGINDISABLED capability: MUST not allow LOGIN #32

nevans opened this issue Nov 23, 2021 · 0 comments · Fixed by #307
Labels
IMAP4rev1 Requirement for IMAP4rev1, RFC3501
Milestone

Comments

@nevans
Copy link
Collaborator

nevans commented Nov 23, 2021

depends on:

@nevans nevans added the IMAP4rev1 Requirement for IMAP4rev1, RFC3501 label Feb 12, 2023
@nevans nevans changed the title LOGINDISABLED capability: MUST not allow login LOGINDISABLED capability: MUST not allow LOGIN Feb 17, 2023
@nevans nevans added this to the v0.5 milestone May 20, 2024
nevans added a commit that referenced this issue Jun 27, 2024
This may be considered a "breaking change", but it should have no
negatative effect on well behaved servers.  This should merely change a
NoResponseError into a LoginDisabledError.

However, some broken servers have been known to hang indefinitely when
issued a +CAPABILITY+ command prior to authentication.  For those
servers, wo offer the `enforce_logindisabled` config option.

Fixes #32.
nevans added a commit that referenced this issue Jun 27, 2024
This may be considered a "breaking change", but it should have no
negative effect on well behaved servers.  This should merely change a
NoResponseError into a LoginDisabledError.

However, some broken servers have been known to hang indefinitely when
issued a +CAPABILITY+ command prior to authentication.  For those
servers, wo offer the `enforce_logindisabled` config option.

Fixes #32.
nevans added a commit that referenced this issue Jun 27, 2024
This may be considered a "breaking change", but it should have no
negative effect on well behaved servers.  This should merely change a
NoResponseError into a LoginDisabledError.

However, some broken servers have been known to hang indefinitely when
issued a `CAPABILITY` command prior to authentication.  For those
servers, wo offer the `enforce_logindisabled` config option.

Fixes #32.
nevans added a commit that referenced this issue Jun 27, 2024
This may be considered a "breaking change", but it should have no
negative effect on well behaved servers.  This should merely change a
NoResponseError into a LoginDisabledError.

However, some broken servers have been known to hang indefinitely when
issued a `CAPABILITY` command prior to authentication.  For those
servers, we offer the `enforce_logindisabled` config option.

Fixes #32.
nevans added a commit that referenced this issue Jun 27, 2024
This may be considered a "breaking change", but it should have no
negative effect on well behaved servers.  This should merely change a
NoResponseError into a LoginDisabledError.

However, some broken servers have been known to hang indefinitely when
issued a `CAPABILITY` command prior to authentication.  For those
servers, we offer the `enforce_logindisabled` config option.

Fixes #32.
@nevans nevans closed this as completed in 8e9a213 Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
IMAP4rev1 Requirement for IMAP4rev1, RFC3501
Development

Successfully merging a pull request may close this issue.

1 participant