Conversation

Notices

1. Embed this notice
   Masto.host (mastohost@mastodon.social)'s status on Tuesday, 10-Jan-2023 18:59:51 JST Masto.host

   in reply to

   • Jeremy ⁂
   • Florian Ledermann

   @floledermann @jeremy Thanks for tagging me and sorry this is happening.
   It's an unfortunate spam filtering practice/decision.

   I do own mastohost.com and could easily make that the domain for sending emails but it doesn't make much sense to me.

   Haven't got any similar reports, so hopefully it's an isolated issue. Will keep that in mind, though.

   • Embed this notice
     Florian Ledermann (floledermann@mapstodon.space)'s status on Tuesday, 10-Jan-2023 19:00:16 JST Florian Ledermann

     in reply to

     • Jeremy ⁂

     @jeremy @mastohost
     FWIW TU Wien has now whitelisted masto.host, but the practice may be more widespread as such (silly and overshooting) blacklists may be shared in the IT community or even embedded in products they use ? .

   • Embed this notice
     Jeremy ⁂ (jeremy@mapstodon.space)'s status on Tuesday, 10-Jan-2023 19:00:38 JST Jeremy ⁂

     in reply to

     • Florian Ledermann

     @floledermann Thanks for investigating Florian! This is quite a regrettable IT decision indeed. Hope there is room for a change of policy at your university.
     Tagging @mastohost so he's aware of the issue.

   • Embed this notice
     Florian Ledermann (floledermann@mapstodon.space)'s status on Tuesday, 10-Jan-2023 19:00:45 JST Florian Ledermann

     in reply to

     My university's #IT claims that the .host TLD is "potentially suspicious", and therefore all incoming email from any .host domain should be ignored without even notifying the receiver.

     If you hear from someone who doesn't receive their confirmation mail from a #mastodon instance hosted on masto.host, this may be the reason (even if the instance has a different domain, mails will originate from masto.host). Such (IMO inacceptable!) policies are often shared in the IT community.

   • Embed this notice
     Florian Ledermann (floledermann@mapstodon.space)'s status on Tuesday, 10-Jan-2023 19:00:54 JST Florian Ledermann

     TIL my university #tuwien blocks incoming emails for the entire .host top-level-domain. Many #mastodon servers are hosted on masto.host, so this would block all confirmation mails from any of these servers (e.g. my instance), making it impossible to register an account. The mails are not even marked as spam, they are simply not delivered (while acknowledging delivery to the sender).

     Is it only me, or is this a quite unbelievable and unacceptable intervention in communication infrastructure?