Plenty of advice here, which I'm certain is well intended, but it feels like we're victim blaming here.
Things like "you cannot mix marketing and transactional email" are good advice, but they do nothing if you're using different subdomains but the same infrastructure (IP address) to send them out.
Microsoft is simply trying to squeeze smaller operators out of the market.
I run an open source project, we send out transaction emails from ome subdomain, and a newsletter to 50K+ subscribers once every 3 months.
I can't afford to pay for different/dedicated IO addresses for each. We use Scaleway for email delivery and it's constant trouble with two providers: qq.com who don't give a damn about non-chinese senders, and Microsoft, who are simply trying to break the ipen internet.
Before, we were on AWS SES. Guess what, we didn't even bother using different subdomains. We also didn't have dedicated IPs. Yet Microsoft did not block us because the sender IP was AWS.
It's pay to play, as simple as that.
Fortunately, we're an open source project, not a business. So when people reach out, I simply explain to them that they have chosen a mail provider that is openly hostile to small volunteer-run projects like us and that that choice has consequences. No emails for you.
IMHO we need to be more vocal about what's really going on here (the rent-seeking on the open internet by big tech), and less victim blaming (what about dns-sec).
Absolutely agreed. These two big corporate players with the biggest market-share are actively ruining the email ecosystem for their profit. I wish people would drop them and stop choosing them. Hopefully, the EU may soon do so.
Hi Joost, FreeSewing is a great idea!
I personally don't know anything about sewing, but I got interested in it after visiting the website.
However, what attracts me to it is its software modeling.
No matter how hard I try, I cannot make two pairs of jeans that are identical.
Same pattern, same denim, same person making them (me), they don't fit/feel the same.
Consistent results when using fabric is hard. Also keep in mind that good denim is practically sheet metal in comparison to most fabrics, so on one hand easier to get consistent results, but on the other hand, even small differences are more noticeable than something lighter or (god forbid) stretchy.
You cannot just engineer your way out of some of the challenges inherit in garment construction (trust me, Ive tried).
The title says "France rejects backdoor mandate" but TFA makes it clear that France is not a hive-mind:
- The rejection was by the French National Assembly (think parliament/congres)
- Ths happened despite pressure from the internal ministry (the government)
I find it interesting that it is often a similar story at the EU level where the European Parliament puts a stop to the worst impulses of the European Commission.
For a real-worl use case, look towards the 'script' processor in Elastic' Beats family of data shippers [1] (example is from Metricbeat but it exists in other Beats too)
They can be configured to mutate the data with some basic DSL syntax, but if you have more advanced needs, you can break out to JavaScript and transform the JSON any way you want.
This is very useful because now any transformation becomes possible. And because this is the user of your product who writes that JavaScript more as configuration than code.
And since there's no build step, it is just part if the configuration loaded at startup.
Things like "you cannot mix marketing and transactional email" are good advice, but they do nothing if you're using different subdomains but the same infrastructure (IP address) to send them out.
Microsoft is simply trying to squeeze smaller operators out of the market.
I run an open source project, we send out transaction emails from ome subdomain, and a newsletter to 50K+ subscribers once every 3 months.
I can't afford to pay for different/dedicated IO addresses for each. We use Scaleway for email delivery and it's constant trouble with two providers: qq.com who don't give a damn about non-chinese senders, and Microsoft, who are simply trying to break the ipen internet.
Before, we were on AWS SES. Guess what, we didn't even bother using different subdomains. We also didn't have dedicated IPs. Yet Microsoft did not block us because the sender IP was AWS.
It's pay to play, as simple as that.
Fortunately, we're an open source project, not a business. So when people reach out, I simply explain to them that they have chosen a mail provider that is openly hostile to small volunteer-run projects like us and that that choice has consequences. No emails for you.
IMHO we need to be more vocal about what's really going on here (the rent-seeking on the open internet by big tech), and less victim blaming (what about dns-sec).