Changing the imaps port #

Odhiambo Washington odhiambo at gmail.com
Tue Jan 22 08:58:22 EET 2019


On Tue, 22 Jan 2019 at 06:17, Patrick Mahan <plmahan at gmail.com> wrote:

> Dovecot 2.3.4, FreeBSD 11.2
>
> Due to comcast buisness ISP intercepting imaps I need to have my clients
> connect to non-standard port (9999).  Previously I had been using stunnel
> to receive the imaps connection and forward it to the imap port over
> 127.0.0.1.  But I would like to retire stunnel and have my imap clients
> connect remotely.
>
> I have configured the imap-login service -
>
> service imap-login {
>   inet_listener imap {
>     address = 127.0.0.1, ::1
>     port = 143
>   }
>   inet_listener imaps {
>     port = 9999
>   }
>   process_min_avail = 3
>   service_count = 0
>   vsz_limit = 1 G
> }
>
> But I am not seeing any listeners on port 9999 -
>
> root at ns(1001)# netstat -an | grep 9999
>
> Using sockstat on FreeBSD:
>
> root at ns(1002)# sockstat | grep dovecot | grep tcp
> root          dovecot      34800 15 tcp4     *:4190
>        *:*
> root          dovecot      34800 37 tcp4     127.0.0.1:143
>     *:*
> root          dovecot      34800 38 tcp6      ::1:143
>         *:*
>
> I have mail_debug = yes, but I don't see any failures.  What is the best
> way to debug why I am not seeing this port number?
>
> Thanks,
>
> Patrick
>
>
I would leave dovecot config untouched and use a firewall (PF) to translate
port 9999 to whatever dovecot listens to.

-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dovecot.org/pipermail/dovecot/attachments/20190122/e1c3b1af/attachment.html>


More information about the dovecot mailing list