Re: [anti-abuse-wg] Abusive behavior by Google Inc
This isn't quite mailop but anyway - what specifically do you mean by replace here? Do you strip mime parts that you consider spam or malware and replace them with a suitable message? And is the gmail mta not reacting well to that? Examples would be interesting - certainly much more interesting than a vague rant. --srs
On 14-Apr-2016, at 7:17 PM, andre@ox.co.za wrote:
Hello,
Incase anyone receives weird NON RFC bounces, from @gmail.com customers saying:
Technical details of permanent failure: read error: generic::failed_precondition: read error (0): error
What this means is:
Google Inc does REPLACE the "Blocked for abuse / spam /scams / phish / virus / spyware messages from the various filters
and sens a cryptic non RFC message to their users implying that the receivers email server is broken in some way....
This is truly EVIL of Google to do...
As they, Google are the ones sending PHISH / VIRUS/ SCAMS / SPAM!
Example: @209.85.218.43
http://www.scammed.by/scam.php?id=185816
Instead of SOLVING the abuse - Google chooses to send CRYPTIC technical failure messages...
Because they are a monopoly and they are simply just too large to care??
Yes, of course!
Andre
On Thu, 14 Apr 2016 19:51:27 +0530 Suresh Ramasubramanian <ops.lists@gmail.com> wrote:
This isn't quite mailop but anyway - what specifically do you mean by replace here?
Yes, but is is an abuse wok group - it is important that the group also discusses abuse, more so if their is abusive behavior from a huge multinational.
Do you strip mime parts that you consider spam or malware and replace them with a suitable message? And is the gmail mta not reacting well to that?
Examples would be interesting - certainly much more interesting than a vague rant.
Not a vague rant at all - the original post already contains the information. Gmail is behaving poorly/abusively. maybe you require me to add additional information? - as there is ZERO chance that you do not know what I am complaining about... I do wonder why you are not simply replying honestly and openly? ... Gmail customer sends email from Gmail to @ox.co.za ox.co.za responds: Listed at SORBS Currently sending SPAM! Gmail sends "improved" bounce report to Gmail customer: example:
Date: 14 April 2016 at 14:09:39 SAST To: customer@gmail.com
Delivery to the following recipient failed permanently:
andre@ox.co.za
Technical details of permanent failure: read error: generic::failed_precondition: read error (0): error
----- Original message -----
--srs
andre
On 14-Apr-2016, at 7:17 PM, andre@ox.co.za wrote:
Hello,
Incase anyone receives weird NON RFC bounces, from @gmail.com customers saying:
Technical details of permanent failure: read error: generic::failed_precondition: read error (0): error
What this means is:
Google Inc does REPLACE the "Blocked for abuse / spam /scams / phish / virus / spyware messages from the various filters
and sens a cryptic non RFC message to their users implying that the receivers email server is broken in some way....
This is truly EVIL of Google to do...
As they, Google are the ones sending PHISH / VIRUS/ SCAMS / SPAM!
Example: @209.85.218.43
http://www.scammed.by/scam.php?id=185816
Instead of SOLVING the abuse - Google chooses to send CRYPTIC technical failure messages...
Because they are a monopoly and they are simply just too large to care??
Yes, of course!
Andre
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In message , andre@ox.co.za writes
... Gmail customer sends email from Gmail to @ox.co.za
ox.co.za responds: Listed at SORBS Currently sending SPAM!
Gmail sends "improved" bounce report to Gmail customer:
example:
Date: 14 April 2016 at 14:09:39 SAST To: customer@gmail.com
Delivery to the following recipient failed permanently:
andre@ox.co.za
Technical details of permanent failure: read error: generic::failed_precondition: read error (0): error
----- Original message -----
in order to comment on the RFC compliance of this message (assuming that this was in any way relevant to RIPE) it would be necessary to provide the raw message with all headers intact (preferably as a text file offlist, perhaps on a web server somewhere as a .txt file to avoid any mangling) the quoting process has probably collapsed down some of the MIME structures making it hard to determine who created what create a test example if you are concerned about PII/data-protection because mangling/redacting messages can often cause misdiagnosis - -- richard Richard Clayton Those who would give up essential Liberty, to purchase a Benjamin little temporary Safety, deserve neither Liberty nor Safety. Franklin -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBVw+vOju8z1Kouez7EQLBBACfZ917gyNxOhNIZtEl+rhCYW4taB8Ani4/ Y9YcQUD4cZnrlqY11PGXNG7O =U0xn -----END PGP SIGNATURE-----
participants (3)
-
andre＠ox.co.za -
Richard Clayton -
Suresh Ramasubramanian