Difference between revisions of "Outbound Mail Routing"
Jump to navigation
Jump to search
| (32 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | This document can now be found at its new location in the [https://docs.hornbill.com/esp-config/email/email-domains/ Hornbill Document Library]. | |
| − | + | ||
| − | + | [[file:hornbill-document-library.png|Hornbill Cloud|link=https://docs.hornbill.com/esp-config/email/email-domains/]] | |
| − | + | <!-- | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | | | ||
| − | + | {{DISPLAYTITLE:Email Domains}} | |
| + | {{bluebanner|[[Main Page|Home]] > [[Administration]] > [[Email Administration | Email]] > Email Domains|[[:Category:Administration|Index]]}} | ||
| + | {{IntroAndLinks|Creating and configuring an Outbound Route is a required part of providing email functionality within some of the Hornbill applications. The "Domain" is primarily concerned with facilitating the Outbound mail operation, delivering from the Hornbill instance to the outside world. There are two methods of outbound routing available to us, "Direct Outbound" or "SMTP SmartHost".| | ||
:* [[Shared_Mailboxes|Shared Mailboxes (Inbound Route)]] | :* [[Shared_Mailboxes|Shared Mailboxes (Inbound Route)]] | ||
:* [[Email_Templates|Configuring Email Templates]] | :* [[Email_Templates|Configuring Email Templates]] | ||
| − | |} | + | :* [[How_to_configure_OAuth2_Authentication_for_Microsoft_Office_365_Mailbox_integration|MS Office 365 integration with OAuth2]] |
| + | }} | ||
{{infobox|Although we have expertise around our own platform and its email routing implementation, configuration, and behaviour, we use the language associated with the POP3, IMAP4, and SMTP standards and not the specific language and/or terminology of any specific vendors' mail server interfaces or platforms. | {{infobox|Although we have expertise around our own platform and its email routing implementation, configuration, and behaviour, we use the language associated with the POP3, IMAP4, and SMTP standards and not the specific language and/or terminology of any specific vendors' mail server interfaces or platforms. | ||
This means Hornbill's technical staff are not experts with the various mail server and firewall interfaces in use. Each organisations mail routing implementation can be unique to their organisation and it will be necessary for you to have someone internally with expertise and a working knowledge of your mail servers and firewalls within your own organisation. You should refer your technical email/network expert to this document which should provide them with sufficient information to allow the planning and configuration of email integration for your organisation.}} | This means Hornbill's technical staff are not experts with the various mail server and firewall interfaces in use. Each organisations mail routing implementation can be unique to their organisation and it will be necessary for you to have someone internally with expertise and a working knowledge of your mail servers and firewalls within your own organisation. You should refer your technical email/network expert to this document which should provide them with sufficient information to allow the planning and configuration of email integration for your organisation.}} | ||
| + | <br> | ||
==Creating and Managing your Outbound Routes== | ==Creating and Managing your Outbound Routes== | ||
| − | To create and Configure a new Outbound route, in Hornbill Administration navigate to '''Home > System > Email > Outbound | + | To create and Configure a new Outbound route, in Hornbill Administration navigate to '''Home > System > Email > Outbound Domains'''. You will find a default domain entry (live.hornbill.com) comes already configured with your instance which allows you to test aspects of the Hornbill applications while you are organizing the email configuration required in your infrastructure. |
* To add a new Outbound route click the plus symbol in the top right of the list. | * To add a new Outbound route click the plus symbol in the top right of the list. | ||
| Line 34: | Line 25: | ||
To successfully configure an Outbound Mail Route the following details must be completed. | To successfully configure an Outbound Mail Route the following details must be completed. | ||
| − | + | {{bullet1|Domain Name|The name that is used here '''must''' be a valid domain name. For example 'mycompany.com'}} | |
| − | + | {{bullet1|Enable processing incoming mail on this route|Turnning this on will allow any email that has been sent to this domain to be processed by the SMTP service and allow it to be routed to the appropriate mailbox.}} | |
| − | + | {{bullet1|Automatically Create Address for this route when a new mailbox is created|When a new user is created a personal mailbox is created and associated with that user. When this feature is enabled, each new user will be automatically allocated an email address using this domain name. The Address Format can then be used to set the format of the username.}} | |
| + | {{bullet1|Address Format|The Address Format to be used when a new personal mailbox is created. This is only available if you have enabled the option above to automatically create addresses for this route. The formats that can be selected are based on variations of the Firstname and Lastname of the user with the exception of the LoginID.}} | ||
| + | {{bullet1|Enable DKIM|DomainKeys Identified Mail (DKIM) is an email authentication method designed to make sure messages aren't altered in transit between the sending and recipient servers and to detect forged sender addresses in email (email spoofing), a technique often used in phishing and email spam.}} | ||
| + | {{bullet2|DKIM Selector|A DKIM selector is specified when the private/public key pair is created when DKIM is set up for the email domain (or email sender), and it can be any arbitrary string of text}} | ||
| + | {{bullet2|DKIM Key Size|Choose between 1024 and 2048 bits for your key size.}} | ||
| + | :::{{infobox|Once the Email Domain has been saved, you will be presented with a DKIM Key}} | ||
| + | {{bullet1|Outbound Routing Mode|There are two methods of outbound routing available in Hornbill, ''Use DNS Routing'' and ''Use SMTP Smart Host''. Select the one that is most desirable to you based on the descriptions below.}} | ||
| + | <br> | ||
| − | |||
| − | |||
| − | |||
== Outbound Routing Modes == | == Outbound Routing Modes == | ||
Now that you have familiarised yourself with where and how Outbound Routing is configured in Hornbill Administration, the next step is to understand which Outbound Routing mode is most suitable for your organisation. The available modes are described below and the decision essentially comes down to what's dictated by your internal IT policies. If your policies don't limit your choice then it's simply what you prefer when it comes to maintaining this integration going forward. | Now that you have familiarised yourself with where and how Outbound Routing is configured in Hornbill Administration, the next step is to understand which Outbound Routing mode is most suitable for your organisation. The available modes are described below and the decision essentially comes down to what's dictated by your internal IT policies. If your policies don't limit your choice then it's simply what you prefer when it comes to maintaining this integration going forward. | ||
<br> | <br> | ||
<br> | <br> | ||
| − | ==Option 1: Direct Outbound== | + | ===Option 1: Direct Outbound=== |
If you wish to use the Direct Outbound method, this quite simply involves the addition of an SPF and TXT record to your DNS server, validating the record using the SPF Check button within the Hornbill Administration UI, and saving the configuration upon success. Please see the section below relating to the SPF/TXT record for more information. | If you wish to use the Direct Outbound method, this quite simply involves the addition of an SPF and TXT record to your DNS server, validating the record using the SPF Check button within the Hornbill Administration UI, and saving the configuration upon success. Please see the section below relating to the SPF/TXT record for more information. | ||
| Line 51: | Line 46: | ||
<br> | <br> | ||
| − | ===SPF/TXT Record=== | + | ====SPF/TXT Record==== |
If you wish to configure “Use Direct Outbound” and the domain name used in the email from address is not live.hornbill.com, a SPF/TXT Record must be configured. The SPF/TXT record allows Hornbill to send email using the configured domain without risk of breaching any anti-spam/email source validation checks. | If you wish to configure “Use Direct Outbound” and the domain name used in the email from address is not live.hornbill.com, a SPF/TXT Record must be configured. The SPF/TXT record allows Hornbill to send email using the configured domain without risk of breaching any anti-spam/email source validation checks. | ||
| Line 81: | Line 76: | ||
<br> | <br> | ||
| − | ==Option 2: SMTP SmartHost== | + | ===Option 2: SMTP SmartHost=== |
A smart host is a type of email message transfer agent that allows a Simple Mail Transfer Protocol (SMTP) server to route email via an intermediate mailserver rather than directly to the recipient's server. With this method, a mailserver within your organisation is configured to allow the relaying of emails from your Hornbill instance (based in our data centre) to your end users. With the relay configured, any outbound email will pass through your domain and therefore, from the recipients perspective, the source domain will correspond to that used in the "from address" that we configure within Hornbill. | A smart host is a type of email message transfer agent that allows a Simple Mail Transfer Protocol (SMTP) server to route email via an intermediate mailserver rather than directly to the recipient's server. With this method, a mailserver within your organisation is configured to allow the relaying of emails from your Hornbill instance (based in our data centre) to your end users. With the relay configured, any outbound email will pass through your domain and therefore, from the recipients perspective, the source domain will correspond to that used in the "from address" that we configure within Hornbill. | ||
<br> | <br> | ||
| Line 93: | Line 88: | ||
<br> | <br> | ||
| − | ===Origin IP Address=== | + | ====Origin IP Address==== |
The origin IP that should be specified in any such firewall rules is one of the following and is dependent on the location of your instance. You should have both the Primary and Secondary IP for your geographical area: | The origin IP that should be specified in any such firewall rules is one of the following and is dependent on the location of your instance. You should have both the Primary and Secondary IP for your geographical area: | ||
* Europe: - 87.117.243.10 OR 212.71.225.67 (If you are a UK or European customer, your instance will be located in our European data centre and any outbound mail will originate from here) | * Europe: - 87.117.243.10 OR 212.71.225.67 (If you are a UK or European customer, your instance will be located in our European data centre and any outbound mail will originate from here) | ||
| Line 104: | Line 99: | ||
<br> | <br> | ||
| − | ===Smart Host Details:=== | + | ====Smart Host Details:==== |
The information you will need to have to hand when specifying your SMART Host is indicated below: | The information you will need to have to hand when specifying your SMART Host is indicated below: | ||
<br> | <br> | ||
[[File:SMART Host Details.PNG|700px|SMART Host Configuration Form]] | [[File:SMART Host Details.PNG|700px|SMART Host Configuration Form]] | ||
| + | |||
| + | ==How to configure OAuth2 Authentication for Microsoft Office 365 Mailbox integration== | ||
| + | |||
| + | '''[[How_to_configure_OAuth2_Authentication_for_Microsoft_Office_365_Mailbox_integration|Guide can be found here]]''' | ||
[[Category:Administration]] | [[Category:Administration]] | ||
| + | --> | ||
| + | [[Category:HDOC]] | ||
Latest revision as of 20:08, 11 April 2024
This document can now be found at its new location in the Hornbill Document Library.
