On Sat, Jan 28, 2017 at 03:28 pm, Shal Farley wrote:
I think the issue is what the users need to be educated about. And that varies with the email service they're using as well as the interface they use to access that service. Desktop web browser, mobile site via mobile web browser, mobile app[1], desktop IMAP/POP application. Others?
?I have to say that I can only partially agree with this, as I don't think what an end user needs to know has much of anything to do with what's going on "under the hood."
Most e-mail clients and web interfaces (mobile is, indeed, a thing of its own and would require more research) have relatively straightforward ways to classify or declassify messages as spam. ?
I don't think we should be trying to take a tutorial style approach so much as making users aware that they need to find out how their e-mail interface of choice can classify/declassify a given message as being spam and what whitelisting is and that they should consider using this mechanism for their e-mail interface of choice when they get the welcome message. ?I also know that many will ignore this information, but at least it will have been presented. ?I get really frustrated when people complain that "well, they don't know that" when you've included the information, in writing, and it's not buried in a message that looks like a legal contract. ?We can't literally speak to the users and the communication method of the medium we're talking about is text-based.
Of course, this is a Catch-22 affair for users who are unsophisticated and who do not ever look in their spam folders to see if something has landed there should not have. ?I don't think that this particular conundrum has an answer, let alone an easy one.
Brian
