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

search with UID ranges returns nothing under certain circumstances #63

Closed
eblume opened this issue May 10, 2012 · 4 comments
Closed

search with UID ranges returns nothing under certain circumstances #63

eblume opened this issue May 10, 2012 · 4 comments

Comments

@eblume
Copy link

eblume commented May 10, 2012

Currently it seems that UID range searches (e.g. [ 'UID', '5:'] require that at least the starting index must be a real UID.

This might not be possible due to the IMAP spec, but it would be nice if the range simply caught all emails that fell in that range, even if the starting index does not map to a real email.

@mscdex
Copy link
Owner

mscdex commented May 11, 2012

There's not much I can do about that, but you should use the asterisk instead of nothing (e.g. ['UID', '5:*']).

@eblume
Copy link
Author

eblume commented May 11, 2012

Ah, thanks - I'll give that a shot. Should perhaps the README be updated to reflect this? (it just says "#:" there.)

@mscdex
Copy link
Owner

mscdex commented May 11, 2012

Let me know if using the asterisk does work for you, I think I have all of the asterisks properly escaped now in the readme....

@eblume
Copy link
Author

eblume commented May 11, 2012

This is fine but it does sort of break with the Markdown philosophy of readable markup - but it gets the point across, I feel.

@mscdex mscdex closed this as completed May 11, 2012
Jivings pushed a commit to squarecat/node-imap that referenced this issue Nov 6, 2019
…ker-noon

Feature bespoke unsub hacker noon
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

Successfully merging a pull request may close this issue.

2 participants