IskandarAlex2 I made a noreply mailbox and used it programmatically with an app password. However, I couldn’t find a way to truly disable it from being used within SOGo. Sure, I can set the password to be so long no one can remember it with a “dead” Time-Based OTP, but still.
esackbauer This is why I never create “noreply” mailboxes. I simply use the relay feature for that e.g. nextcloud servers IP is allowed to relay via “Forwarding Hosts” in Mailcows admin UI. No user needed.
IskandarAlex2 I tried that and it worked! I made a Docker network, trust its IP range, and presto. Although, for some reason, it responds to my app server slower than using a mailbox, but eh. At least it works and isn’t prone to the eventuality of a break-in.
esackbauer IskandarAlex2 it responds to my app server slower than using a mailbox That is probably due to additional spam checks. You could try to whitelist the IP also on Postscreen: https://docs.mailcow.email/manual-guides/Postfix/u_e-postfix-postscreen_whitelist/
IskandarAlex2 esackbauer I have whitelisted it 10.99.0.0/24 permit, but it still responds quite slowly. I checked the Postfix logs, and it did allow it, so I’m unsure why. However, the queue active log taking a whole 10 seconds did make me question it.
