Added imapp, starttls support for smtpp, pop3p, tlspr

This commit is contained in:
Vladimir Dubrovin committed 2026-07-22 16:15:50 +03:00
1 parent 7798f78137
commit 9ab2e820b5
27 files changed
+893 -122

No files matched your search

+15
View File
@@ -9,6 +9,7 @@
.IB \fR[ -i internal_ip\fR]
.IB \fR[ -e external_ip\fR]
.IB \fR[ -h default_ip[:port]\fR]
.IB \fR[ -x ]
.SH DESCRIPTION
.B pop3p
is POP3 gateway service to allow internal users to access external POP3
@@ -66,6 +67,10 @@ Port. Port proxy listens for incoming connections. Default is 110.
.B -h
Default destination. It's used if the target address is not specified by the user.
.TP
.B -x
Disable STARTTLS (STLS) support. STLS is not announced in the CAPA response
and the STLS command is not accepted.
.TP
.B -l
Log. By default logging is to stdout. If
.I logfile
@@ -94,6 +99,16 @@ is the user\'s login on this POP3 server. The login itself may contain an \'@\'
Only cleartext authentication is supported, because challenge-response
authentication (APOP, CRAM-MD5, etc.) requires a challenge from the server before
we know which server to connect to.
When running as a 3proxy service (not as a standalone binary), STLS is
supported and announced in the CAPA response unless disabled with
.BR -x .
After the client issues STLS, the connection is handled by
.BR tlspr (8):
the destination host is taken from the SNI of the client TLS handshake (or from
the -h option), the proxy performs STLS negotiation with the destination
server, and then transparently passes TLS traffic between the client and the
server. If the destination server does not support STLS, the TLS handshake
with the client fails.
.SH BUGS
Report all bugs to
.BR 3proxy@3proxy.org