Often it is necessary to have certain addresses which would normally be local, actually being remote.
For instance, you may have a domain widgets.com, now, most people @widgets.com are at your site, but you may have certain users (e.g. karen) who are at a different site. Because you will have specified the Local Domains as including the widgets.com domain then VPOP3 will try to send mail to karen@widgets.com to a local user called karen. Since karen is not really a local user, an error will be generated when a message to karen@widgets.com is sent.
To get around this problem, you would create a VPOP3 mapping of karen to the *REMOTE pseudo mailbox. This tells VPOP3 that mail to a local name of karen is actually remote, even though it appears to be local, so VPOP3 will queue that message to be sent to the ISP instead of trying to send it locally. Also, if VPOP3 downloads a message to a user called karen it will simply ignore the message (if it’s CCed to other users as well, then they will still receive their copy)
This feature is useful if you are using a single email account for mail to more than one site (and therefore more than one VPOP3 server).
Note, on the Utilities -> Admin Settings Page, you can tell VPOP3 to treat all unrecognised users as if they have a *REMOTE mapping.
Note, if you are doing this there are several things you should be aware of:
Your ISP may prohibit this type of use
If both VPOP3 servers connect to the same ISP POP3 mailbox at the same time, one of them will be refused access.
You need a VPOP3 licence for each site.
There is no enforceable method of preventing one site downloading mail for another site.
If that is all acceptable, then read on. If not, then there are other ways of achieving a similar effect. See the ‘Distributed Sites’ topic for more details.
If you have 4 users in two offices, Sue and James in office 1 and Philip and Karen in office 2, then, first of all, it is best to arbitrarily designate one office as being the ‘main’ office as far as your email configuration is concerned (it is probably best for the ‘main’ office to be the one where your ‘technical’ person is based). For this example we will say that office 1 is the ‘main’ office. We will also say that Sue is the technical person, and that the email domain is bobble.com
You will need two configurations:
This should have the following configurations
A user called sue
A user called james
A mapping of philip to *REMOTE
A mapping of karen to *REMOTE
This should have the following configurations
A user called philip
A user called karen
On the Utilities -> Admin Settings Page you should have Treat as *REMOTE for what VPOP3 should do with messages to unrecognised users. Note you should NOT have this setting in Office 1, otherwise badly addressed messages will simply disappear without trace!
If you want to set up any Autoresponders or further distribution/mailing lists, it is recommended that you manage them at the main office (office 1 in the above example) and have mappings of those Autoresponder/list names to *REMOTE at any other offices, to mean that messages to those addresses are ignored by sites apart from the main office.
If you have set the VPOP3 In Mail setting to Use Download Rules, VPOP3 will automatically not download any messages which are only for remote users, but it will download messages which are for local users or for a mixture of local users and remote users.