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

Issues with uid_tracking marking emails as read #45

Open
pemontto opened this issue Sep 24, 2019 · 1 comment · May be fixed by #46
Open

Issues with uid_tracking marking emails as read #45

pemontto opened this issue Sep 24, 2019 · 1 comment · May be fixed by #46

Comments

@pemontto
Copy link
Contributor

There are some issues with the new uid_tracking option. I expect the most common use for this config is so a mailbox can be used by normal users without this logstash-input-imap changing the state of messages.

Some issues currently:

  • Emails are always marked as READ (interrupts normal usage)
  • Inboxes with no UNSEEN/NOT SEEN messages aren't scanned if uid_tracking is on and there is no uid_last_value. E.g. using it on a Sent mailbox will produce no results as everything is already "SEEN"

I'm proposing a new flag mark_read which will default to true (maintaining current behaviour), but when enabled with uid_tracking will not change the email FLAGS.

@pemontto pemontto linked a pull request Sep 24, 2019 that will close this issue
@mikehwang
Copy link

Why have these PRs been not reviewed?

mikehwang pushed a commit to Parametric/logstash-input-imap that referenced this issue Apr 2, 2020
Issue: logstash-plugins/logstash-input-imap logstash-plugins#45
Issue: WAM-5
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