Import your messages or account from Outlook Express to Outlook

You can import e-mail messages from Outlook Express into Outlook. The process you use depends on whether the two e-mail programs are installed on the same computer or not. The Outlook Express Inbox folder is a single file, Inbox.dbx. Conversely, Outlook stores each message as an individual file. To transfer messages by using the Import and Export Wizard, you must first locate and copy the correct files from the computer where Outlook Express is installed to the computer where Outlook is installed.

  When outlook and outlook express are installed on same computer:           
1.In Outlook, on the File menu, click Import and Export.
2. Click Import Internet Mail and Addresses, and then click Next.
3. Click Outlook Express.
4. Select the Import mail check box.
5. Click Next.
6. Click Finish.
7. To save a copy of the import summary to your Inbox, click Save in Inbox.
  
When outlook and outlook express are installed on different computer:
    
    Copy Outlook Express folder
1.On the computer where your Outlook Express account is set up, in Outlook Express, on the Tools menu, click Options.
2. Click the Maintenance tab.
3.Click Store Folder, and then note the entire path shown in the field in the Store Location dialog box.
4. If necessary, modify the default view in Windows Explorer so that you can see hidden folders. The Outlook Express folder is located in a hidden folder.
5. Browse to the location that you found in the Store Location dialog box.
6. Do one of the following:
Copy the entire Outlook Express folder to removable media, such as a floppy disk, DVD, or portable memory device, and then copy it to the computer where Outlook is installed.
Copy the entire Outlook Express folder to a network location that the computer with both Outlook and Outlook Express has access to.
7. On the computer where Outlook is installed, open Outlook Express. If prompted to create an e-mail account, click Cancel.
8. On the Tools menu, click Options.
9. Click the Maintenance tab.
10.Click Store Folder and then click Change.
11. Browse to the location where you copied the Outlook Express folder, and then click the folder that you copied in step 6. Click OK.
12. To close the Store Location dialog box, click OK.
13. When prompted to use the new messages or replace them with messages from the old store location, click yes to switch to that store.
14. Close Outlook Express, and then open it again to complete the process.
Import Outlook Express messages into Outlook as mentioned above.

Read more »

Configuring the Outlook 2003 RPC over HTTP Client

The RPC over HTTP protocol allows your full Outlook 2003 MAPI clients to connect to Exchange 2003 Servers using HTTP/HTTPS. This solves the problem remote Outlook 2003 users have when located behind restrictive firewalls. The trick is to figure out how to properly configure the Outlook 2003 client to use this protocol. If you have remote users who need to access Exchange 2003 via Outlook 2003, then check out this article and see how to configure Outlook 2003 to use RPC over HTTP.

Internet connected organizations are coming to the realization that firewalls are useful for more than just inbound access control. The traditional way of thinking about firewalls is that they protect you from intruders located outside the firewall. Today’s firewall administrator realizes that the corporate firewall must not only control what comes into the network, but also what leaves the network. Many of us learned this lesson the hard way after having our networks infected with the Nachi virus.

Unfortunately, many firewall administrators go too far. In their attempts at controlling outbound access, they end up preventing outbound access to all protocols except for HTTP or SSL secured HTTP (HTTPS). This prevents remote users from accessing your Exchange Server using secure Outlook RPC connections via ISA Server 2000 Secure Exchange RPC publishing. Blocking secure RPC connections prevents your remote users from benefiting from the full Outlook MAPI client.
Microsoft realized the magnitude of this problem. Their solution is the RPC over HTTP protocol. This protocol allows remote Outlook 2003 clients to connect to Exchange 2003 Servers using HTTP or HTTPS. The RPC protocol commands and data are "wrapped" (as known as encapsulated) in an HTTP header. The firewall in front of the Outlook 2003 MAPI client only sees the HTTP header and passes the outbound connection through. The RPC over HTTP protocols allows your remote users to get around what might be considered an overly zealous approach to outbound access control.
The Outlook 2003 client connects to an RPC over HTTP proxy server. The RPC over HTTP proxy server can be a front-end Exchange Server running IIS 6.0 on Windows Server 2003, or the RPC over HTTP proxy server can be a machine running the IIS 6.0 RPC over HTTP proxy service on a machine that is not configured as a front-end Exchange Server. Microsoft’s documentation stresses the front-end/back-end Exchange configuration, but this configuration is not required. The Outlook 2003 client only needs to connect to a Windows Server 2003 machine configured as a RPC over HTTP proxy.
An example of such a configuration is shown in the figure below.

here are many ways you can make the RPC over HTTP proxy available to remote users. The most secure way, and the only way I recommend that you do so, is to use an ISA Server 2000 firewall to control inbound access to the RPC over HTTP proxy. The ISA Server 2000 firewall is able to inspect even SSL encrypted packets for dangerous exploits that might be hidden inside the SSL tunnel. Other firewalls are not able to evaluate the validity of the commands and data moving from a remote client to the RPC over HTTP proxy and put your network and Exchange Servers at unnecessary risk.
For more information on how to configure an ISA Server 2000 firewall to support secure inbound RPC over HTTP connections, check out the following series of articles:
Part 1 of this series can be found at:
http://www.msexchange.org/articles/rpchttppart1.html
Part 2 of this series can be found at:
http://isaserver.org/articles/rpchttppart2.html
Part 3 of this series can be found at:
http://www.isaserver.org/tutorials/rpchttppart3.html 
Part 4 of this series can be found at:
http://isaserver.org/tutorials/rpchttppart4.html 
You must use Outlook 2003 running on Windows XP Service Pack 1 to connect using the RPC over HTTP protocol. In addition, you must install the hotfix mentioned in Microsoft KB article Outlook 11 Performs Slowly or Stops Responding When Connected to Exchange Server 2003 Through HTTP. Download and install the hotfix before configuring a profile that allows the user to connect to the Exchange Server.
It is important to note that you must create the Outlook 2003 profile while the Outlook 2003 computer is on the internal network, or while the Outlook 2003 computer is on the Internet and can access the Exchange Server using RPC (TCP 135 – typically through an ISA Server 2000 secure Exchange RPC Publishing rule). You will not be able to create a new profile or change an existing profile to use RPC over HTTP if is does not have access to the Exchange Server via RPC (TCP 135).
This bears repeating: you will not be able to create a new Outlook profile when the Outlook client is not on the internal network and can access the Exchange Server using RPC via TCP 135. In addition, a user with an existing profile will not be able to alter the existing profile so that it can use RPC over HTTP if that client is not located on the internal network and can access the Exchange Server using TCP 135. The Outlook 2003 profile must be configured to use RPC over HTTP while that machine is connected to the internal network and can access the Exchange Server via TCP port 135.
Of course, there are always exceptions to the rule. The article Configuring Outlook 2003 for RPC over HTTP indicates that you should be able to use the Office Resource Kit to configure an Outlook 2003 profile that allows access to the RPC over HTTP severs without requiring RPC access to the Exchange Server. We have not tested this configuration. If you have used the ORK to configure such a profile, please let us know about your experiences on the message board at http://forums.isaserver.org/ultimatebb.cgi?ubb=get_topic;f=5;t=002315.

Configuring the Outlook 2003 RPC over HTTP Client

Perform the following steps to create the Outlook 2003 profile:

1. Click Start and then right click on the Outlook 2003 icon in the menu. Click on the Properties command.

2. Click the Add button in the Mail dialog box.

3. Type in a name for the profile in the Profile Name text box. Click OK.

 4. Select the Add a new e-mail account option in the This wizard will allow you to change the e-mail accounts the direction that Outlook uses page. Click Next.

5. On the Server Type page, select the Microsoft Exchange Server option and click Next.

6. On the Exchange Server Settings page, type in the FQDN of the front-end Exchange Server. This must be the same name used on the Web site certificate you have assigned to the front-end Exchange Server’s Web site. For example, we obtained a Web site certificate for the front-end Exchange Server’s Web site. The Common Name (CN) on the Web site certificate is owa.internal.net. Therefore we enter owa.internal.net in the Microsoft Exchange Server text box.

Type a user account name in the User Name text box. Click the Check Name button to confirm that the Outlook 2003 client machine can communicate with the front-end Exchange Server.
Put a checkmark in the Use local copy of Mailbox checkbox.
Click the More Settings button.

 7.You can change how Outlook detects the connection state on the General tab of the Microsoft Exchange Server dialog box. Do not make any changes here unless you have an explicit reason to do so.

 8. Click on the Advanced tab. Confirm that there is a checkmark in the Use local copy of Mailbox checkbox. The default selection is Download headers followed by full item.

 9. Click on the Security tab. Put a checkmark in the Encrypt information checkbox. I’m not sure this does anything when you use RPC over HTTP, but encryption is a good thing, so we’ll enable this checkbox anyhow.

10. Click on the Connection tab. Select the Connect using my Local Area Network (LAN) option. Put a checkmark in the Connect to my Exchange mailbox using HTTP, then click the Exchange Proxy Settings button.

 

 

11. You configure the specifics of the RPC over HTTP session in the Exchange Proxy Settings dialog box. Type in the FQDN to your front-end Exchange Server in the Use this URL to connect to my proxy server for Exchange text box. This is same name listed as the Common Name on the Web site certificate.

Put a checkmark in the Mutually authenticate the session when connecting with SSL checkbox. Put in the FQDN of the front-end Exchange Server (the same name listed on the Web site certificate) in the Principal name for proxy server text box. Use the format:
Msstd:FQDN For example, we use msstd:owa.internal.net for our published front-end Exchange Server because the Common Name on the certificate is owa.internal.net.
Put a checkmark in the Connect using HTTP first, then connect using my Local Area Network (LAN). This is an interesting setting, as its unclear what a "LAN" protocol is in contrast to an "HTTP" protocol. I assume it means to use unencapsulated RPC messages, but I can’t say that for sure.
In the Use this authentication when connecting to my proxy server for Exchange drop down box, select the Basic Authentication option. This forces you to use SSL, which is OK, because we are using SSL for our links.
Click OK on the Exchange Proxy Settings dialog box.

12. Click Apply and OK on the Microsoft Exchange Server dialog box.

 13. Click Next on the Exchange Server Settings page.

14. Click Finish on the Congratulations! Page.

15. Click OK on the Mail dialog box.

 16. Open Outlook 2003. You will be able to use HTTPS for the connection, as confirm in the Exchange Server Connection Status window. You can access the connection status window by right clicking on the Outlook 2003 icon in the system tray and selecting the connection status command right after you start up Outlook 2003.

Read more »

Use Gmail IMAP in Microsoft Outlook 2007

We’ve all been hearing about the new IMAP support in Gmail, but how do we access that from Outlook? Those of you that have been waiting patiently will be happy to know all the instructions are on this page.
Using IMAP we can synchronize email across multiple devices, since the mail stays on the server. You already stopped reading this part and skipped down to the instructions, didn’t you?
Enable IMAP in Gmail Settings
Open your Settings panel in Gmail, and then click on the “Forwarding and POP/IMAP” tab.

 Now click the Enable IMAP radio button, and click Save Changes.

Add Account to Outlook
Use the Tools menu you to open the Account Settings panel.

 If this is your first account you’ll be prompted for the wizard, otherwise you’ll need to click the New button under the E-mail tab.

 Now select the “Microsoft Exchange, POP3, IMAP or HTTP” option and hit next.

 Select the checkbox for “Manually configure server settings” and everything on that page will gray out. Hit the next button again.

 

Now select “Internet E-mail”  (Didn’t we just do this? This wizard is taking too long…)

Finally we can enter some settings! Add in all your personal information here.

Note: If you are outside of the US you may need to use imap.googlemail.com and smtp.googlemail.com instead of imap.gmail.com and smtp.gmail.com.
Note: for Gmail Apps accounts, you’ll need to put in your full email address wherever you see an @gmail.com above. For instance, if your account was geek@howtogeek.com you would put that in the E-mail address field as well as the User Name field.
Click on the “More Settings” button and find the Outgoing Server tab, where you’ll need to check the box for “My outgoing server requires authentication”

Now choose the Advanced tab, and enter the following values (Very important)

• Incoming Server: 993
• Incoming Server encrypted connection: SSL
• Outgoing Server: 587
• Outgoing Server encrypted connection: TLS 

Note: If you are having an issue with your sent email not showing up in Gmail, you can use the Folders tab, and then select the [Gmail] \ Sent Mail folder.
Note: Only do this step if your mail is not showing up, otherwise it will duplicate the sent mail.

 Now that you’ve closed out that dialog, you can click the Test Account Settings button to make sure everything is going to work.

If all goes well, you should see a success message.

Note: Some ISPs restrict outgoing mail, so if you have a problem sending a test message you’ll need to consult with their documentation.
Accessing Your Mail
Now that everything is working you’ll notice a new set of folders for your Gmail account. (I’m using Gmail apps, which is why you don’t see an @gmail.com email address)
All of your labels will show up as separate folders, and the built-in “folders” in Gmail will be under the new [Gmail] folder.

Outlook Flags = Gmail Stars
If you want to star a message in Gmail, you just need to flag it in Outlook. When I flagged this message from Mysticgeek…

 It shows up in Gmail as a starred message. (And it works the other way too)

Sending Email from Outlook
To send a new email from your Gmail account, just change the “Account” drop-down to your Gmail address before you send a message.

Note that if you only use Gmail, you won’t have this drop-down and it will default to your Gmail.
Final Thoughts
Here’s a few things to keep in mind:

• Gmail Labels = Outlook Folders. To label a message, add it to a folder.
• Gmail Stars = Outlook Flags.
• Do Not move spam messages to the “Junk E-mail” folder in Outlook, move them to the [Gmail] \ Spam folder.
• Outlook has a built-in Search Folder for “Large Mail”, which will let you easily find messages with large attachments.

Now that you can access your starred and labeled messages, you can start using Outlook’s excellent Search Folders to find messages more easily.

Read more »

How to Configure Ms.Outlook pop3

This tutorial shows you how to set up Microsoft Outlook 2003® to work with your e-mail account. This tutorial focuses on setting up Microsoft Outlook 2003, but these settings are similar in other versions of Microsoft Outlook. You can set up previous versions of Microsoft Outlook by using the settings in this tutorial.

To Set Up Your E-mail Account in Microsoft Outlook

1. In Microsoft Outlook, from the E-mail Accounts menu, select Tools.

2. On the E-mail Accounts wizard window, select Add a new e-mail account, and then click Next.

3. For your server type, select POP3 or IMAP, and then click Next.

4.

1. On the Internet E-mail Settings (POP3/IMAP) window, enter your information as follows:

Your Name

Your first and last name.

E-mail Address

Your email address.

User Name

Your email address, again.

Password

Your email account password.

Incoming mail server (POP3)

POP, Pop.secureserver.net or IMAP, imap.secureserver.net.

Outgoing mail server (SMTP)

Smtpout.secureserver.net

Click More Settings.


NOTE: "smtpout.secureserver.net" is an SMTP relay server. In order to use this server to send e-mails, you must first activate SMTP relay on your e-mail account. Log on to your Manage Email Accounts page to set up SMTP relay. If you do not have SMTP relay set up and your Internet Service Provider (ISP) allows it, you can use the outgoing mail server for your Internet Service Provider. Contact your Internet Service Provider to get this setting.





5. On the Internet E-mail Settings window, go to the Outgoing Server tab.
6. Select My outgoing server (SMTP) requires authentication. 
7. If you did not change the SMTP relay section, select Use same settings as my incoming mail server. If you changed the user name and password in the SMTP relay section of your Manage Email Accounts page, select Log on using and enter the user name and password. The following example assumes you did not change your SMTP relay section in your Manage Email Accounts page. 



 8. Go to the Advanced tab, and then change the Outgoing server (SMTP) port to 80 or 3535.
9. Click OK.





10. Click Next.





11. Click Finish.


 


NOTE: As a courtesy, we provide information about how to use certain third-party products, but we do not endorse or directly support third-party products and we are not responsible for the functions or reliability of such products. Outlook 2003® is a registered trademark of Microsoft Corporation in the United States and/or other countries. All rights reserved.

Read more »