The bot used to authenticate on this forum through DeltaChat, delta-identity@testrun.org, is hosted on a regular Mailcow e-mail server, which performs many types of spam checks including PTR and IP reputation check.
This approach is not suitable for chatmail relays since the only things we rely on are DKIM signatures and forced PGP encryption.
In general, proper interoperability with regular e-mail servers is nice to have, but chatmail ecosystem doesn’t enforce this, so the DeltaChat forum OAuth should not too.
to=<delta-identity@testrun.org>, relay=testrun.org[5.1.76.52]:25, delay=0.94, delays=0.01/0/0.41/0.52, dsn=5.7.1, status=bounced (host testrun.org[5.1.76.52] said: 554 5.7.1 This message does not meet our delivery requirements (in reply to end of DATA command))
So i can’t sign in to the forum from my chatmail relay
I think moving the bot to a regular chatmail relay would make sense, to avoid interoperability issues. Many real world chatmail relays in use by a bunch of users don’t have PTR records, and I’ve heard from multiple admins finding themselves on IP reputation lists. Those legacy reputation mechanisms don’t seem to work well with how the DeltaChat ecosystem operates.