Handling abuse complaints (was: Abusive behavior by Google Inc)
On Thu, Apr 14, 2016 at 5:38 PM, <andre@ox.co.za> wrote:
Basically, if I receive a bounce from gmail saying that they think my email is spam, i sent the same bounce to my client - so that they can fix / adjust their behavior...
From the rant I found actually this interesting.
So, instead of investigating yourself and terminating the spamming customer you forward the complaint (in the worst case unedited) to the customer for listwashing? What an idea! I hope the spammers don't find your service, as you'd land in quite a few filters. This might cause even more customers leaving. esa -- Mr Esa Laitinen Skype: reunaesa Yahoo: reunaesa Mobile: +4178 838 57 77
On Thu, 14 Apr 2016 18:07:37 +0200 Esa Laitinen <esa@laitinen.org> wrote:
On Thu, Apr 14, 2016 at 5:38 PM, <andre@ox.co.za> wrote:
Basically, if I receive a bounce from gmail saying that they think my email is spam, i sent the same bounce to my client - so that they can fix / adjust their behavior...
From the rant I found actually this interesting. So, instead of investigating yourself and terminating the spamming customer you forward the complaint (in the worst case unedited) to the customer for listwashing? What an idea! I hope the spammers don't find your service, as you'd land in quite a few filters. This might cause even more customers leaving.
sorry, i realize that many of you probably have zero/little/no technical skills... I apologize it is my fault for not typing/communicating more clearly :( - what i obviously meant was that I do not re-write email headers. Email bounces are generally returned to Return-path: I do not read clients email and should i receive an actual complaint at my abuse-c :) I will deal with that ...
Sigh - I'm having a throwback moment to the worse parts of 90s nanae and spam-l with this whole thread. At least nanae had cat stories and pun cascades to balance out the weirdness. --srs
On 14-Apr-2016, at 9:37 PM, Esa Laitinen <esa@laitinen.org> wrote:
So, instead of investigating yourself and terminating the spamming customer you forward the complaint (in the worst case unedited) to the customer for listwashing?
What an idea! I hope the spammers don't find your service, as you'd land in quite a few filters. This might cause even more customers leaving.
On Thu, 14 Apr 2016 21:50:22 +0530 Suresh Ramasubramanian <ops.lists@gmail.com> wrote:
Sigh - I'm having a throwback moment to the worse parts of 90s nanae and spam-l with this whole thread. At least nanae had cat stories and pun cascades to balance out the weirdness.
well, it does help with increasing knowledge... at the very least it will make people understand how it all works, this helps to form POV and to educate, and all that is not a bad thing - even I learn that I must not do ranty type posts :) learning, for example: When I say that "I receive a spam bounce" I mean my email server receives it and I forward the spam bounce to the sender without re-writing headers... Esa Laitinen thought that this was 'bad' or wrong, but this is in fact how things work... even at @laitinen.org if I were admin mailserver laitinen.org and esa@laitinen.org receives a bounce notice for SPAM from wherever - I am not going to re-write the bounce... and YES, I am going to deliver the bounce to esa@laitinen.org NO, this is not wrong and no, I am a mail server, so this is what I do - deliver email... I do not worry about abuse or clients or anything other than delivering email... What is interesting is that Esa chooses to focus on finding problems with my behavior, post or actions instead of commenting on the elephant in the room... I do apologize if some of my post is rant like :) andre
--srs
On 14-Apr-2016, at 9:37 PM, Esa Laitinen <esa@laitinen.org> wrote:
So, instead of investigating yourself and terminating the spamming customer you forward the complaint (in the worst case unedited) to the customer for listwashing?
What an idea! I hope the spammers don't find your service, as you'd land in quite a few filters. This might cause even more customers leaving.
participants (3)
-
andre＠ox.co.za -
Esa Laitinen -
Suresh Ramasubramanian