Outlook for Mac 2011 Outlook for Mac can automatically set up accounts from many popular email service providers such as Outlook.com (previously known as Hotmail), AOL, Gmail, MobileMe, and Yahoo. If Outlook can't set up an account automatically, you can configure it manually. When setting up manually, you’ll need additional information about your account, for instance the account type and addresses of mail servers. Outlook supports both POP and IMAP accounts. To learn more about each account type, see. Set up an Exchange account.
Feb 8, 2012 - Outlook 2011 MAC does not sends Email (TLS currently unavailable). D) Outgoing server authentication is enabled (login same as incoming). Hi - I have outlook for mac (2016 version) and it only saves my emails for 7 days. I used to have outlook 2011 (for mac) and it kept all my emails. Once I upgraded to El Capitan it screwed up the way.
Open Outlook for Mac 2011. On the Tools menu, click Accounts. If this is the first account you're creating in Outlook 2011, under Add an Account, click Exchange Account.
If you've previously created an email account for a different email address, in the lower corner of the Accounts dialog box, click, and then click Exchange. On the Enter your Exchange account information page, type your email address. Under Authentication, make sure User Name and Password is selected. In the User name box, type your complete email address. In the Password box, type your password. Make sure Configure automatically is selected, and then click Add Account.
After you click Add Account, Outlook will perform an online search to find your email server settings. In the dialog box that asks if you want to allow the server to configure your settings, select the Always use my response for this server check box, and then click Allow. If Outlook is able to set up your account, you'll see the account you set up in the Accounts dialog box. Close the Accounts dialog box. If Outlook isn't able to set up your account, see the next section in this article. Add more email accounts.
On the Tools menu, click Accounts. In the lower-left corner of the Accounts dialog box, click Add, and then click E-mail. Enter your email address and password, and then click Add Account. If the Add Account button is unavailable. Enter the information about your account, including the following required fields: User name, Type, Incoming server, and Outgoing server.
If your email service requires Secure Sockets Layer (SSL) for either the incoming or outgoing server, select the Use SSL to connect check box for that server. Use the information from table below for Outlook.com accounts: Fields POP IMAP Incoming server pop3.live.com imap-mail.outlook. Com Port for the incoming server 995 993 Outgoing server smtp.live.com smtp-mail.outlook.com Port for the outgoing server 587 587 When the process of adding the account is complete, the account appears in the left pane of the Accounts dialog box, and Outlook begins downloading your messages. Notes:. Your email service provider may require you to enable POP or IMAP access through its Web site before you can use the account in Outlook.
If you add a POP account and another type of account, messages from the POP account appear in the Inbox under On My Computer in the folder list. With POP and IMAP email accounts, email messages are the only items that are synchronized between Outlook and the mail server. Other items that you create in Outlook — such as contacts, calendar events, tasks, and notes — are stored on your computer, not on the mail server. To delete an account, in the left pane of the Accounts dialog box, select an account, and then click Delete.
When you delete a POP account, existing messages from that account remain in Outlook, but no further messages are downloaded or sent. When you delete an IMAP account, all messages from that account are deleted from Outlook, but any copies of messages that you have on the server remain there. Items other than messages, such as contacts and events, are not affected when you delete a POP or IMAP account. Try the latest version of Outlook The latest version of Outlook for Mac makes it a breeze to add email accounts with just a username and password.
Configure authenticated SMTP settings for POP3 and IMAP4 clients in Exchange Server. 7/5/2018.
6 minutes to read. Contributors. In this article After you enable and configure POP3 or IMAP4 on an Exchange server as described in and, 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 ' 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:. 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.
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 ' 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. 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. 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 ' Receive connector to allow clients to send authenticated SMTP email. However, because port 25 is also configured on the 'Client Frontend ' 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. 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 topic.
For information about keyboard shortcuts that may apply to the procedures in this topic, see. Tip Having problems? Ask for help in the Exchange forums. Visit the forums at:,. Step 1: Configure the FQDN on the 'Client Frontend ' 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, 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: Get-ReceiveConnector -Identity 'Client Frontend.' Set-ReceiveConnector -Fqdn This example configures the FQDN value mail.contoso.com.
Get-ReceiveConnector -Identity 'Client Frontend.' Set-ReceiveConnector -Fqdn mail.contoso.com How do you know this step worked? To verify that you've successfully the FQDN on the 'Client Frontend ' Receive connector, use either of the following procedures:. the EAC, go to Mail flow Receive connectors select Client Frontend, click Edit ( ) Scoping, and verify the value in the FQDN field. In the Exchange Management Shell, run the following command: Get-ReceiveConnector -Identity 'Client Frontend.' Format-List Name,Fqdn 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.
Also, you need to assign the certificate to the Exchange SMTP service. For more information, see. To specify the certificate that's used for authenticated SMTP client connections, use the following syntax: $TLSCert = Get-ExchangeCertificate -Thumbprint $TLSCertName = '$($TLSCert.Issuer)$($TLSCert.Subject)' Get-ReceiveConnector -Identity 'Client Frontend.' Set-ReceiveConnector -TlsCertificateName $TLSCertName This example uses the certificate that has the thumbprint value 434AC2B26521298CE8834C514856AB. $TLSCert = Get-ExchangeCertificate -Thumbprint 434AC2B26521298CE8834C514856AB $TLSCertName = '$($TLSCert.Issuer)$($TLSCert.Subject)' Get-ReceiveConnector -Identity 'Client Frontend.' Set-ReceiveConnector -TlsCertificateName $TLSCertName How do you know this step worked?