The very short version: Microsoft are ridiculously heavy handed with their antispam, etc, mechanisms. As a result, they more frequently than not simply block mail from all but the largest mail service providers – and conversely, their own mail users simply fail to receive a *lot* of mail which they should be getting.

The problem seems to be with their implementation of “sender reputation”, which is basically the ratio of “good” emails sent from your mail domain compared to “bad” ones (spam, etc). Getting a decent insight into a domains “reputation” requires, as you might imagine, a decent volume of mail from that domain to sample from.

This can make building that reputation difficult for smaller mail providers like our own. But there several other techniques and protocols which can mitigate the issue – Things like SPF, DKIM and properly configured reverse DNS. We employ *all* of these techniques.

Yet, for the ~20 years I’ve been running our own mail services for myself, my own businesses and hosted clients, M$ have consistently and *repeatedly* simply blocked our domains and IP ranges for no readily apparent reason/s. We’ve *never* sent out spam (we have server-side mechanisms to both monitor and mitigate that).

Sooo, for the last couppla decades I’ve needed to submit about half a dozen requests per year to them to have us removed from their block lists. Of course, the only way I know such a request is needed again is when email to an M$ domain has already failed. By then, some damage is already done. And it’s historically taken at least 48 hours to get any response to the requests…

…Until this year. I got an email a few months ago from an old friend I’d not heard from in ages. From her Hotmail mail account. My reply to her bounced, so I submitted another request to M$ to have the block removed. This time, I noticed that a lot of their relevant web pages were 404’ing and I had to go to some effort to find the requisite form. Anyways, a couple of days later I got an email back telling me we weren’t blocked (that’s “normal – I think it means our sender domain is okay but the block was against our IP range (our IPs are provided from ranges belonging to the provider of our servers). But I’ve received nothing since.

So that’s it. I’m done repeatedly going through these motions for a brain-dead service provider who clearly don’t give a shit about other providers in their space, or their own users. I give up, and from now on simply do not support sending mail to any M$ domain.

A quick search today for others experiencing the same problems produced this thread in an M$ discussion forum. Don’t just take my word for it – read through the thread 🙂

In summary, if you use any of the M$ mail services – like Outlook, Hotmail, MSN, Live – grab yourself an account at any other provider – gmail is good – and start phasing out your usage of the M$ one/s sooner rather than later.

CME - Second Life inworld store

Visit our Second Life inworld store to see and demo our range of products.

CME - Second Life Marketplace store

Visit our Second Life Marketplace store to see our range of products.

CandM World

Our OpenSimulator world (grid).

LL Designs - Second Life inworld store

Visit our Second Life inworld store to see and demo our range of products.

LL Designs - Second Life Marketplace store

Visit our Second Life Marketplace store to see our range of products.

Soooo, apparently Discord had a glitch and blocked me from “talking” in any WaS channels right about the time WaS tried to be honest and open by posting screenshots of my chat with their representative (user “was” with tagline “Message me for support!”). Bloody Discord…

Soooo, let’s help out here by outlining what happened. And while we’re at it, we’ll let you know why Corrade is so awesome and why you should definitely use it. If you’re not good at detecting sarcasm, read the following more carefully than usual 😉

Anyways, so we started using Corrade – WaS’ bot controller software – a little over a year ago when we realised that SL doesn’t allow for scripts inviting users to non-open groups. We needed this for our rental platform. Once we discovered Corrade, we started using it for a bunch of other stuffs too.

I like to know everything I can about the stuff I work with – it’s just how I’m built, I guess. To that end, I joined all of the useful-looking SL groups related to Corrade, and their Discord “server”.

I also created an account on their MantisBT issue tracker. And noticed right away that I couldn’t see *any* content there. Just an empty framework.

Anyways, a week or so ago they posted in their Discord that they were shutting down the Corrade channel due to “low traffic”, which is odd as that channel generated, by far, the most discussion of any of their other methods of contact. They said we should start using other discussion channels or just submit tickets to their issue tracking system.

As we no longer use SL, and can’t see any issues being tracked in their Mantis, this meant I was now completely in the dark about Corrade stuffs. And note that Corrade is not open source, so I also can’t just read the source code for any enlightenment.

So I contacted “was” in Discord to ask about their Mantis appearing empty to me. Since they apparently think that posting screenshots of a discussion is the way to disclose stuff (they literally posted them to their new “disclosures” Discord channel), we’re just gonna do the same here…

At least they left these screenshots intact – the only other post to the same “disclosures” channel is an exchange they apparently had with Linden Lab, but those are heavily redacted (perhaps WaS aren’t terribly familiar with the meaning of the word “disclosure”?).

While we’re at it, might as well also attach the text file (that WaS themselves posted in their Discord) of an “office hour” meeting. It’s a long read, so here’s the key takeaways: at one point, Corrade wouldn’t run if the WaS website was down; Corrade has historically “phoned home” with data that was being run through it (including IM chat content); they removed that code… so they say… and it’s closed source so we gots ta take their word for that; they’d prefer to keep it all easier to run for unskilled users (despite that corrade is a pain in the ass to code, etc, for to begin with) than to introduce any basic security mechanisms; they’d love you to connect corrade to IoT so you can, for instance, say “Alexa: restart my region” (if you don’t get the irony here, re-read this entire paragraph until you do); if you even remotely speak out to challenge them, they’ll silence you any way they can.

Pretty sure ’nuff said. We’ve dumped Corrade. Strongly suggest you do same (or stay away from it / them if you’re not already unfortunate enough to have invested anything in it).

Update…

Thanks to Arrhen, whose comment reminded me to *finally* add this update…

On the 25th of March 2024, I got a few emails from our site comment thingie. I’ve since deleted the emails (which is odd – I usually don’t do that… but they were essentially rubbish anyways), but they did point me to the following, posted on his Discord the same day…

=====

Good day!

A funny read perhaps, from Mattt, a person running a 5 person grid, has a crashing WordPress installation, yet has the time to write hit-pieces on us: https://candmworld.com/wizardry-and-steamworks-corrade

and our response:

https://grimore.org/wiki/public_relations/hate_group_2

Too bad that Mattt deletes comments too fast because we tried to pick up the conversation on his website but the comment got deleted. Weren’t you supposed to be open to discussion, unlike us?

Be vigilant!

=====

Note that the “crashing WordPress installation” he refers to is because there *is* a crash related to certain formats (or some such) of dodgy email addresses spammers sometimes use – they are trapped by one of the antispam techniques I implemented in the contact form code, but for some reason they sometimes cause the site to crash. Since it only happens under those circumstances, I’ve never put a lot a lot of weight on addressing it. I guess I should / will one day. But the point is that he also left several post comments (which require approval, and since they were basically rubbish I declined to do so) on the same day using clearly fake names and email addresses…

At no point did Lance try to engage me in any kind of discussion, so I sent him a couppla messages on Discord. He took the opportunity to post screenshots of some of them to his Discord group thingie (on the 26th of March)…

Annnnd, he also posted this…

I’m yet to hear from any authority, let alone SWAT. Team America woulda been *super* cool 🙂

In case you don’t notice it in the discussion thread below, note that we now use SecondBot and (particularly now the new and quite cool events system has been implemented) I thoroughly recommend that 🙂

CME - Second Life inworld store

Visit our Second Life inworld store to see and demo our range of products.

CME - Second Life Marketplace store

Visit our Second Life Marketplace store to see our range of products.

CandM World

Our OpenSimulator world (grid).

LL Designs - Second Life inworld store

Visit our Second Life inworld store to see and demo our range of products.

LL Designs - Second Life Marketplace store

Visit our Second Life Marketplace store to see our range of products.