@GrapheneOS@grapheneos.social avatar

GrapheneOS

@GrapheneOS@grapheneos.social

Open source privacy and security focused mobile OS with Android app compatibility.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

GrapheneOS, to random
@GrapheneOS@grapheneos.social avatar

We'll be blacklisting mailbox.org and websites using it for email hosting for registration on discuss.grapheneos.org and as an alert email for attestation.app. They're blocking emails from our mail server for a convoluted, nonsensical reason and won't stop.

GrapheneOS,
@GrapheneOS@grapheneos.social avatar

mailbox.org has whitelisted the GrapheneOS domains so emails are now always getting through to our users instead of being rejected. We still disagree with blocking emails based on IPv6 addresses used by website server instances but at least it's no longer our problem.

GrapheneOS, to random
@GrapheneOS@grapheneos.social avatar

One of our community members has been doing testing of Android VPN apps to check for leaks. They've found and reported 2 issues where leak blocking functionality doesn't appear to work as intended: one occurs with local network multicast and the other with DNS while VPN is down.

GrapheneOS,
@GrapheneOS@grapheneos.social avatar

We're actively looking into these issues. Local network multicast not being blocked as expected is likely an OS bug caused by special handling of multicast. DNS issue may be another missed special case or a race condition, but it's possible the apps are handling it incorrectly.

GrapheneOS,
@GrapheneOS@grapheneos.social avatar

One of the two issues (DNS) has spread to discussions about VPN apps elsewhere. Responsibility for blocking leaks is shared between the OS and VPN apps. It's a good thing that the OS provides standard infrastructure for this. Since the OS controls most of it, we can improve this.

jwildeboer, to random
@jwildeboer@social.wildeboer.net avatar

People sending me e-mails, me replying to them only to find out that their mailserver is blocking my mailserver for weird reasons, forcing me to reconfigure my mailserver so I can get through with their mailserver which immediately blocks me again for "abusive behaviour". Well, sorry, fan of my blog. You'll never get my reply I guess. Also dear mailbox.org: your laziness wrt throwing blacklists in your server config is excluding small servers. You are NOT helping with decentralising e-mail.

jwildeboer,
@jwildeboer@social.wildeboer.net avatar

And before you ask: yes, my mailserver supports DKIM, DMARC, SPF, accepts only modern ciphers for TLS communications, has a working PTR record in DNS. Spamhaus just hates the fact that I have my mailserver running to OVH, who don't give me a /64 for my IPv6 which they deem to be reason to block me in their CSS blocklist, which mailbox.org uses on all their servers.

jwildeboer,
@jwildeboer@social.wildeboer.net avatar

Spamhaus just shrugs and tells me to STFU and find a better provider as they won't change their policy. "NOTE: If your allocation is smaller than /64, we cannot remove it from CSS, and the situation needs to be corrected with the provider prior to requesting removal." https://check.spamhaus.org/listed/?searchterm=2001:41d0:305:2100::548c

Mailbox.org just shrugs and tells me to read what Spamhaus is telling me.

But if I use IPv4, mailbox.org happily accepts my mails. From the very same server. So I guess they just don't want IPv6 traffic?

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • mdbf
  • ngwrru68w68
  • cubers
  • magazineikmin
  • thenastyranch
  • rosin
  • khanakhh
  • InstantRegret
  • Youngstown
  • slotface
  • Durango
  • kavyap
  • DreamBathrooms
  • megavids
  • tacticalgear
  • osvaldo12
  • normalnudes
  • tester
  • cisconetworking
  • everett
  • GTA5RPClips
  • ethstaker
  • anitta
  • Leos
  • provamag3
  • modclub
  • lostlight
  • All magazines