VPOP3 can be configured to restrict access to its various services depending on the client computer's IP address. This is useful if you want to allow access from only certain IP addresses (eg within your LAN) and prevent access from other IP addresses (eg the Internet).

With some services you can also restrict access to certain users on those IP addresses. These are generally only those services which require some form of logon (eg POP3, WebMail etc)

To secure a service, go to the Services tab in VPOP3, and click on the service you want to secure. You should find in there a tab called IP Access Restrictions. In that box each line defines an access restriction rule.

In these versions, the access restrictions are defined using a helper editor. Each line defines an access restriction rule.

To edit a rule, you can click on the rule, to add a rule, click on the Add New Rule text, or to remove a rule click on the X or waste bin to the left of the rule.

When adding or editing a rule you can specify whether the rule applies to a single host, a subnet (specified in CIDR format, as <network address>/<mask>, eg 192.168.0.0/24) or all addresses. You can also specify whether the restriction blocks access (DENY) or allows access (ALLOW).

If the service requires authentication, then you can also specify which users can access it from these addresses (if you don't specify any users, then all users are allowed). Note that with SMTP, if the service is configured never to require authentication, then you cannot restrict by username, as VPOP3 can not know a username, unless authentication is used.

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.

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:

1. create a DENY rule for any gateways (routers)
2. 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 (the router address)
• ALLOW 192.168.1.0/24 (the local network)
• 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/network details are changed since VPOP3 started, it will configure the settings incorrectly using this button. This can especially be an issue if VPOP3 is connected via a wireless LAN.)

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's security is compromised, this could allow access into VPOP3 from anywhere on the Internet

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)

In these versions, the access restrictions are defined as text controls. Each line defines an access restriction rule. The parts to that rule are as follows:

• Optionally if the first character on the line is a '!' (exclamation mark) it means do NOT allow access from the following IP addresses (you cannot specify user names in this case)
• The first part of the line is the 'Network Address'.
• The second part is the 'Subnet Mask'. If the Network address specifies a single host, then you can omit this section as it will default to '255.255.255.255'
• Following the 'Subnet Mask' you can optionally specify one or more usernames to indicate which users can access the service from the specified IP addresses.

This is best clarified with an example:

!192.168.0.1
192.168.0.0 255.255.0.0
0.0.0.0 0.0.0.0 fred bob

This means:

• Don't allow access to the service from IP address 192.168.0.1
• Allow access to the service from IP addresses 192.168.0.0-192.168.255.255 for anyone
• Allow access to the service from any other IP address, but only for the 'fred' and 'bob' users

Notes

• If you don't have any access restrictions defined, then all access is allowed, if you do have some access restrictions defined, then any unspecified IP addresses are denied access
• For the SMTP service, if you have specified any SMTP authentication options, you can specify a 'username' of NOAUTH. This means that access from the specified IP addresses does not require authentication
• If you want to allow access from anywhere, use a line like 0.0.0.0 0.0.0.0 to mean 'allow access from anywhere'
• The Access Restriction rules are processed from the top to bottom until an IP address match is found. So, in the above example, if the 0.0.0.0 0.0.0.0 line was put at the start, the rest of the rules would be ignored because that first line would match all IP addresses.

On the service specific access restrictions, if the address is allowed, then VPOP3 will check the global access restrictions on the Services page, unless NOGLOBAL is specified in the service specific restrictions. So, if you are modifying service specific access restrictions it is probably best to add a line saying NOGLOBAL to prevent the global access restrictions from overriding the changes.