how_to:vpop3_access_security
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| how_to:vpop3_access_security [2011/09/14 10:40] – [VPOP3 version 2.5 to 4.0] paul | how_to:vpop3_access_security [2011/09/14 10:53] – [VPOP3 version 2.5 to 4.0] paul | ||
|---|---|---|---|
| Line 18: | Line 18: | ||
| If the service allows (but does not require) authentication (eg SMTP, LDAP), then there will also be a **no auth** checkbox which allows you to say that, from the specified IP addresses, authentication is not required, even if the settings normally require authentication. | If the service allows (but does not require) authentication (eg SMTP, LDAP), then there will also be a **no auth** checkbox which allows you to say that, from the specified IP addresses, authentication is not required, even if the settings normally require authentication. | ||
| + | ====Default for your LAN==== | ||
| + | The **Default for your LAN** button makes VPOP3 create a default set of rules which are likely to be OK for basic internal LAN usage scenarios | ||
| + | |||
| + | What it does is: | ||
| + | - create a **DENY** rule for any gateways (routers) | ||
| + | - create an **ALLOW** rule for each network which the VPOP3 computer is directly connected to | ||
| + | |||
| + | For more situations, this will create a set of rules such as: | ||
| + | * DENY 192.168.1.1 | ||
| + | * ALLOW 192.168.1.0/ | ||
| + | * ALLOW 127.0.0.0/8 (the loopback addresses) | ||
| + | |||
| + | If there are multiple network adapters (or multiple IP addresses bound to a single adapter), then there may be more entries. | ||
| + | |||
| + | The **Default for your LAN** button cannot automatically detect if you have multiple local networks connected by internal routers, but if you have that level of complexity of network topography, it should be relatively clear how you need to configure the access restrictions to do what you require. | ||
| + | |||
| + | |||
| + | (Note that VPOP3 detects the LAN configuration when starting up, so if the IP address/ | ||
| + | |||
| + | ===The default DENY rule for your router/ | ||
| + | The router is denied access by the default rules because: | ||
| + | * Routers are very unlikely to need to send outgoing mail, or collect mail using POP3 or IMAP4, themselves | ||
| + | * Some routers act as proxy servers, so that incoming connections appear to come from the router themselves. This means that if this **DENY** rule was omitted, the default rules would allow access from anywhere on the Internet (including making VPOP3 into an open relay) - this would be very undesirable as a default rule | ||
| + | * If the router' | ||
| + | |||
| + | Note that blocking access from the router does NOT block access from external IP addresses (so it will not conflict with **ALLOW** rules allowing access from outside), unless the router acts like a proxy server, rather than a normal router. | ||
| + | |||
| + | Usually there is no need to remove this rule. The only times you would need to do that are if you need the router to send outgoing mail or collect mail itself (which is very unusual), or if your router acts as a proxy server rather than a router (which is also very unusual). In the latter case, you will need to be very careful, and set up any access rules and anti-relay rules on the router itself. (You may need to change the router if you need external access and the router does not support this) | ||
| + | |||
| + | The deny rule does NOT (with the other default settings) prevent the router from sending internal email via VPOP3, e.g. for error reports or intrusion notifications. | ||
| + | |||
| + | (Note that, nowadays, it is very rare for routers to act like proxy servers, but it was more common several years ago. If in doubt, presume it does not act this way) | ||
how_to/vpop3_access_security.txt · Last modified: 2018/11/14 10:45 by 127.0.0.1
Page Tools
