mirror of
https://github.com/3proxy/3proxy.git
synced 2026-09-03 13:25:48 +08:00
f2ae920db2
pop3p, imapp and smtpp are built with MAILPROXY=true, and ftppr and the ftp:// scheme of the HTTP proxy with FTP=true; with CMake the switches are 3PROXY_USE_MAILPROXY and 3PROXY_USE_FTP. Neither is in a default build, and the standalone binaries follow what was built. A configuration naming one of them is still read either way. The three mail protocols amount to a STARTTLS negotiation now that mail is carried over TLS, so without a proxy of their own those names are tlspr speaking the protocol: the file holds a stand-in which sets the protocol for the connection and returns tlspr for the caller to run, which serves the service name and a parent chain alike and leaves conf.c and the redirect table untouched. FTP has no such fallback, so the service is known, answers nothing and logs the refusal. The Linux workflow builds both, so all of it is still compiled and run. |
||
|---|---|---|
| .. | ||
| build-ipk.yml | ||
| build-rpm-arm64.yml | ||
| build-rpm-armhf.yml | ||
| build-rpm-x86-64.yml | ||
| build-watcom.yml | ||
| build-win32.yml | ||
| build-win64.yml | ||
| build-win-msys2-ucrt64.yml | ||
| build-winarm64.yml | ||
| c-cpp-cmake.yml | ||
| c-cpp-Linux.yml | ||
| c-cpp-MacOS.yml | ||
| c-cpp-Windows.yml | ||
| docker-test.yml | ||
| docker.yml | ||
| update-docs.yml | ||
| update-version.yml | ||
| update-wiki.yml | ||