-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
External IMAP clients don't connect. #521
Comments
Hi @tomav , no, I got the exact same issue after completly disabling fail2ban and re-up the container :/
|
I got same error with RainLoop, are you solution it? |
after delete Hi @tomav how to set whitelist fail2ban? |
really strange as I completely disabled fail2ban and it doesn't work... Just trying your trick and I'll let you know. |
Just tryed with Solmail app from google play store and this client can connect to the server. Wierd... |
follow me
then it's working. another error issues |
what about your ssl conf? |
Did it get solved? |
same issue here: solved removing lib-fail2ban/* |
What is causing it to get on the ban list? |
Hi,
I have a strange issue. My container is up and running.
I use rainloop as a webmail. It is installed as another docker container on the same server.
When I configure Rainloop with the local IP of the server, everything is working flawlessly (including sending/receiving emails), but when I configure it with the fdqn or the external IP adress, connections are refused with these errors :
(telnet from outside to these ports are ok)
Here are 2 TCPDump made on the server while attempting to connect with external IMAP client :
Paquets are arriving, but there is no answer at all...
Here is my docker-compose.yml file (I tryed disabling cap_add, but got the same issue) :
Any idea ?
The text was updated successfully, but these errors were encountered: