mirror of
https://github.com/3proxy/3proxy.git
synced 2026-11-22 23:59:41 +08:00
Added imapp, starttls support for smtpp, pop3p, tlspr
This commit is contained in:
1 parent
7798f78137
commit
9ab2e820b5
27 files changed
+893
-122
No files matched your search
+2
-1
@@ -29,6 +29,7 @@ from the configuration file like an independent service
|
||||
.BR proxy (8)
|
||||
.BR socks (8)
|
||||
.BR pop3p (8)
|
||||
.BR imapp (8)
|
||||
.BR tcppm (8)
|
||||
.BR udppm (8)
|
||||
.BR ftppr (8)
|
||||
@@ -140,7 +141,7 @@ configuration file
|
||||
Report all bugs to
|
||||
.BR 3proxy@3proxy.org
|
||||
.SH SEE ALSO
|
||||
3proxy.cfg(5), proxy(8), ftppr(8), socks(8), pop3p(8), tcppm(8), udppm(8),
|
||||
3proxy.cfg(5), proxy(8), ftppr(8), socks(8), pop3p(8), imapp(8), tcppm(8), udppm(8),
|
||||
kill(1), syslogd(8),
|
||||
.br
|
||||
https://3proxy.org/
|
||||
|
||||
+11
-1
@@ -55,6 +55,9 @@ Recursion is not allowed.
|
||||
.B pop3p
|
||||
[options]
|
||||
.br
|
||||
.B imapp
|
||||
[options]
|
||||
.br
|
||||
.B smtpp
|
||||
[options]
|
||||
.br
|
||||
@@ -92,6 +95,9 @@ Proxy with protocol autoselection between proxy / socks / tlspr
|
||||
.B pop3p
|
||||
POP3 proxy (default port 110)
|
||||
.br
|
||||
.B imapp
|
||||
IMAPv4 proxy (default port 143)
|
||||
.br
|
||||
.B smtpp
|
||||
SMTP proxy (default port 25)
|
||||
.br
|
||||
@@ -209,6 +215,7 @@ Never ask for username/password
|
||||
.BR proxy (8)
|
||||
.BR socks (8)
|
||||
.BR pop3p (8)
|
||||
.BR imapp (8)
|
||||
.BR tcppm (8)
|
||||
.BR udppm (8)
|
||||
.BR ftppr (8)
|
||||
@@ -847,6 +854,9 @@ locally redirects to
|
||||
.B pop3
|
||||
locally redirects to
|
||||
.B pop3p
|
||||
.B imap
|
||||
locally redirects to
|
||||
.B imapp
|
||||
.B http
|
||||
locally redirects to
|
||||
.B proxy
|
||||
@@ -1384,7 +1394,7 @@ authentication and/or allow/deny ACLs.
|
||||
Report all bugs to
|
||||
.BR 3proxy@3proxy.org
|
||||
.SH SEE ALSO
|
||||
3proxy(8), 3proxy_crypt(8), proxy(8), ftppr(8), socks(8), pop3p(8), smtpp(8), tlspr(8), tcppm(8), udppm(8), syslogd(8),
|
||||
3proxy(8), 3proxy_crypt(8), proxy(8), ftppr(8), socks(8), pop3p(8), imapp(8), smtpp(8), tlspr(8), tcppm(8), udppm(8), syslogd(8),
|
||||
.br
|
||||
https://3proxy.org/
|
||||
.SH AUTHORS
|
||||
|
||||
+124
@@ -0,0 +1,124 @@
|
||||
.TH imapp "8" "July 2026" "3proxy 0.9" "Universal proxy server"
|
||||
.SH NAME
|
||||
.B imapp
|
||||
\- IMAPv4 proxy gateway service
|
||||
.SH SYNOPSIS
|
||||
.BR "imapp " [ -d ]
|
||||
.IB \fR[ -l \fR[ \fR[ @ \fR] logfile \fR]]
|
||||
.IB \fR[ -p port\fR]
|
||||
.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 imapp
|
||||
is IMAPv4 (IMAP4rev1) gateway service to allow internal users to access external
|
||||
IMAP servers.
|
||||
.SH OPTIONS
|
||||
.TP
|
||||
.B -I
|
||||
Inetd mode. Standalone service only.
|
||||
.TP
|
||||
.B -d
|
||||
Daemonize. Detach service from console and run in the background.
|
||||
.TP
|
||||
.B -t
|
||||
Be silenT. Do not log start/stop/accept error records.
|
||||
.TP
|
||||
.B -u
|
||||
Never look for username authentication.
|
||||
.TP
|
||||
.B -e
|
||||
External address. IP address of the interface the proxy should initiate connections
|
||||
from.
|
||||
By default, the system will decide which address to use in accordance
|
||||
with the routing table.
|
||||
.TP
|
||||
.B \-ni\fIPATH\fR
|
||||
(Linux only) Switch to the network namespace identified by
|
||||
.I PATH
|
||||
before opening the listening socket. The current namespace is saved and restored
|
||||
immediately after binding, so outgoing connections run in the original namespace
|
||||
unless
|
||||
.B \-ne
|
||||
is also given.
|
||||
.TP
|
||||
.B \-ne\fIPATH\fR
|
||||
(Linux only) Switch to the network namespace identified by
|
||||
.I PATH
|
||||
after the listening socket has been bound (and after restoring from
|
||||
.B \-ni
|
||||
if applicable). Both options accept any namespace file path
|
||||
(e.g.\& \fI/var/run/netns/myns\fR or \fI/proc/PID/ns/net\fR)
|
||||
and require \fBCAP_SYS_ADMIN\fR.
|
||||
.TP
|
||||
.B -i
|
||||
Internal address. IP address the proxy accepts connections to.
|
||||
By default, connections to any interface are accepted. It\'s usually unsafe.
|
||||
Unix domain sockets can be specified with
|
||||
.I -iunix:/path/to/socket
|
||||
syntax (e.g., -iunix:/var/run/imapp.sock). On Linux, abstract sockets use
|
||||
.I -iunix:@socketname
|
||||
syntax.
|
||||
.TP
|
||||
.B -p
|
||||
Port. Port proxy listens for incoming connections. Default is 143.
|
||||
.TP
|
||||
.B -h
|
||||
Default destination. It's used if the target address is not specified by the user.
|
||||
.TP
|
||||
.B -x
|
||||
Disable STARTTLS support. STARTTLS is not announced in the CAPABILITY
|
||||
response and the STARTTLS command is not accepted.
|
||||
.TP
|
||||
.B -l
|
||||
Log. By default logging is to stdout. If
|
||||
.I logfile
|
||||
is specified logging is to file. Under Unix, if
|
||||
.RI \' @ \'
|
||||
precedes
|
||||
.IR logfile ,
|
||||
syslog is used for logging.
|
||||
.TP
|
||||
.B -S
|
||||
Increase or decrease stack size. You may want to try something like -S8192 if you experience 3proxy
|
||||
crashes.
|
||||
.SH CLIENTS
|
||||
You can use any MUA (Mail User Agent) with IMAPv4 support. Set the client to use
|
||||
.I internal_ip
|
||||
and
|
||||
.IR port
|
||||
as an IMAP server. The address of the real IMAP server must be configured as a part of
|
||||
the IMAP username. The format for the username is
|
||||
.IR username @ server ,
|
||||
where
|
||||
.I server
|
||||
is the address of the IMAP server and
|
||||
.I username
|
||||
is the user\'s login on this IMAP server. The login itself may contain an \'@\' sign.
|
||||
Supported client authentication methods are the LOGIN command, AUTHENTICATE PLAIN
|
||||
and AUTHENTICATE LOGIN. With the server, the proxy authenticates using the method
|
||||
chosen by the client if the server supports it (as advertised in the CAPABILITY
|
||||
response); otherwise it falls back to AUTHENTICATE LOGIN, AUTHENTICATE PLAIN or
|
||||
the LOGIN command, in this order of preference. Challenge-response authentication
|
||||
(CRAM-MD5, etc.) is not supported, because it 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), STARTTLS is
|
||||
supported and announced in the CAPABILITY response unless disabled with
|
||||
.BR -x .
|
||||
After the client issues STARTTLS, 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 STARTTLS negotiation with the destination
|
||||
server, and then transparently passes TLS traffic between the client and the
|
||||
server. If the destination server does not support STARTTLS, the TLS handshake
|
||||
with the client fails.
|
||||
.SH BUGS
|
||||
Report all bugs to
|
||||
.BR 3proxy@3proxy.org
|
||||
.SH SEE ALSO
|
||||
3proxy(8), ftppr(8), pop3p(8), proxy(8), smtpp(8), socks(8), tcppm(8), tlspr(8), udppm(8), syslogd(8),
|
||||
.br
|
||||
https://3proxy.org/
|
||||
.SH AUTHORS
|
||||
3proxy is designed by Vladimir Dubrovin <vlad@3proxy.org>
|
||||
+15
@@ -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
|
||||
|
||||
+16
-1
@@ -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 smtpp
|
||||
is SMTP gateway service to allow internal users to access external SMTP
|
||||
@@ -61,11 +62,15 @@ syntax (e.g., -iunix:/var/run/smtpp.sock). On Linux, abstract sockets use
|
||||
syntax.
|
||||
.TP
|
||||
.B -p
|
||||
Port. Port proxy listens for incoming connections. Default is 25.
|
||||
Port. Port proxy listens for incoming connections. Default is 587.
|
||||
.TP
|
||||
.B -h
|
||||
Default destination. It's used if the target address is not specified by the user.
|
||||
.TP
|
||||
.B -x
|
||||
Disable STARTTLS support. STARTTLS is not announced in the EHLO response
|
||||
and the STARTTLS command is not accepted.
|
||||
.TP
|
||||
.B -l
|
||||
Log. By default logging is to stdout. If
|
||||
.I logfile
|
||||
@@ -95,6 +100,16 @@ is the user\'s login on this SMTP server. The login itself may contain an \'@\'
|
||||
Only cleartext authentication is supported, because challenge-response
|
||||
authentication (CRAM-MD5, SPA, 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), STARTTLS is
|
||||
supported and announced in the EHLO response unless disabled with
|
||||
.BR -x .
|
||||
After the client issues STARTTLS, 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 STARTTLS negotiation with the destination
|
||||
server, and then transparently passes TLS traffic between the client and the
|
||||
server. If the destination server does not support STARTTLS, the TLS handshake
|
||||
with the client fails.
|
||||
.SH BUGS
|
||||
Report all bugs to
|
||||
.BR 3proxy@3proxy.org
|
||||
|
||||
@@ -78,6 +78,15 @@ TLS_CHECK_LEVEL. 0 (default) - allow non-TLS traffic to pass, 1 - require TLS, o
|
||||
.B -s
|
||||
Split the TLS Client HELLO packet across multiple TCP segments to make SNI-based DPI detection harder. An optional numeric value can follow (e.g. \fB-s1\fR) to control the splitting behaviour.
|
||||
.TP
|
||||
.B -Ximap | -Xpop3 | -Xsmtp
|
||||
STARTTLS mode for the given protocol. The proxy speaks the plaintext protocol
|
||||
with the client (greeting, capability advertisement with STARTTLS only, STARTTLS
|
||||
command), then, after the client issues STARTTLS and sends a TLS Client HELLO,
|
||||
connects to the destination taken from SNI (default port 143/110/587), performs
|
||||
STARTTLS negotiation with the destination server and transparently passes TLS
|
||||
traffic. If the destination server does not support STARTTLS, the TLS handshake
|
||||
with the client fails.
|
||||
.TP
|
||||
.B -l
|
||||
Log. By default logging is to stdout. If
|
||||
.I logfile
|
||||
|
||||
Reference in new issue
Block a user