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

SAVEDATE work out behaviour when unsupported by the implementation #13

Closed
brong opened this issue Jan 4, 2018 · 2 comments
Closed

SAVEDATE work out behaviour when unsupported by the implementation #13

brong opened this issue Jan 4, 2018 · 2 comments
Assignees

Comments

@brong
Copy link
Contributor

brong commented Jan 4, 2018

Currently the text says [FIXME: This is what Dovecot currently does, but for a
standard this is inappropriate. It should probably indicate the lack
of support with a particular NO response code, or it could just
return NULL or some other special value].

This needs to be resolved before publication.

It is also necessary to document how the SEARCH extensions work

@stephanbosch
Copy link

See the discussions on the mailing list. I am still not sure how to address this.

@stephanbosch
Copy link

Addressed in latest draft.

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