I have a dockerised test server that cannot send email because of a SASL authentication error. To be clear I haven’t configured anything with SASL, and I had no itention of doing so. It seems to me that SASL shouldn’t be involved, as I would expect Sogo to be ‘authenticating’ with postfix by virtue of being inside the docker network.
The postfix logs say this: mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248]: SASL PLAIN authentication failed: (reason unavailable),
I suspect I could fix this by changing ‘mynetworks’, but I can’t find any documentation suggesting that I should have to do that, which makes me think that something else is wrong. No part of 172.22.1.0/24 is in the current mynetworks:
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
The only thing in extra.conf is ‘myhostname’
nevermind, I figured it out.
Users (mailboxes) have to be enabled for SMTP. I don’t want my users to actually use remote SMTP, just webmail and activesync, so I had disabled SMTP for that user.
nevermind, I figured it out.
Users (mailboxes) have to be enabled for SMTP. I don’t want my users to actually use remote SMTP, just webmail and activesync, so I had disabled SMTP for that user.
nevermind, I figured it out.
Users (mailboxes) have to be enabled for SMTP. I don’t want my users to actually use remote SMTP, just webmail and activesync, so I had disabled SMTP for that user.
nevermind, I figured it out.
Users (mailboxes) have to be enabled for SMTP. I don’t want my users to actually use remote SMTP, just webmail and activesync, so I had disabled SMTP for that user.
Also this forum system is super buggy, I posted that many replies because it kept telling me it had failed to post the reply