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

already readed mails stay in the inbox #353

Closed
webratte opened this issue Jul 4, 2018 · 13 comments
Closed

already readed mails stay in the inbox #353

webratte opened this issue Jul 4, 2018 · 13 comments
Labels

Comments

@webratte
Copy link

@webratte webratte commented Jul 4, 2018

If I receive a (replyed) message, this message is shown in the inbox (k9 on my normal device or Thundrbird) until DC come online on my test device. Then, if DC come online, this message will moved to the "DeltaChat" folder.

I think this is the normal behavior.

But if I I read this message first in K9 or Thunderbird on my PC before DC come online this message will not trigger a push message notification in DC and also this message will not moved to the "DeltaChat" folder.

Not even if I mark it as unread manually.

DC Version 0.18.2

@Hocuri

This comment has been minimized.

Copy link
Collaborator

@Hocuri Hocuri commented Jul 6, 2018

Personally, I think that it makes sense that "old" mails stay where they are and only new ones are moved. I would even be confused if mails that have always been in the inbox were moved to another folder when DC is installed.

@webratte

This comment has been minimized.

Copy link
Author

@webratte webratte commented Jul 6, 2018

I don't agree.
This mails are part of a chat history.
And I think its more confused if a few mails of this chat history in the DeltaChat folder.

And a few (maybe readed by accident because the push notification in k9 on the same device was faster then DC) are in the inbox.

And another thing.
I would like to mark all DC mails as read via sieve or server side filter (I use a explicitly mailadress for DC). If DC would treat this mails as new (push and move) e.G. by compare if this mail already in the locale history of the device.

I never would notice this mails in other mail clients. Only in DC. And so it would feel like a stand alone messenger.
Not like a mail client 😉

@testbird

This comment has been minimized.

Copy link
Contributor

@testbird testbird commented Jul 6, 2018

@webratte

This comment has been minimized.

Copy link
Author

@webratte webratte commented Jul 7, 2018

@testbird

This comment has been minimized.

Copy link
Contributor

@testbird testbird commented Jul 7, 2018

Well, most of the things are already there in one way or the other. But the alignment of all parts is going to deliver a simple and reliable user experience more likely than ad-hock special case improvements.

@testbird

This comment has been minimized.

Copy link
Contributor

@testbird testbird commented Jul 7, 2018

The strategy has been compiled from a lot of issues, and there is no need to implement all (e.g. 2xPUSH) in one go to make things work nicely.

@webratte

This comment has been minimized.

Copy link
Author

@webratte webratte commented Jul 11, 2018

Another way for me would be to move all incoming chat mails to the "DeltaChat" folder via filter.
Then I can exclude this folder from push in K9.

But this mails need more then 10 minutes to be pushed to DC.
Don't you watch the "DeltaChat" folder for push?

K9 pushed ALL Folders immediately if enabled.

@testbird

This comment has been minimized.

Copy link
Contributor

@testbird testbird commented Jul 12, 2018

That scheme is also included in https://github.com/deltachat/deltachat-core/wiki/IMAP-strategy, but as you wrote, it needs multiple idle/push connections (2xPUSH requirement on deltachat and the server), and would thus only make sense in a second step.
deltachat/deltachat-core#117

@webratte

This comment has been minimized.

Copy link
Author

@webratte webratte commented Jul 12, 2018

@testbird

This comment has been minimized.

Copy link
Contributor

@testbird testbird commented Jul 12, 2018

An there so much issues releated to each other...

Yes, that's the reason the wiki documens exist... To stay ahead of them and find the most consistent solution.

Thank you for reporting, and even more for thinking about solutions!
It's good to see your thoughts support the documented strategy.

@webratte

This comment has been minimized.

Copy link
Author

@webratte webratte commented Jul 12, 2018

@testbird

This comment has been minimized.

Copy link
Contributor

@testbird testbird commented Jul 12, 2018

You're welcome. :-)

@r10s

This comment has been minimized.

Copy link
Member

@r10s r10s commented Oct 13, 2018

targeted by https://github.com/deltachat/deltachat-core/milestone/2

closing this for now here, of course, the discussion can go on in the new support forum at https://support.delta.chat

@r10s r10s closed this Oct 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.