starred/cypht

Fork 0

mirror of https://github.com/cypht-org/cypht.git synced 2026-04-25 04:56:03 +03:00

[GH-ISSUE #412] Better handling of spam folder: Special folder, aggregate view, tag as "not spam", etc. #340

New issue

Open

opened 2026-02-25 21:34:47 +03:00 by kerem · 8 comments

kerem commented

2026-02-25 21:34:47 +03:00

Owner

Originally created by @marclaporte on GitHub (Jun 25, 2020).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/412

Originally assigned to: @jasonmunro on GitHub.

I received an email. Went in spam folder. I didn't think to check. It was an important email. Not spam. I had nothing prompting me to go check there. Not good.

We should:

Have a obvious way to see if there is new/unread spam.
Add Spam as a special folder like Trash and Sent, knowing that an external process is likely set up to move suspected spam.
Have a button to identify a message as "not spam" and move it back to relevant inbox. And if possible, teach the server that it's not spam (is there a standard for this?)

Thanks!

Originally created by @marclaporte on GitHub (Jun 25, 2020). Original GitHub issue: https://github.com/cypht-org/cypht/issues/412 Originally assigned to: @jasonmunro on GitHub. I received an email. Went in spam folder. I didn't think to check. It was an important email. Not spam. I had nothing prompting me to go check there. Not good. We should: - Have a obvious way to see if there is new/unread spam. - Add Spam as a special folder like Trash and Sent, knowing that an external process is likely set up to move suspected spam. - Have a button to identify a message as "not spam" and move it back to relevant inbox. And if possible, teach the server that it's not spam (is there a standard for this?) Thanks!

kerem added the

enhancement

label

2026-02-25 21:34:47 +03:00

kerem commented

2026-02-25 21:34:48 +03:00

Author

Owner

@dumblob commented on GitHub (Jun 25, 2020):

Have a button to identify a message as "not spam" and move it back to relevant inbox. And if possible, teach the server that it's not spam (is there a standard for this?)

If there is any standard for that, I'm ok with this proposal. But if not (and I don't know of any), I'm strongly against yeat another button (or any UI extension in this regard) because the functionality is equivalent to "move to another folder" (duplicating functionality is UX anti-pattern).

@dumblob commented on GitHub (Jun 25, 2020): >Have a button to identify a message as "not spam" and move it back to relevant inbox. And if possible, teach the server that it's not spam (is there a standard for this?) If there is any standard for that, I'm ok with this proposal. But if not (and I don't know of any), I'm **strongly against** yeat another button (or any UI extension in this regard) because the functionality is equivalent to "move to another folder" (duplicating functionality is UX anti-pattern).

kerem commented

2026-02-25 21:34:48 +03:00

Author

Owner

@Yamakasi commented on GitHub (Jun 27, 2020):

Have a button to identify a message as "not spam" and move it back to relevant inbox. And if possible, teach the server that it's not spam (is there a standard for this?)

If there is any standard for that, I'm ok with this proposal. But if not (and I don't know of any), I'm strongly against yeat another button (or any UI extension in this regard) because the functionality is equivalent to "move to another folder" (duplicating functionality is UX anti-pattern).

I thought directly, did Marc not asked for the same a couple of months ago ?

@Yamakasi commented on GitHub (Jun 27, 2020): > > > > Have a button to identify a message as "not spam" and move it back to relevant inbox. And if possible, teach the server that it's not spam (is there a standard for this?) > > If there is any standard for that, I'm ok with this proposal. But if not (and I don't know of any), I'm **strongly against** yeat another button (or any UI extension in this regard) because the functionality is equivalent to "move to another folder" (duplicating functionality is UX anti-pattern). I thought directly, did Marc not asked for the same a couple of months ago ?

kerem commented

2026-02-25 21:34:48 +03:00

Author

Owner

@marclaporte commented on GitHub (Oct 16, 2020):

Just happened again. spam folder is too hidden.

@marclaporte commented on GitHub (Oct 16, 2020): Just happened again. spam folder is too hidden.

kerem commented

2026-02-25 21:34:48 +03:00

Author

Owner

@ElvisAns commented on GitHub (Sep 23, 2022):

I join the thread... I hope to find a solution with your help

@ElvisAns commented on GitHub (Sep 23, 2022): I join the thread... I hope to find a solution with your help

kerem commented

2026-02-25 21:34:48 +03:00

Author

Owner

@marclaporte commented on GitHub (Sep 24, 2022):

Here is how Gmail and Roundcube do it:

@marclaporte commented on GitHub (Sep 24, 2022): Here is how Gmail and Roundcube do it: ![2022-09-24_122529](https://user-images.githubusercontent.com/1004261/192109135-c7e53197-a010-4043-961e-805ce610f9c3.png) ![2022-09-24_122152](https://user-images.githubusercontent.com/1004261/192109136-62a00592-a66a-45a0-a68c-0710bd82e119.png)

kerem commented

2026-02-25 21:34:48 +03:00

Author

Owner

@marclaporte commented on GitHub (Feb 27, 2023):

https://support.mozilla.org/en-US/kb/thunderbird-and-junk-spam-messages#w_tell-thunderbird-what-is-not-junk
http://kb.mozillazine.org/Junk_Mail_Controls

NonJunk is visible here:
https://datatracker.ietf.org/doc/rfc5232/
https://datatracker.ietf.org/doc/rfc9051/
https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/05/

@marclaporte commented on GitHub (Feb 27, 2023): https://support.mozilla.org/en-US/kb/thunderbird-and-junk-spam-messages#w_tell-thunderbird-what-is-not-junk http://kb.mozillazine.org/Junk_Mail_Controls NonJunk is visible here: https://datatracker.ietf.org/doc/rfc5232/ https://datatracker.ietf.org/doc/rfc9051/ https://datatracker.ietf.org/doc/draft-ietf-extra-imap4rev2/05/

kerem commented

2026-02-25 21:34:48 +03:00

Author

Owner

@marclaporte commented on GitHub (Mar 22, 2024):

Partially done: https://github.com/cypht-org/cypht/pull/704

@marclaporte commented on GitHub (Mar 22, 2024): Partially done: https://github.com/cypht-org/cypht/pull/704

kerem commented

2026-02-25 21:34:48 +03:00

Author

Owner

@marclaporte commented on GitHub (Oct 26, 2024):

The next step on this task is: "Have a button to identify a message as 'not spam' and move it back to relevant inbox. And if possible, teach the server that it's not spam (is there a standard for this?)"

All the email services I use offer a webmail. And from memory, they all have a way to mark "not spam" in the webmail. As of now, I need to login all of them one by one, find the messages and click "not spam". This is quite annoying as I am now accustomed to Cypht's unifed inbox. Thus, I want to do this in Cypht, and Cypht should inform mail server to adjust spam detection rules.

@marclaporte commented on GitHub (Oct 26, 2024): The next step on this task is: "Have a button to identify a message as 'not spam' and move it back to relevant inbox. And if possible, teach the server that it's not spam (is there a standard for this?)" All the email services I use offer a webmail. And from memory, they all have a way to mark "not spam" in the webmail. As of now, I need to login all of them one by one, find the messages and click "not spam". This is quite annoying as I am now accustomed to Cypht's unifed inbox. Thus, I want to do this in Cypht, and Cypht should inform mail server to adjust spam detection rules.