We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2014-11-20 23:44:05 +0200 |
This is missing currently from the email client. Where possible (depending on backend), email client should allow for marking of emails as SPAM.
2 | No.2 Revision |
This is missing currently from the email client.
Where possible (depending on backend), email client should allow for marking of emails as SPAM.SPAM
and consequently move them to the appropriate SPAM folder.
3 | No.3 Revision |
This is missing currently from the email client. Where possible (depending on backend), email client should allow for marking of emails as SPAM and consequently move them to the appropriate SPAM folder.
Upon marking an email as SPAM, the user must have the chance to identify the spam folder as such (if no spam folder has been chosen by the user yet); the mail client by default must try to identify such folder based on known names (spam, junkmail, ...).
The point of this is to improve capability of mail client users to remove spam.
4 | No.4 Revision |
This is missing currently from the email client. Where possible (depending on backend), email client should allow for marking of emails as SPAM and consequently move them to the appropriate SPAM folder.
Upon marking an email as SPAM, the user must have the chance to identify the spam folder as such (if no known spam folder is available / has been chosen by the user yet); the mail client by default must try to identify such folder based on known names (spam, junkmail, ...).
The point of this is to improve capability of mail client users to remove spam.
5 | No.5 Revision |
This is missing currently from the email client. Where possible (depending on backend), email client should allow for marking of emails as SPAM and consequently move them to the appropriate SPAM folder.
Upon marking an email as SPAM, the user must have the chance to identify the spam folder as such (if no known spam folder is available / has been chosen by the user yet); the mail client by default must try to identify such folder based on known names (spam, junkmail, ...).names, for example "spam", "junkmail", ....
The point of this is to improve capability of mail client users to remove spam.
This is missing currently from the email client. Where possible (depending on backend), email client should allow for marking of emails as SPAM and consequently move them to the appropriate SPAM folder.
Upon marking an email as SPAM, the user must have the chance to identify the spam folder as such (if no known spam folder is available / has been chosen by the user yet); the mail client by default must try to identify such folder based on known names, for example "spam", "junkmail", ....
The point of this is to improve capability of mail client users to remove spam.
7 | No.7 Revision |
This is missing currently from the email client. Where possible (depending on backend), email client should allow for marking of emails as SPAM and consequently move them to the appropriate SPAM folder.
Upon marking an email as SPAM, the user must have the chance to identify the spam folder as such (if no known spam folder is available / has been chosen by the user yet); the mail client by default must try to identify such folder based on known names, for example "spam", "junkmail", ....
The point of this is to improve capability of mail client users to remove spam.