@abloo @hackernews because good web design kills children in African countries

@hackernews Really interesting. Did experience this before already (with mails sent to Google or Microsoft from a selfhosted corporate server). That's why I have for a while and still pretty much am very cautious to consider "e-mail" the shining example of successfully working and established decentralized services. It's just not true. A vast load of mails these days runs through large corporate entities, and quite some of them have been making life difficult for smaller systems for a while now.

@yura@udongein.xyz @hackernews@die-partei.social Ага, уже месяц не могу заставить это говно работать. Пишут что "заблокировали за то потому что есть доказательства рассылок спама, доказательства, как у коммуняк - в секретных никому неизместных папочках, показывать мы их конечно не будетм. Тикеты не обрабатывают, пидарасы в общем"

@hackernews Microsoft have been doing this for years - I used to be admin for a mid-sized environment (50k mailboxes) and we would strike this issue every now and then.

I also belonged to some mail operations lists that had presence from some Microsoft email engineers, and while the organisation seems to be uncaring, the individuals very much did care.

Unfortunately with 90% of all email being spam it implies that a similarly large number of "support requests" will be from spammers too. They're not all incompetent ... spammers were basically the earliest adopters of technologies like SPF, to make sure they could get more deliverability.

The only real approach is to lodge a ticket, and escalate every time you get a response. Eventually you'll get a human - most of the early responses are just scripted. Stay respectful throughout (as you obviously are) and just keep on sending the same facts in each email (i.e. "I have SPF,DKIM,DMARC,DNNSEC; I am a mail host/ISP for multiple small businesses and invidigual users; Registered with JMRP and SNDS with no complaints ... etc etc")

If you can run message content analysis on your own outbound messages, you might consider doing the same thing that MS do - if the messages look like spam (often the case if someone is receiving spam but autoforwarding all their email to another mailbox) then send them through a dedicated outbound IP that you can afford to lose/replace; but if they really look like good content send them through your more permanent IP. Your IP address needs to have a long-term reputation of sending only good messages; also the whole adjacent range of addresses need to have this as well, otherwise you'll suffer from a lazy "block the whole /24" attitude. Put rate limits on your good IP - a customer that sends 1k emails per day who suddenly sends 1k in a minute needs to be blocked (queued) immediately, as they are probably compromised. Don't trust everything they send just because you know who they are ...

It's a thankless job these days. Even recently, GMail was blocking email coming from Microsoft ... so the problem exists for everyone.

Melde dich an, um an der Konversation teilzuhaben
Die PARTEI Mastodon

Mastodon ist ein soziales Netzwerk. Es basiert auf offenen Web-Protokollen und freier, quelloffener Software. Es ist dezentral (so wie E-Mail!).