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] Mimecast.com
- Previous message (by thread): [anti-abuse-wg] Mimecast.com
- Next message (by thread): [anti-abuse-wg] Mimecast.com
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
andre at ox.co.za
andre at ox.co.za
Wed Nov 4 11:40:54 CET 2015
On Wed, 4 Nov 2015 10:20:51 +0000 James Hoddinott <jhoddinott at cloudmark.com> wrote: > Hi Andre, > Hello James :) > I don't think they are Evil Corp and this is little more than spam > filtering on a role address (which you can debate ad-infinitum if you nope. no debate - simply broken if you advice on bounce to contact mr x and mr x auto bounces from the same ip/address > like). I did spot that your replies on this thread were flagged as > spam by us and since we provide them some services I dug in a little > more and can see that our systems had erroneously set the domain > hostacc.com [1] as spammy so I have fixed that up for you and I okay, no - not really understood or accepted? how come the same happened to 176.9.148.244 @cozahosts.com 209.17.190.102 at ns3.ox.co.za wetmy.com and all the others, every time that I send request to support at mimecast - magically: new server is also blocked... can you fix all my servers? surely all of my thousands of users all over the planet did not suddenly all attack mimecast? Some systems are on BSD, Some on Linux, Some on Unix, Some on Windows, etc It is extremely unlikely that everything by me was compromised all at the same time - and then ONLY to mail bomb mimecast.com... so, this shows me only one thing? - Malice. Do I (and everyone else) when they have a magical problem like this have to post on public lists and beg? Or is it not occam's razor? - Simple extortion for money? > reckon you should now be able to send your reports in to Mimecast > without issue (or at least, without this issue). > Thank you so much James, I do honestly and truly appreciate it from the bottom of my heart. But I am as stubborn as my email address, I need to understand why I need to know what is wrong, understand the situation and problem so that it can make sense to me, Also, I think that is is important to do things openly, so that everyone can understand what is going on as next week (or last week) maybe this also happened to someone else and if we know how to respond or what the issues are, we can help others and do the whole Kumbaya thing :) again thanks James :) andre > [1] This appears to be what your sending IP resolves to and what it > HELOs as. >
- Previous message (by thread): [anti-abuse-wg] Mimecast.com
- Next message (by thread): [anti-abuse-wg] Mimecast.com
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]