Proxy Configuration
Changes don't take effect until system restart. You must restart the server before making any other configuration changes or the changes you make below will be overwritten.
Act As HTTP Proxy Server

CHECKED> Yes
CHECKED> No

 Configure the server to act as an HTTP proxy server. The Sambar Server is not a caching HTTP proxy server, simply a "pass-through" gateway. If turned on, the proxy server runs on the same port as the HTTP server. Note: FTP proxy over HTTP, and SSL tunneling are supported when HTTP proxy is turned on. Make sure the security restrictions (proxyaccept) in security.ini are appropriate for your site.
HTTP Proxy Word Filter

CHECKED> Yes
CHECKED> No

 The HTTP Proxy includes a simple word filter that can be enabled to restrict access to URLs that contain undesirable words. The config/wordlist.ini file contains the proxy filter words.
Proxy Word Filter IPs

A space separated list of IP addresses on which to filter. This list may use wild-card characters tomatch against (i.e. 192.168.*). If no IP addresses are provided or a star (*) is provided, all HTTP proxy users are subject to the wordlist filter.
Log HTTP Proxy Usage

CHECKED> Yes
CHECKED> No

 If the Sambar Server is configured to run as an HTTP Proxy server, this flag determines if a log/proxy.log log file should be maintained.
Remote Proxy Server

When acting as an HTTP proxy, a remote caching proxy server can also be used. If the Remote Proxy field is non-blank, all proxy requests will be forwarded to the server configured (typically your ISPs caching proxy). FTP and SSL tunneling requests are also directed to the remote proxy.
Remote Proxy Port

Remote Proxy Port to connect with when utilizing a caching remote proxy server.
Act As NNTP Proxy Server

CHECKED> Yes
CHECKED> No

 Configure the server to act as an NNTP proxy server. Important: The Sambar Server can only act as an NNTP Proxy server for a single News server. The NNTP Proxy server cannot be run when the Sambar Server is configured to run as a native NNTP Server.
NNTP Server

The NNTP Server that proxy requests will be directed to. This field is not used when the Sambar Server is configured to run as a native NNTP Server.
NNTP Port

The TCP/IP protocol has a number of ports which are used to differentiate requests to different processes. The standard NNTP port number is 119.
Act As SMTP Proxy Server

CHECKED> Yes
CHECKED> No

 Configure the server to act as an SMTP proxy server.
SMTP Server

The SMTP Server that proxy requests will be directed to. This server must be configured in order to use the SMTP Proxy.
SMTP Port

The TCP/IP protocol has a number of ports which are used to differentiate requests to different processes. The standard SMTP port number is 25.
Act As POP3 Proxy Server

CHECKED> Yes
CHECKED> No

 Configure the server to act as a POP3 proxy server.
POP3 Server

The POP3 Server that proxy requests will be directed to.
POP3 Port

The standard POP3 port number is 110.
POP3 Enhanced

CHECKED> Yes
CHECKED> No

 The POP3 Enhnaced mode allows users to override the POP3 proxy specified above with one of their own choosing by modifying their username to include the POP3 server that the proxy should connect via. The # symbol is used to specify an alternative server (i.e. user#pop3server).
Act As IMAP4 Proxy Server

CHECKED> Yes
CHECKED> No

 Configure the server to act as a IMAP4 proxy server.
IMAP4 Server

The IMAP4 Server that proxy requests will be directed to.
IMAP4 Port

The standard IMAP4 port number is 143.
Act As FTP Proxy Server

CHECKED> Yes
CHECKED> No

 Configure the server to act as an FTP proxy server. The HTTP proxy server includes a basic FTP proxy server used by browser clients; this "native" FTP proxy server is for traditional FTP client applications such as CuteFTP or WSFtp. The port used for the FTP Proxy server is the same port as is configured for the FTP Server. See the Proxy documentation for more details on the native FTP proxy.
Act As Telnet Server/Proxy

CHECKED> Yes
CHECKED> No

 Configure the server to act as a Telnet server and proxy. See the Telnet documentation for more details on the Telnet Server/Proxy functionality.
Act As Bridge Proxy Server

CHECKED> Yes
CHECKED> No

 Configure the server to act as a bridge proxy server. This feature provides a bridge capability for any TCP application bound to a specific port.
Bridge Server

The Bridge Server that proxy requests will be directed to.
Bridge Port

The standard Bridge proxy port number.
Act As SOCKS Proxy

CHECKED> Yes
CHECKED> No

 Configure the server to act as a SOCKS4/SOCKS5 proxy server.
SOCKS Port

The TCP/IP protocol has a number of ports which are used to differentiate requests to different processes. The standard SOCKS port number is 1080.
Act As Real/AV Proxy

CHECKED> Yes
CHECKED> No

 Configure the server to act as a Real Audio/Video proxy server.
Real/AV Port

The TCP/IP protocol has a number of ports which are used to differentiate requests to different processes. The default Real/AV port number is 1090.
Dial-On-Demand

CHECKED> Yes
CHECKED> No

 Configure the server for dial-on-demand (all outgoing connections). Warning! The dial-on-demand functionality can cause system instability. Some users experience no problems with this feature while others experience server crashes; the problems are being investigated but appear to be dialer and operating system dependent. It is recommended that anyone experiencing problems use a third-party dialer.
Trace Dial-On-Demand Usage

CHECKED> Yes
CHECKED> No

 Trace dial-on-demand usage to the server.log.
Dial-On-Demand Entry

The RAS Entry to use for Dial-On-Demand. This is the name you specified when setting up the RAS configuration for your ISP.
Dial-On-Demand User

The username to use with the RAS Entry when dialing.
Dial-On-Demand Password

The password to use with the RAS Entry when dialing.
Dial-On-Demand Timeout

The timeout period to use for Dial-On-Demand. This is the time, in seconds after the last outgoing connection has been terminated that the dial-up connection should be maintained. Note: Since the scheduler only checks tasks every 2 minutes, the actual timeout duration will vary by up to 2 minutes.