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/[email protected]/
[anti-abuse-wg] Microsoft New Abuse Policies
- Previous message (by thread): [anti-abuse-wg] Interesting email abuse header extract
- Next message (by thread): [anti-abuse-wg] New on RIPE Labs: Report from the workshop on Coordinating Attack Response at Internet Scale (CARIS2)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ac
ac at main.me
Sun Jun 2 10:01:53 CEST 2019
Hi All, Today it is me, tomorrow it may be you? Microsoft has new abuse policies in terms of email abuse and it is interesting insofar as it is mysterious Which is perfectly fine, it is Microsoft's infrastructure and they may do and decide whatever they want - But - it is important to understand ABUSE in all it's forms. I am saying that this Microsoft behavior is Abuse in itself as they leveraged their monolopy in operating systems into an eventual email dominance and their behavior is abuse. Anyway, you will recall that I posted here about the AI at Microsoft, as I (a human) took 20 minutes to complete their web form (and solve their stupid capcha) and the Microsoft response was so very quickly: "no" Well, I escalated and escalated the "no we are not going to accept relay from you, internationally from any @microsoft infrastructure" for an IP number and sender domains that are 100% clean and has, in ten years, not even has a single abuse complaint from anywhere: http://multirbl.valli.org/lookup/5.9.29.165.html I received the final Microsoft response this morning after many email exchanges, and with different "people": +++++++++++++++++++++++++++++++++ Hello, As previously stated, your IP do not qualify for mitigation at this time. I do apologize, but I am unable to provide any details about this situation since we do not have the liberty to discuss the nature of the block. At this point, I would suggest that you review and comply with Outlook.com's technical standards. This information can be found at https://postmaster.live.com/pm/postmaster.aspx <https://postmaster.live.com/pm/postmaster.aspx> We regret that we are unable to provide any additional information or assistance at this time. Best regards, Outlook.com Deliverability Support +++++++++++++++++++++++++++++++++++++++ The staff are "not at liberty" i.e FREE and "at this point" They are not referring me to RFC as my emails comply with RFC, IETF and all standards, so there is no 'technical' reason... or to any abuse by myself (as that does not exist) instead I am being directed to copious amounts of "policy" where I have to work through pages of drivel with an end result of them still saying "no" and with a result of wasting my time. Of course, as I already said: Microsoft can refuse to accept email from anyone they choose and for any reason they choose. So, there is nothing that I can do or say and it is what it is. Andre
- Previous message (by thread): [anti-abuse-wg] Interesting email abuse header extract
- Next message (by thread): [anti-abuse-wg] New on RIPE Labs: Report from the workshop on Coordinating Attack Response at Internet Scale (CARIS2)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]