ok, i figured that by letting dovecot answer on the internal IP address without any encryption, i would solve my problems..
in effect, i'd be accessing my mail using my own webmail component.
but the following settings still fail :
{
"{192.168.178.21:143\/imap\/novalidate-cert}": "FAIL:[\n \"TLS\\\/SSL failure for 192.168.178.21: SSL negotiation failed\"\n]"
}"
any ideas, please?
On Mon, Oct 11, 2021 at 7:21 PM Rene Veerman <rene.veerman.netherlands@xxxxxxxxx> wrote:
oh, i was trying to access dovecot using port 143, while i should be using 993.i got another problem though, dovecot is full of zero-day exploits, and using starttls with certbot forces me to use a domain name, not an IP address, which means i have to open and forward that on my internet modem to the machine running dovecot.i'm NOT looking forward to opening my machine to remote execution attacks.any suggestions?On Mon, Oct 11, 2021 at 6:55 PM Rene Veerman <rene.veerman.netherlands@xxxxxxxxx> wrote:i need to connect to a dovecot server running on ubuntu 20.04, from PHP 7.4.3 running on the same server.i've verified that dovecot is listening on port 143.i've setssl_min_protocol = TLSv1.2in /etc/dovecot/conf.d/10-ssl.confbut in my web app, i now get :{192.168.178.21:143/imap/ssl}: "FAIL:[\n \"TLS\\/SSL failure for 192.168.178.21: SSL negotiation failed\"\n]"so i'm thinking the TLS protocol version that imap_open() in PHP is off target.how do i correct this?
