This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] Abuse: Too big to fail
- Previous message (by thread): [anti-abuse-wg] Abuse: Too big to fail
- Next message (by thread): [anti-abuse-wg] Abuse: Too big to fail
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Esa Laitinen
esa at laitinen.org
Mon Jun 19 12:11:10 CEST 2017
On Mon, Jun 19, 2017 at 10:49 AM ox <andre at ox.co.za> wrote: > > As I said: All ethical, honest and functional blocklists lists Twitter > as a Spammer. - It seems that at least 25% do actually list Twitter as a > spammer, and that is quite a lot. So maybe there is hope after all? > While I can certainly believe Twitter is a spam enabler, I did a small test. I created a new twitter account, but didn't confirm the account. I cannot send messages to this account from my other twitter account. So, I couldn't make twitter to facilitate email spam in this case. I do get email from Twitter when somebody sends me a direct message to my real twitter account. I chose to receive these notifications, thus the emails are not spam, and it would be wrong of me to report those emails as spam, even if the direct message is spam. Question raises: does the user you were using as an example have a twitter account connected with that email address? And has he selected to receive emails for direct messages (or something else) in twitter? Yours, esa -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/anti-abuse-wg/attachments/20170619/0bf253a0/attachment.html>
- Previous message (by thread): [anti-abuse-wg] Abuse: Too big to fail
- Next message (by thread): [anti-abuse-wg] Abuse: Too big to fail
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]