The Advanced Server is a complete system that includes the Debian Linux-based Univention Corporate Server operating system, and a raft of nifty tools such as the Open-Xchange Microsoft Outlook Uploader (for migrating data from Outlook or an MS Exchange server), the OXtender for Mobile Web, and an MS Outlook updater. EM Client is a desktop email client with full MS Exchange synchronization. Features eM Client can be set up with Microsoft Exchange and replace Outlook, syncing your emails, contacts, calendars and tasks.
-->After you enable and configure POP3 or IMAP4 on an Exchange server as described in Enable and configure POP3 on an Exchange server and Enable and configure IMAP4 on an Exchange server, you need to configure the authenticated SMTP settings for POP3 and IMAP4 clients so they can send email messages.
The default Receive connector named 'Client Frontend <Server name>' in the Client Access services on the Mailbox server listens for authenticated SMTP client submissions on port 587. By default, this connector uses the following settings for internal and external client (authenticated) SMTP connections:
- SMTP server:
<ServerFQDN>
. For example,mailbox01.contoso.com
. - TCP port: 587
- Encryption method: TLS. Note that this is opportunistic TLS (STARTTLS) that results in an encrypted connection after the initial plain text protocol handshake.
For more information, see Default Receive connectors created during setup and Client access protocol architecture.
To configure the authenticated SMTP settings that are used by POP3 and IMAP4 clients, perform the following steps:
- Configure the FQDN on the 'Client Frontend <Server name>' Receive connector.
- Specify the certificate that's used to encrypt authenticated SMTP client connections.
- Configure Outlook on the web (formerly known as Outlook Web App) to display the SMTP settings for authenticated SMTP clients at Settings > Options > Mail > Accounts > POP and IMAP.
For more information about POP3 and IMAP4, see POP3 and IMAP4 in Exchange Server.
What do you need to know before you begin?
- Estimated time to complete: 5 minutes.
- Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms 'SSL' and 'TLS' (without versions) are often used interchangeably. Because of this similarity, references to 'SSL' in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, 'SSL' refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). To find out why you should disable the SSL protocol and switch to TLS, check out Protecting you against the SSL 3.0 vulnerability.
- If you have POP3 or IMAP4 clients that can only send SMTP email on port 25, you can configure port 25 on the 'Client Frontend <Server name>' Receive connector to allow clients to send authenticated SMTP email. However, because port 25 is also configured on the 'Client Frontend <Server name>' Receive connector for email from external SMTP servers, you'll need to modify the local IP addresses that are used to listen on port 25 on one or both of the connectors. For more information, see Receive connector local address bindings.
- You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the 'Receive connectors' entry in the Mail flow permissions topic.
- For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.
Tip
Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection.
Step 1: Configure the FQDN on the 'Client Frontend <Server name>' Receive connector
You can skip this step if you want to keep the default server FQDN value (for example, mailbox01.contoso.com). Or, you can specify an FQDN value that's more compatible with your Internet naming convention or a TLS certificate that you want to use.
If you change the FQDN value, and you want internal POP3 or IMAP4 clients to use this connector to send email, the new FQDN needs to have a corresponding record in your internal DNS.
Regardless of the FQDN value, if you want external POP3 or IMAP4 clients to use this connector to send email, the FQDN needs to have a corresponding record in your public DNS, and the TCP port (587) needs to be allowed through your firewall to the Exchange server.
Use the EAC to configure the FQDN for authenticated SMTP clients
- In the EAC, go to Mail flow > Receive connectors.
- In the list of Receive connectors, select Client Frontend <Server name>, and then click Edit ().
- In the Exchange Receive Connector page that opens, click Scoping.
- In the FQDN field, enter the SMTP server FQDN that you want to use for authenticated SMTP client connections (for example, mail.contoso.com) and then click Save.
Use the Exchange Management Shell to configure the FQDN for authenticated SMTP clients
To configure the FQDN for authenticated SMTP clients, use the following syntax:
This example configures the FQDN value mail.contoso.com.
How do you know this step worked?
To verify that you've successfully the FQDN on the 'Client Frontend <Server name> ' Receive connector, use either of the following procedures:
- the EAC, go to Mail flow > Receive connectors > select Client Frontend <Server name>, click Edit () > Scoping, and verify the value in the FQDN field.
- In the Exchange Management Shell, run the following command:
Step 2: Use the Exchange Management Shell to specify the certificate that's used to encrypt authenticated SMTP client connections
The certificate needs to match or contain the FQDN value that you specified in the previous step, and the POP3 and SMTP clients need to trust the certificate, which likely means a certificate from a commercial certification authority. For more information, see Certificate requirements for Exchange services.
Also, you need to assign the certificate to the Exchange SMTP service. For more information, see Assign certificates to Exchange Server services.
To specify the certificate that's used for authenticated SMTP client connections, use the following syntax:
This example uses the certificate that has the thumbprint value 434AC224C8459924B26521298CE8834C514856AB.
How do you know this step worked?
To verify that you've specified the certificate that's used to encrypt authenticated SMTP client connections, perform the following steps:
- Run the following command in the Exchange Management Shell:
- Run the following command in the Exchange Management Shell:
- Verify the Subject or CertificateDomains field of the certificate that you specified on the Receive connector contains the Fqdn value of the Receive connector (exact match or wildcard match).
Step 3: Use the Exchange Management Shell to configure Outlook on the web to display the SMTP settings for authenticated SMTP clients
To configure Outlook on the web to display the SMTP settings server for authenticated SMTP clients, run the following command:
Note: To prevent the SMTP settings from being displayed in Outlook on the web, change the value from
$true
to $false
.How do you know this step worked?
To verify that you've configured Outlook on the web to display the SMTP settings for authenticated SMTP clients, perform the following steps:
- Open a mailbox in Outlook on the web, and then click Settings > Options.
- Click Mail > Accounts > POP and IMAP and verify the correct SMTP settings are displayed.Note: If the SMTP settings that you configured don't appear as expected in Outlook on the web, run the commands
net stop was /y
andnet start w3svc
to restart Internet Information Services (IIS).
How do you know this task worked?
![Server Server](https://www.sendcloud.net/doc/en//resources/foxmail.jpg)
To verify that you've configured the authenticated SMTP settings on the Exchange server, perform one or more following procedures:
- Use the Test-PopConnectivity or Test-ImapConnectivity cmdlets, which use authenticated SMTP to send test messages. For more information, see Test-PopConnectivity and Test-ImapConnectivity.
- Enable protocol logging on the 'Client Frontend <Server name>' Receive connector, configure a POP3 or IMAP4 client to connect to a mailbox, send a test message from an internal network connection and/or an external Internet connection, and view the results in the protocol log. For more information, see Protocol logging.Note: You can't use POP3 or IMAP4 to connect to the Administrator mailbox. This limitation was intentionally included in Exchange 2016 and Exchange 2019 to enhance the security of the Administrator mailbox.
Microsoft declared its plans and ideas of on-premises Exchange Server at the Ignite 2017 conference. They are calling this new version “Exchange Server 2019.” The preview will be revealed in mid-2018 and the release is supposed to occur in the second half of 2018. The other releases of the Exchange Server were:
- Exchange 2016 in late 2015
- Exchange 2013 in late 2012
- Exchange 2010 in late 2009
It can be observed that Microsoft releases a typical new version after every 3 years, with the RTM of the newly launched version is marginally preceding the year that it is named with.
In the first step, new features were added in Exchange Online. Then, this initiative made its way to the development of on-premises Exchange. For instance, some modifications done in the Exchange 2013 era have not appeared as on-premises until the Exchange server 2016 was released.
However, Microsoft does not make any particular declarations till now. The predictions for Microsoft Exchange Server 2019 depends on the slideshow that Microsoft called out, some convection, previous patterns, and the practicability of carrying cloud modifications to the on-premise architecture.
Expected Features To Be Seen In Exchange Server 2019
- Less dependency on the operating system and the Active Directory which are out of mainstream support will be excluded. This will establish Windows Server 2012 R2 as the minimum OS required. If the Exchange Server 2019 (announced at Ignite 2017) RTM is before 2018 when Windows 2012 R2 goes into expanded compatibility, the minimum requirement will be AD. If the Exchange server 2019 RTM is later, the minimum requirement can be set to Windows Server 2016 instead.
- The services which were disapproved in Exchange 2016 will be completely eliminated in the Exchange Server 2019. It implies the closure of RPC-over-HTTP, which is replaced by the reformed MAPIhttp protocol. MAPThttp protocol is adaptive by all the Outlook clients that are present in either mainstream or the extended support so, the need of retaining RPC-over-HTTP does not emerge. This also means the elimination of “Outlook Anywhere” as the programmable Client Access namespace, and the MAPI virtual directory is taking its place.
![Foxmail Microsoft Exchange Server Foxmail Microsoft Exchange Server](/uploads/1/2/5/7/125718317/324942882.jpg)
- The minimum supported email client is MS Outlook 2013. By the time Exchange 2019 will be launched, Office 2013 will not be included in the mainstream. It is appropriate to demand the brand-new operating system for a newly launched Exchange edition. But it is not fair to demand users to update the overall Office client arrangement. It is predicted that Office 2019 will not be launched early because Microsoft requires N-1 clients for Exchange Server 2019, so they will hold the support of Outlook 2013 to satisfy the users, maybe via an update launched that is needed for best performance and compatibility.
- Outlook on the network will be upgraded to the recent Exchange Online customer’s experience (they are very near today but, the EXO edition will keep evolving).
- Microsoft will extract some more improvements in performance from the database engine. Exchange 2016 amends storage IOPS and examines performance, and in recent times, increase the maximum specialization of hardware, that can be used to scale only Exchange server up to. If the scale is given on which the Exchange Online runs at, Microsoft always tries harder to make it further better, and due to this on-premise customers will be in profit as well.
- The architecture of Server role will not be changed. DAG (Database Availability Group) is a high availability and site resilience illustration from Exchange 2010, and it forms the foundation of HA/SR in Exchange Online. To fulfill the demands of customers, edge transport will remain as the available role.
- The size capacity allotted to the public folders will increase. However, no drastic change will be noticed in the case of features.
- The cross-premises objections of hybrid deployments, for instance, mailbox permissions, calendar sharing, delegates, etc., will keep getting better.
- Migration will be smooth, as noticed by the other capacities of Exchange server 2013 and 2016.
These are some of the Exchange Server 2019 features, which are expected to be seen in the launch of this latest version.
The Final Words
Microsoft keeps getting better and aims to provide distinct solutions for users of on-premises. One such innovation is Exchange Server 2019. It is believed that Exchange 2019 will follow the arrangement and architecture of Exchange 2016. The only difference is some extra and advanced features will be added. On comparing different versions and assumptions, the brand new features of Microsoft Exchange Server 2019 are predicted here.
For More Technical Updates Visit: http://blog.systoolsgroup.com/