Advertisement
Guest User

Untitled

a guest
Dec 23rd, 2015
120
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.47 KB | None | 0 0
  1. Send mailop mailing list submissions to
  2. mailop@mailop.org
  3.  
  4. To subscribe or unsubscribe via the World Wide Web, visit
  5. https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
  6. or, via email, send a message with subject or body 'help' to
  7. mailop-request@mailop.org
  8.  
  9. You can reach the person managing the list at
  10. mailop-owner@mailop.org
  11.  
  12. When replying, please edit your Subject line so it is more specific
  13. than "Re: Contents of mailop digest..."
  14.  
  15.  
  16. Today's Topics:
  17.  
  18. 1. WHAT can be done about Ezoic and their spamming through
  19. Google? (Anne Mitchell)
  20. 2. Re: WHAT can be done about Ezoic and their spamming through
  21. Google? (mikea)
  22. 3. Re: WHAT can be done about Ezoic and their spamming through
  23. Google? (Geordie Guy)
  24. 4. Re: WHAT can be done about Ezoic and their spamming through
  25. Google? (Noel Butler)
  26.  
  27.  
  28. ----------------------------------------------------------------------
  29.  
  30. Message: 1
  31. Date: Tue, 22 Dec 2015 09:14:51 -0700
  32. From: Anne Mitchell <amitchell@isipp.com>
  33. To: mailop <mailop@mailop.org>
  34. Subject: [mailop] WHAT can be done about Ezoic and their spamming
  35. through Google?
  36. Message-ID: <489FA53E-93AB-4138-A244-CDDAF6C28F20@isipp.com>
  37. Content-Type: text/plain; charset=us-ascii
  38.  
  39. We are repeatedly being spammed by Ezoic, and we have reported them to their providers (enom, scalr, Amazon and Google multiple times).
  40.  
  41. Just *what* can be done about a non-moving target spammer who is sending through Google (already reported to them) and hosting on Amazon? (ditto.)
  42.  
  43. I don't mean at the local level, I mean about getting them shut down (or at least listed).
  44.  
  45. Anne
  46.  
  47.  
  48.  
  49.  
  50.  
  51.  
  52. ------------------------------
  53.  
  54. Message: 2
  55. Date: Tue, 22 Dec 2015 10:28:12 -0600
  56. From: mikea <mikea@mikea.ath.cx>
  57. To: mailop <mailop@mailop.org>
  58. Subject: Re: [mailop] WHAT can be done about Ezoic and their spamming
  59. through Google?
  60. Message-ID: <20151222162812.GA59028@mikea.ath.cx>
  61. Content-Type: text/plain; charset=us-ascii
  62.  
  63. On Tue, Dec 22, 2015 at 09:14:51AM -0700, Anne Mitchell wrote:
  64. > We are repeatedly being spammed by Ezoic, and we have reported them to their providers (enom, scalr, Amazon and Google multiple times).
  65. >
  66. > Just *what* can be done about a non-moving target spammer who is sending through Google (already reported to them) and hosting on Amazon? (ditto.)
  67. >
  68. > I don't mean at the local level, I mean about getting them shut down (or at least listed).
  69.  
  70. At this point, all I can think of is this:
  71.  
  72. If you don't complain, then they can't ignore you.
  73.  
  74. Google and Amazon are "too big to be shut down", "too important to be
  75. blocked", and "too big to be influenced from outside". That's a bad
  76. combination.
  77.  
  78. --
  79. Mike Andrews, W5EGO
  80. mikea@mikea.ath.cx
  81. Tired old sysadmin
  82.  
  83.  
  84.  
  85. ------------------------------
  86.  
  87. Message: 3
  88. Date: Tue, 22 Dec 2015 20:14:13 +0000
  89. From: Geordie Guy <Geordie.Guy@covermore.com.au>
  90. To: Anne Mitchell <amitchell@isipp.com>
  91. Cc: mailop <mailop@mailop.org>
  92. Subject: Re: [mailop] WHAT can be done about Ezoic and their spamming
  93. through Google?
  94. Message-ID: <16F18A22-18A6-46DB-AC07-051B3EE4FDC3@covermore.com.au>
  95. Content-Type: text/plain; charset="us-ascii"
  96.  
  97. You only control the local level. As a postmaster you're responsible for delivery to and from your domains, not mine, not anyone else's. Get your opsec team to ban their AS at your firewall and go about your day.
  98.  
  99. Sent from my mobile. Please excuse any unusual brevity or typos while I'm on the go.
  100.  
  101. > On 23 Dec 2015, at 3:19 AM, Anne Mitchell <amitchell@isipp.com> wrote:
  102. >
  103. > We are repeatedly being spammed by Ezoic, and we have reported them to their providers (enom, scalr, Amazon and Google multiple times).
  104. >
  105. > Just *what* can be done about a non-moving target spammer who is sending through Google (already reported to them) and hosting on Amazon? (ditto.)
  106. >
  107. > I don't mean at the local level, I mean about getting them shut down (or at least listed).
  108. >
  109. > Anne
  110. >
  111. >
  112. >
  113. >
  114. > _______________________________________________
  115. > mailop mailing list
  116. > mailop@mailop.org
  117. > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
  118.  
  119.  
  120.  
  121. ------------------------------
  122.  
  123. Message: 4
  124. Date: Wed, 23 Dec 2015 09:26:05 +1000
  125. From: Noel Butler <noel.butler@ausics.net>
  126. To: mailop@mailop.org
  127. Subject: Re: [mailop] WHAT can be done about Ezoic and their spamming
  128. through Google?
  129. Message-ID: <30d0730fb78b2be50dc5e686265da9ba@ausics.net>
  130. Content-Type: text/plain; charset=US-ASCII; format=flowed
  131.  
  132. On 23/12/2015 02:28, mikea wrote:
  133. > On Tue, Dec 22, 2015 at 09:14:51AM -0700, Anne Mitchell wrote:
  134. >> We are repeatedly being spammed by Ezoic, and we have reported them to
  135. >> their providers (enom, scalr, Amazon and Google multiple times).
  136. >>
  137. >> Just *what* can be done about a non-moving target spammer who is
  138. >> sending through Google (already reported to them) and hosting on
  139. >> Amazon? (ditto.)
  140. >>
  141. >> I don't mean at the local level, I mean about getting them shut down
  142. >> (or at least listed).
  143. >
  144. > At this point, all I can think of is this:
  145. >
  146. > If you don't complain, then they can't ignore you.
  147. >
  148. > Google and Amazon are "too big to be shut down", "too important to be
  149. > blocked", and "too big to be influenced from outside". That's a bad
  150. > combination.
  151.  
  152.  
  153. Rubbish! no-ones too big to be blocked, it's this type of attitude that
  154. allows the bigger players to sit back and say "ahhhhh so what" when you
  155. do complain.
  156.  
  157. I've blocked google before and I'll block them again in a flash if the
  158. level of crap from them warrants it. Usually only a short period of time
  159. does the trick.
  160.  
  161. That said, you do need to give them reasonable time to reach your
  162. complaint and act, just because they are one of the larger mail
  163. providers, doesnt mean they have an army of abuse@ desk people, so you
  164. need to be a little patient.
  165.  
  166. You should already have implemented local measures for general anti spam
  167. anyway, if not use spamassassin and if it doesnt by default catch them,
  168. its very easy to write custom rules if you need to, even if
  169. google/amazon and co do nothing, your problems still solved.
  170.  
  171.  
  172. --
  173. If you have the urge to reply to all rather than reply to list, you best
  174. first read http://members.ausics.net/qwerty/
  175.  
  176.  
  177.  
  178. ------------------------------
  179.  
  180. Subject: Digest Footer
  181.  
  182. _______________________________________________
  183. mailop mailing list
  184. mailop@mailop.org
  185. https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
  186.  
  187.  
  188. ------------------------------
  189.  
  190. End of mailop Digest, Vol 98, Issue 27
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement