Version 6.1
Introduction |
|---|
| |||||
|
|
Version 6.1 |
||||||||||||||||||||||||||||
|
|
When the CommuniGate Pro server receives any message directed to aname@domain.dom, and the Domain does not have an Account/Group/Forwarder/Mailing List with that aname name, the message is Rerouted (the envelope address is changed) to aname%domain.dom@otherserver.dom._via. The ._via suffix tell the Router module to accept this address, and to cut off the domain name, using that part only as a name of the server to connect to (the Router module always cuts off the IP-address domain parts, too). The resulting envelope address (aname%domain.dom) is converted to the standard form (aname@domain.dom) before it is sent to that other server. As a result, the other server receives such a message with the unmodified envelope data and header fields.
As soon the aname Account is created in the CommuniGate Pro domain.dom Domain, mail starts to go to that Account automatically. You can copy all messages from the aname account on the old server to the aname Account on the new server and phase out the aname account on the old server.
If you want to bypass the MX or SRV records and relay all E-mail and Signals to a certain IP address (specified explicitly or using a DNS A-record), then see the Bypassing MX/SRV section.
If you want your Server to act as a backup E-mail relay for certain domains, you can enable
the Relay to All Hosts We Backup option in the SMTP module settings.
This is not a perfect solution, since anybody who can modify DNS records for certain domains
can use your server as a backup relay for those domains.
The SMTP module does not look at the MX records if the port number of a remote host is explicitly specified. By specifying the standard (25) SMTP port number, you tell the SMTP module to look for the relay.domain DNS A-record, and ignore its MX records.
The SIP module does not look at the SRV records if the port number of a remote host is explicitly specified. By specifying the standard (5060) SIP port number, you tell the SIP module to look for the relay.domain DNS A-record, and ignore its SRV records.
Note: You may want to add a Relay:, NoRelay: or RelayAll: prefix to these Router records.
To deliver mail to those sites, you should configure your CommuniGate Pro server as their mail relay. Depending on the customer server capabilities, your can use either the ATRN or the Unified Domain-Wide Account (RPOP) method.
If the customer server supports the On-Demand Mail Relaying (ATRN) method, you should:To let mail to all customer domains being released with one ETRN or ATRN command, you should enqueue mail sent to the customer "secondary" domains into the customer "main domain" queue.
If the remote server should receive mail for the domain1.dom, domain2.dom, and domain3.dom domains, but it sends ETRN or ATRN commands only for the domain1.dom domain, use the following Router domain-level records:Mail to all customer domains will be placed into the domain1.dom queue, and if you want to hold that queue till the ATRN/ETRN command is sent, include the domain1.dom name into the Hold Mail for Domains setting of the SMTP module.
The account security should already exist in the main domain, and the Mailbox outgoing should already exist in that account.
To use a Shared Mailbox, two steps must be taken: first, potential users of the shared Mailbox should be granted access rights for that Mailbox. On the second step the user mailers should be configured to access shared Mailbox(es). Since these shared Mailboxes belong to a different account, they are called foreign Mailboxes.
First, the owner of the shared Mailbox should create a regular Mailbox within his/her account. It is useful to create a special account public and create shared Mailboxes in that account. To grant others access rights to the shared Mailbox, the account owner should use either a decent IMAP client that can deal with ACL (Access Control Lists) or the WebUser Interface. The WebUser Interface section describes how you can set the desired Mailbox Access Rights.
If a shared Mailbox is created inside the public account, it is useful to grant all Mailbox Access Rights to the real shared Mailbox owner, so the owner can perform all operations with that Mailbox without logging in as the user public.
To access shared Mailboxes, user mailers should be configured to display both the user account's own Mailboxes, and the available shared (foreign) Mailboxes. The most universal method is to use the account Mailbox Subscription list. This list is a simple set of Mailbox names, and both account's own Mailbox and foreign Mailbox names can be included into that list.
Many IMAP clients can only use the Mailbox Subscription list, but they cannot modify that list, or they do not allow a user to enter a foreign Mailbox name into that list. In this case IMAP users should use the WebUser Interface to fill their subscription lists. If a shared Mailbox announce has been created in the account marketing, users should put the ~marketing/announce foreign Mailbox name into their subscription lists.
The domain administrator can use the Account Template to specify the initial Mailbox Subscription list, so all new accounts automatically get subscriptions to some shared Mailboxes.
When shared Mailboxes are included into the Account Subscription List, the users should configure their mail clients to display all Mailboxes listed in the Subscription List:Some clients (including Microsoft Outlook and Outlook Express) cannot display foreign Mailboxes even if those Mailbox names are included into the account subscription list. Users of these mailers can access foreign Mailbox via Mailbox aliases. They should use the WebUser Interface to specify aliases for foreign Mailboxes they want to access. If a shared Mailbox announce has been created in the account marketing, users should create the mkt-announce Mailbox alias for the ~marketing/announce foreign Mailbox. Their IMAP clients will display the mkt-announce name and will provide access to the ~marketing/announce Mailbox messages.
The domain administrator can use the Account Template to specify the initial Mailbox Aliases, so all new accounts automatically get a predefined set of Mailbox aliases for the specified shared Mailboxes.
The Server Administrator with the All Domains access right
has unlimited access rights to all Mailboxes in all Accounts.
The Domain Administrator with the CanAccessMailboxes access right
has unlimited access rights to all Mailboxes in that Domain Accounts.
Administrators can use any decent IMAP, MAPI, or XIMSS client to access user Mailboxes. That client should
be able to let a user enter a Mailbox name directly.
To open the INBOX Mailbox in the username Account, administrators should log in under their own names
and tell the client to open the ~username/INBOX Mailbox.
The WebUser Interface can be used for the same purpose. Administrators can log in under their own names, open the Subscription page and type the user Mailbox name in the Open Mailbox panel.
You may want to provide better looking http://username.domain.dom/ URLs for your Account personal Web sites. This feature is based on the method the Server uses to route requests sent to the HTTP User ports.
For users in the domain.dom secondary Domain, add the following records to the Router:*.domain.dom = *@domain.dom <LoginPage%*@domain.dom> = *@domain.domIf the domain.dom is your Main Domain, then add the following records:
*.domain.dom = *@fict <LoginPage%*@fict> = *
These records route the LoginPage@username.domain.dom addresses to username@domain.dom addresses (or username addresses if domain.dom is the Main Domain).
Finally, you should update your DNS server to ensure that all username.domain.dom
names point to your Server IP address.
You may want to use wildcard records (*.domain.dom CNAME domain.dom) if your DNS server supports them.