‏הצגת רשומות עם תוויות Exchange. הצג את כל הרשומות
‏הצגת רשומות עם תוויות Exchange. הצג את כל הרשומות

יום חמישי, 29 בדצמבר 2011

Exchange 2010 Setup: Unable to read data from the Metabase. Ensure that Microsoft Internet Information Services is installed

Open Power Shell in elevated mode (run as administrator)
  1. Type the following (or copy paste)
    • Import-Module ServerManager
    • Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart
  2. The second command will install the required components and reboot the server
  3. After reboot, open the Power Shell again in elevated mode.
  4. Type this to set NetTcpPortSharing service to automatic.
    • Set-Service NetTcpPortSharing -StartupType Automatic
  5. Close the Powershell. Try running Exchange 2010 setup again.


יום חמישי, 28 באפריל 2011

Configure OMA in Exchange 2003

Configure OMA in Exchange 2003

One of the coolest things in Exchange Server 2003 is it's ability to allow mobile users to connect to it via a stripped down version of Outlook Web Access called (you guessed right) "Outlook Mobile Access", or OMA for short.
Exchange Server 2003 enables any device capable of running the Windows Mobile 2002 or later, such as browser-enabled cell phones or Windows Mobile–based Personal Digital Assistants (PDAs) to access corporate Exchange information. All changes made on the wireless device are reflected in the live mailbox and can be seen from a full desktop mail client such as Outlook 2003 or Outlook Web Access (OWA).
The best thing about OMA is that it is practically configuration-free. almost nothing to worry about and no buttons to click. Just install Exchange Server 2003 and you're almost ready to go.

Requirements

In order to successfully implement OMA on your organization you need the following:
Lamer note: Make sure you have all things set up and that your Exchange organization is flawlessly working. We do not want to blame OMA for messing up your settings, because it won't.
Pre-SP1 installations of Exchange Server 2003 required that you install .NET Framework 1.1 Device Update 4.0. If, for some strange reason, you do not want to install SP1 for Exchange, make sure your install DUP. SP2 does not require any additions.
Any mobile phone or mobile device–based browsers that support HTML, XHTML, or Compact Hypertext Markup Language (cHTML) can be used to connect to OMA. For a list many supported devices click HERE.

Enabling OMA

As stated above, you actually do not need to install anything to get OMA up and running.
  1. Open the Exchange System Manager.
  2. Navigate to the Global Settings folder, expand it and go to Mobile Services. Right-click Mobile Services and choose Properties.
  1. In the Mobile Services properties window, under Outlook Mobile Access, click to select the Enable Outlook Mobile Access and the Enable Unsupported Devices check boxes.
  2. Click Ok.

Firewall and Internet connection

I won't go into detail here, but you should make sure that your Firewall allows TCP Port 80 and 443 (optional) to your server (the Exchange server that holds the OMA site) and to the following URL: http://FQDN/OMA (replace FQDN with the Fully Qualified Domain Name of your server).
In cases where your organization uses a Front-End/Back-End topology, you should allow access to the Front-End server(s).

SSL and security

You can protect the OMA traffic by using SSL. Read the following article on how to do that: Configure SSL on OMA.

Enabling/Disabling per user settings

By default, all mailbox-enabled users have OMA enabled. If you want, you can disable OMA on a per-user basis, while retaining the OMA functionality for other users.
Do disable (and later enable) a specific mailbox-enabled user from using OMA perform the following steps:
  1. On your Exchange server, open Active Directory Users and Computers.
  2. Navigate to (or find) the required user account.
  3. Double-click the required user account, or right-click it and select Properties.
  4. Go to the Exchange Features tab, select Outlook Mobile Access, and press the Disabled button.
  1. Click Ok all the way out.
To re-enable OMA for the specific user, reverse your actions.

Test OMA

You should now Test OMA in Exchange 2003 from a regular web browser (just to see that it's working), from any Pocket Explorer or WAP browser emulator (as I did with the following screenshots) or from your mobile phone/Pocket PC/Palm OS.
Provide your username and password:
Begin browsing your mailbox:

Working with OMA

As with Outlook Web Access (OWA), as long as you maintain a connection to your server you can browse and work with your mailbox.
Most settings and options are self explanatory, such as browsing the folder tree:
Answering mail:


יום ראשון, 10 באפריל 2011

Running Evolution with Exchange 2007

The Evolution MAPI provider adds support for Microsoft Exchange, including Exchange 2007, to the Evolution groupware suite, using the proprietary MAPI protocol. Unlike the Exchange connector (in the evolution-exchange package), it does not use Outlook Web Access and requires direct access to the Exchange server. (dpkg package description)
To install this package in Ubuntu,
$ sudo apt-get install evolution-mapi

You can use dpkg to know more about evolution-mapi after installing it

$ dpkg -s evolution-mapi

יום ראשון, 27 במרץ 2011

שעון קיץ 2011 - טיפול בבעיית שעונים,לוחות שנה,פגישות,אייפון,בלקברי

מאמר מקיף מטעם מיקרוסופט בנושא כיוון שעון קיץ ל - 2011
http://www.microsoft.com/israel/support/tips/other/DaylightSavingTime.aspx

הורדת עדכון לטיפול בנושא:
http://support.microsoft.com/kb/2443685

בונוס: מאמר בנוגע לעדכון שעון קיץ בבלקברי (בחסות אורנג'):
http://www.orange.co.il/he-il/support/BB_clock/

השנה בנוסף לתזוזות הפגישות בתקופת סיום שעון הקיץ,
תזוזנה הפגישות בין התאריכים 26.3 (סיום תקןפת שעון החורף לשנת 2010) ל - 1.4 (סיום תקןפת שעון החורף לשנת 2011).
בכדי לפתור את הבעיה, יש לפעול באחת משלושת הדרכים הבאות:
·         הרץ את Tzmove לפי מאמר 931667.
·         הזז את הפגישות הנ"ל באופן ידני.
·         הרצת Exchange update calendar tool לפי המאמר הבא:
http://msexchangeteam.com/archive/2008/08/15/449583.aspx
§         יתכן היסט של שעה בזימוני פגישות מול ארגונים אחרים.
§         פגישות בסביבה בינלאומית ייקבעו בהיסט של שעה.

מדוע נדרש לעדכן את Outlook ו Exchange?
o        תוכנת ה Outlook מתחשבת בשלושה גורמים בעת קביעת פגישה:
א)      השעה הנוכחית בתחנת המשתמש,
ב)      אזור הזמן בו נמצאת תחנת העבודה (מורכב מזמן GMT והיסט) – לדוגמה: בישראל GMT+2)),
ג)       הגדרות המעבר לשעון קיץ בתחנה.

o        שרתי 2003 Exchange משתמשים בשעון ובאזור זמן, כאשר עובדים עם ממשק CDO (Collaboration Data Objects) - לדוגמה עבור Outlook Web Access ועבור Auto Accept Agent.
רכיב ה CDO בשרת ה Exchange מכיל טבלה קבועה (ועצמאית) של אזורי זמן, המבוססת על אזורי הזמן הקיימים כברירת מחדל במערכת ההפעלה. אי לכך, שינוי כלשהו בהגדרות אזור זמן במערכת ההפעלה לא ישנה את הגדרות אזור הזמן בטבלת רכיב ה CDO.
o        בכדי להתגבר על בעיה זו, יש להתקין תיקון KB924335, אשר גורם למנגנון ה – CDO, לקחת את הגדרות שעון הקיץ ישירות ממערכת ההפעלה (עדכון זה מצריך אתחול לשרת הדואר).
o        לשרתי Exchange 2007 / 2010 לא נדרש תיקון DST, אלא רק תיקון למערכת ההפעלה.

הנחיות לעדכון שעון הקיץ:
בדומה להשלכות שתוארו לעיל, גם ההנחיות להתמודדות עם שעון הקיץ משתנות מארגון לארגון. תרשימי הזרימה הבאים יובילו להנחיות המתאימות לארגונך. לקבלת ההנחיות לגבי מוצרים שאינם מבית מיקרוסופט יש לפנות לספקים השונים.
פירוט בנושא סדר הפעולות המלא מופיע ב: http://support.microsoft.com/gp/dst_topissues.
רשימת מוצרי מיקרוסופט המושפעים מהזזת שעון הקיץ וההנחיות בנושא מופיעים באתר http://support.microsoft.com/gp/dst_prodlist. הרשימה מתייחסת לשינוי שעון הקיץ בארה"ב ואופן הטיפול במוצרים השונים בהיבטי השינוי שהתרחש בארה"ב.

יום שני, 10 בינואר 2011

How To Convert from Mixed Mode to Native Mode in Exchange

This article describes how to convert a Microsoft Exchange 2000 organization or a Microsoft Exchange 2003 organization that is currently running in mixed mode to native mode. Follow these steps after the last Exchange 5.5 server in the organization is upgraded or before the last Exchange 5.5 server is decommissioned.

Exchange 2000 and Exchange 2003 Mixed Mode

An organization running in mixed mode can accommodate all versions of Microsoft Exchange. By default, Exchange 2000 and Exchange 2003 is installed in mixed mode.

Exchange 2000 and Exchange 2003 running in mixed mode is subject to the following limitations:
  • Exchange Server 5.0 and 5.5 sites are mapped directly to administrative groups.
  • Administrative groups are mapped directly to Exchange Server 5.0 and 5.5 sites.
  • Servers cannot be moved between administrative groups.
  • Routing group membership consists only of servers that are installed in the administrative groups.

Exchange 2000 and Exchange 2003 Native Mode

An organization running in native mode can accommodate only Exchange 2000 or Exchange 2003 computers. New Exchange Server 5.0 or 5.5 computers cannot be introduced into the organization.

You can switch an Exchange 2000 or Exchange 2003 organization to native mode after all of the servers in that organization are upgraded to Exchange 2000 or Exchange 2003. You cannot switch to native mode until you either upgrade or decommission all earlier versions of Exchange Server.

The following are some of the features of Exchange 2000 and Exchange 2003 native mode:
  • Support for multiple routing groups within a single administrative group.
  • Routing groups can consist of servers from multiple administrative groups.
  • Ability to move servers between routing groups.
  • Ability to move mailboxes between servers in different Administrative Groups within an organization.
  • Simple Mail Transfer Protocol (SMTP) is the default routing protocol.
  • An administrative group does not have to contain any routing groups and a server can belong to an administrative group without belonging to a routing group within that administrative group.

Determine the Mode of the Exchange Organization

By default, an Exchange 2000 or Exchange 2003 server is installed in mixed mode. To determine which mode your Exchange organization is currently running in:
  1. Start Exchange System Manager. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
  2. Right-click the organization that you want to determine the mode for, and then click Properties.
  3. Click the General tab. The operating mode of the organization is displayed Under Operations Mode.

When to Switch from Mixed Mode to Native mode

The following scenarios are good candidates for conversion to native mode:
  • There are no Exchange 5.5-based servers in your organization.
  • There are no plans to add Exchange Server 5.5 servers to your organization in the future.
  • Your organization will never require interoperability between Exchange 2000 or Exchange 2003 and servers running earlier versions of Exchange Server.
  • Your organization does not use any connectors or gateway programs that run only in Exchange Server 5.5.

Change from Mixed Mode to Native Mode

Before you can change an organization from mixed mode to native mode, all of the computers in the organization must be running Exchange 2000 or Exchange 2003. The switch to native mode cannot be reversed. Review the implications of this switch before proceeding.

After you upgrade or remove all versions of Exchange Server prior to Exchange 2000, you can switch your Exchange 2000 or Exchange 2003 organization to native mode by using Exchange System Manager:
  1. Start Exchange System Manager. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
  2. Right-click the organization, and then click Properties.
  3. Click the General tab, and then click Change Mode under Change Operations Mode. Click Yes if you are sure that you want to permanently switch the organization's mode to native mode.

יום שלישי, 14 בדצמבר 2010

How to increase the Exchange Server 2003 Service Pack 2 18-gigabyte database size limit

הבעיה:
שרת הדואר Exchange Server 2003 Service Pack 2 מוגבל ברמת ה- DB כברירת מחדל לגודל מקסימלי של 18GB
ניתן בצורה יחסית קלה ופשוטה להגדיל את המגבלה עד ל - 75GB

הסבר כיצד להגדיל את המגבלה  ל - 75GB:

How to increase the Exchange Server 2003 Service Pack 2 18-gigabyte database size limit

New functionality has been included with Microsoft Exchange Server 2003 Service Pack 2 (SP2). You can now configure database size limits.

The database size limits for Microsoft Exchange Server 2003 Standard Edition have been increased from 16 GB to 18 GB. The limit can be increased to as much as 75 GB by using a registry key.

Microsoft Exchange Server 2003 Enterprise Edition does not have a maximum database size limit.

To increase the Exchange Server 2003 SP2 database size, follow these steps:

Important Before you increase the maximum size of an Exchange database, verify that sufficient hard disk space is available for the larger database.
  1. On the computer that is running Exchange 2003 SP2, click Start, click Run, type regedit, and then click OK.
  2. Click one of the following registry subkeys, as appropriate for the store that you want to increase:
    • For a mailbox store, click the following registry subkey:
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Private-Mailbox Store GUID
    • For a public folder store, click the following registry subkey:
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Public-Public Store GUID
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. In the New Value #1 box, type Database Size Limit in Gb, and then press ENTER.
  5. Right-click Database Size Limit in Gb, and then click Modify.
  6. Click Decimal, and then type an integer from 1 to 75 in the Value data box.

    Note These integer values represent the maximum size of the database in gigabytes (GB). For example, a value of 75 represents a database that has a maximum size of 75 GB.
  7. Click OK, and then exit Registry Editor.
  8. Restart the Microsoft Exchange Information Store service. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, type the following command, and then press ENTER:
      net stop msexchangeis
    3. After the Microsoft Exchange Information Store service has stopped successfully, type the following command, and then press ENTER:
      net start msexchangeis
  9. Examine the Application log to verify that the database size has been set successfully. To do this, follow these steps:
    1. Click Start, click Run, type eventvwr, and then click OK.
    2. In the Event Viewer tool, click Application.
    3. Double-click event ID 1216 to verify that the database size has been set successfully.




הערות:
1. כשמתחילים להתקרב למגבלת הגודל ( 18 גיגה במקרה של ברירת המחדל ו 75 גיגה במקסימום) יופיעו הודעות ב - EVENT LOG וכשממש נהיה קרובים למגבלה, ה - service של ה - information store לא יעלה באופן אוטומאטי ועשוי להגיע עד למצב שלא נוכל לבצע mount ל - information store

2. הגבלת הגודל אינה חלה על גרסת Enterprise

מידע נוסף:
1. Exchange 2007 standard SP1 מוגבל ל – 250 גיגה
http://blog.sembee.co.uk/post/Exchange-Database-Size-and-Limits.aspx

מידע נוסף גם ניתן לקבל כאן:
http://technet.microsoft.com/en-us/library/bb218437(EXCHG.80).aspx


2. Exchange 2010 standard SP1 מוגבל ל – 1024 גיגה
http://technet.microsoft.com/en-us/library/bb232092.aspx

יום שישי, 1 בינואר 2010

Exchange 2003 configuration step by step

Configuring your new Exchange 2003 server for internet email with POPcon for downloading the email from POP3 mailboxes isn't hard if you just do it step by step as shown in this configuration sample. In this guide we will step through a sample installation of Exchange 2003 for a company we will call "Mycompany". Mycompany consequently owns the internet domain name "mycompany.com".
Actually it only takes these simple steps:
And this is how to configure the Exchange Server to accept email for a domain like "mycompany.com" and cooperate with POPcon:

First install the Exchange server software from the CD or DVD. You may have to go back to the "Add/remove Software" utility in the control panel to add NNTP support if you did not do so during initial setup of your windows installation. Then open the Exchange System Manager and configure the new Exchange installation.

1. Adding your internet domain name to the recipient policies

Open the Exchange System-Manager. It should look like this:

One of the problems most often encountered when configuring an Exchange 2003 Server system is the fact that often the internet domain nane you want to receive email for ("mycompany.com") does not match your standard active directory domain name (i.e. "servername.mycompany.com"). The Exchange 2003 Server component handling incomming emails - the SMTP server - does not accept emails for other domains than the ones entered in the "recipient policies", even if you entered the correct email addresses ("user@mycompany.com") in the active directory.
To make Exchange accept email for additional domains like your internet domain you need to add the domain names to the default recipient policy like this:

On the main tree panel of the exchange system manager expand the tree "Recipients" and then click on "Recipient Policies". The policies will be shown on the right panel. Normally only the "Default Policy" will be there:


Open the properties of the "Default Policy" by double-clicking it:


In the Default Policy Properties please choose the tab "E-Mail Addresses". There you will find a list of domains supported by your exchange server. Usually only your internal active directory server domain will be listed here:

Like you can see, after installing our Exchange Server from scratch only our AD domain "Christensen.local" was listed as accepted SMTP address. But emails from the internet will be comming in addressed to "@mycompany.com" and not Christensen.local!

Choose "New..." here to add another accepted inbound domain. Since emails on the internet are sent via the SMTP protocol we want to add an "SMTP Address":

Now enter the domain name you want to receive email for. Please add a leading "@" to the domain name. This is what we entered to support emails addressed to @mycompany.com:


This is how the Default Policy Properties look like after entering the additional SMTP domain:


Enable the newly created entry with a check mark next to it:

When you OK the above dialog, Exchange will ask you with the next dialog box if you want to add the new address to all new users. Usually you do want exactly that to save some typing later.

Please note: You may need to restart your server to activate the new domain!

2. Configuring the SMTP server for inbound email

Next we will configure the SMTP-Server. This is the part of Exchange that accepts incomming emails from POPcon. No special settings are needed to work with POPcon but these are the standard settings in any case:

You will find the settings for the SMTP server under Servers/Protocols/SMTP/Default SMTP Virtual Server. Open the properties by right-clicking on the Default SMTP Virtual Server and choosing "Properties":

The settings on tab "General" can normally be left to the defaults.

On the tab "Access" you can find some configuration settings that might interfere with POPcon.



POPcon only works with a standard SMTP connection WITHOUT authentication, so allow "Anonymous access" in the "Authentication" dialog:


Choose "Connection" to grant or refuse the right to connect to the SMTP server to individual or multiple IP Address Ranges. Please ensure the system POPcon runs on does have the right to connect granted. With this setting ALL systems will have access to your SMTP server:


Under "Relay..." you can assign the right to relay through your SMTP-Server to some systems. This might be needed in some configuration and to be sure you should grant the system POPcon runs on relay rights. All other systems will need to authenticate before accessing the SMTP server to prevent unauthorized users using your system to relay spam:





Under the "Messages" tab you can restrict message size and number of messages accepted for each connection. Please make sure these settings are liberal enough to allow POPcon to transmit large messages to your server.

Also, on this tab you can choose an internal additional recipient for copies of the non-delivery reports. These NDRs will be sent back to senders of mails addressed to recipients unknown in your Exchange Server and they include a copy of the original message sent. You can use these postmaster copies of the NDRs to manually forward emails sent to mistyped recipients to the correct users.





Under tab "Delivery" some more configuration settings for outgoing emails can be found:




3. Adding the SMTP Connector for outbound emails

Now we need to add an SMTP-Connector (vs. SMTP Server) to handle outgoing email to the Internet.

Right-click "Connectors" in the Exchange System Manager and choose "New", "SMTP-Connector" to start adding the new connector and name it appropriately (like "SMTP-Out" in our case):


On the "General" tab you can now choose wether Exchange will send outgoing emails directly to the recipients system ("Use DNS...") or if all emails should be relayes through a SMTP relay server ("smart host").
The first option, DNS, is more direct but can sometimes cause problems when you use a dialup internet connection because some recipient systems will not accept emails that are coming from you ISP's dialup IP range while pretending to come from your real internet domain. Sending via your ISP's smart host / smtp relay server is the better option in this case. We chose our ISPs smtp relay server here.


Also, on this tab you need to add the "local bridgehead" server (as shown above)
On the tab "Address Space" we need to add a wildcard address space for SMTP. We want to allow emails to any domain, so we use the wildcard "*" here:

Side note about the "Cost" entry: If you want to send emails to some domains via a different route you can create multiple SMTP connectors and set the "Cost" entry of this wildcard connector to a higher value while setting the cost entry of the special domain route to a lower cost but with only the special domain allowed on this page. This is especially useful if you generally want to send via DNS and only route to some systems that won't accept your email via some relay server.

If your ISP's SMTP server requires authentication (and almost all of them do today) you can set the username and password on the "Advanced" tab of the SMTP connector. Select "Outbound Security":


Select "Basic authentication" and chose "Modify" to enter the username and password:





And that's alreay it - Your Exchange is now configured to send email to the internet and receive an SMTP email feed like it will come from POPcon or a direct internet connection. All you should do now is configure your users' email addresses in the Active directory.


4. Configuring your user's email addresses in the Active Directory

You can set one or multiple email addresses for each user to receive email at. We will step through the neccessary actions when creating a new user called John Galt.
First open the active directory and right-click the "Users" item to select "New", "User":
[Image]
The resulting dialog will allow you to create a new AD user to log into your server and creates an Exchange mailbox all in one wizard pass:
[Image]
Next...
 
[Image]
Next...
 
[Image]
Now the wizard continues into the Exchange Server realm and lets us create a new exchange mailbox
 
We just accepted the default alias here. Next...
 
[Image]
Ok, fine - but wait: What about our desired email address? john@servolutions.com? We need to add this mail address manually. We are back at the AD configuration console and select the properties of our new user "John Galt" by right-clicking on the name:
 
[Image]

Lot's of tabs on this resulting dialog:
 
[Image]
We go to the "E-mail Addresses" tab:
 
[Image]
 
And surprise: john@servolutions.com is already there, but in suspiciously non-bold print. Actually, Exchange automatically entered this additional email address because we choose so during the editing of the default recipient policies. But we want this address to be the primary address meaning all email sent by John will get this address as the "senders" and "reply" addresses in the mail headers. So we click on "Set As Primary" and are done:
 
[Image]
We could also add more email addresses like info@servolutions.com or sales@servolutions.com but only one of these addresses can be the primary address that will be the default senders' address in all emails sent out by john.
And that's really it - just step through you other user's AD entries and set the appropriate primary and additional email addresses.


5. Installing and configuring POPcon or POPcon PRO

After going through the above 4 steps your Exchange is configured to send out email but it still can't pull down email from POP3 or IMAP mailboxes on your provider server. For this you need to install and configure POPcon.
Configuring POPcon is quite straightforward. You need to follow these steps:
a) Configure a Postmaster email address on the GENERAL configuration tab.
b) Add one or more POP3 mailboxes on the POP3/IMAP tab.
c) Configure the Exchange server name on the EXCHANGE configuration tab.

Download and run the self-extracting installer of POPcon or POPcon PRO and follow the instructions during the installation. It will install the POPcon Administrator program and the POPcon service that runs in the background on your system.
Run POPcon Adminstrator from Start > Programs > POPcon
POPcon Administrator

POPcon Screenshot

Click on "Configure" to open up the POPcon configuration screen.

a) Configure a Postmaster email address on the GENERAL configuration tab.

Screenshot of general options tab in POPcon PRO
On this first configuration page you only need to enter the email address of your Postmaster or Administrator user. The Postmaster will receive all emails without a valid recipient as well as general POPcon status notifications. It is very important to define a real email address from inside your exchange server here because mails can be lost irretrievably if POPcon forwards some mail with no recipient information to the postmaster and that account does not exist in your exchange server.
You can leave the log file options to their default settings for now.

Next go to the POP3/IMAP tab to configure the POP3 or IMAP mailbox accoutns you want POPcon to download email from.

b) Add one or more POP3 mailboxes on the POP3/IMAP tab.

POPcon PRO POP3 accounts configuration screenshot
POPcon PRO collects mail from as many POP3 accounts you like. Just click on Add to add another POP3 host or account to the list of Polled POP3 Hosts. For each server or account you need to fill in the POP3 server settings as shown below.
If you are using catch-all style mailboxes (mailboxes that receive email for a whole domain, regardless of the recipient part before the "@") POPcon needs to filter recipients from incoming mail so only the recipients at your own internet domain are accepted. Please add the domain you consider your own in the "Accepted Recipient Domains" box. This is the same domain you configured earlier in the Exchange Default Policy.

Individual account settings

This dialog lets you input the specifics about a POP3 or an IMAP server you want to have polled by POPcon PRO.
This is the information POPcon PRO needs to know about each server:
Server type:
Here you can select on the four supported server types:
POP3: Default. POP3 servers are by far the most common mail server types on the internet.
POP3-SSL: Some POP3 Servers need SSL encryption enabled for the connection in order to protect passwords and sensitive information. Choose this type to have a SSL-encrypted connection to a POP3 server.
IMAP: IMAP Servers are also quite common and theoretically allow the client to manipulate email folders and move email between folders online. In our case the protocol is used to download email from the INBOX of the IMAP server to your exchange server.
IMAP-SSL: Supports SSL connections to IMAP servers for added protection.

Access:
Configure the server name, account name and password to connect to the mail server here.
Servername: The name the server you want to have polled. You can also enter the IP address directly.
Username: The username needed to log into your POP3 or IMAP mail server.
Password: The password needed to log into your mail server.
IP portnumber: Almost always the TCP/IP port for POP3 mail is 110. Under some circumstances, internet routers or firewalls change the port number. Please ask your network administrator or internet provider. The standard port for POP3-SSL is 995, for IMAP it is 143 and for IMAP-SSL this should be set to 993.
Timeout: Leave this to the default value.
Please ask your POP3 mailbox hosting provider if you do not have the above information.

Type of mailbox / distribution:
POPcon PRO supports both catch-all and single user mailboxes
Catch-all mailbox ("*@domainname.com"): For this type of mailbox, POPcon PRO will distribute the email retrieved from this server according to what it finds in the TO:, CC:, BCC: and other header-fields of the mail. If you choose this option, don’t forget to add your internet domain name(s) to the "Accepted Recipient Domains" box. on the POP3/IMAP configuration dialog
Single user mailbox ("user@domainname.com"): This type of mailbox receives email for only one specific Exchange mailbox. You need to specify the receiver of the email here. POPcon PRO will then direct all mail retrieved from this server to the recipient email address given here.

Delete / keep email on the server:
This block allows you to configure POPcon PRO to either delete email after downloading or keep it on your POP3 or IMAP server for a specified amount of time or indefinitely.
Delete downloaded email: This is the default setting – POPcon PRO will delete the Email on your POP3 or IMAP server after successfully downloading it.
Leave a copy of downloaded email (indefinitely): This option will cause POPcon PRO to leave a copy of the email on the server. Only use this option during testing or when you are sure the mail will be deleted eventually, i.e. by another system periodically downloading an deleting email.
Leave a copy of downloaded email for n number of days: Causes POPcon PRO to leave a copy of the email on the POP3/IMAP server for the specified number of days before deleting it. You can use this option to allow access to a single POP3 or IMAP mailbox by two different systems.

c) Configure the Exchange server name on the EXCHANGE configuration tab.

POPcon PRO SMTP/Exchange settings screenshot

On this configuration screen you can specify the Exchange™-(SMTP) Server you want the mail to be directed to. Normally this will be the computer name of your Exchange™ server (like "MYSERVER").
You can leave all other settings default

These three steps to configure POPcon will provide you with a working set-up. Test it out by confirming the new configuration with OK and then use the "Trigger mail retrieval" button on the POPcon Administrator main screen to start the first mail download. You can follow what is happening in the scrolling log display on that screen. Watch out for any error messages there. There is also a POPcon log file (c:\program files\POPcon\POPconSrv.log – open with notepad) that you can view at your leisure.

6. Check out the ChangeSender Outlook Add-in

ChangeSender Exchange Send-as Add-in adds one important piece of functionality to Microsoft Outlook when used with Exchange Server: It allows you to send as any of your email addresses and even group addresses or those of other users if allowed by the administrator. Effectively this is the Exchange Send-as function without the limitations of the ActiveDirectory
Without the ChangeSender Exchange send-as components, Exchange always sends out emails on your default email address fixed in the ActiveDirectory even when answering emails received on one of your additional email addresses. Also, Exchange does not allow sharing the same email address (i.e. department-wide or company-wide email addresses) between users. ChangeSender solves both problems by adding a configurable "send as" selection box to your Outlook email form.

ChangeSender Features
  • Automatically selects the right send-as address when replying to emails. ChangeSender uses the address of the original email as sender address for replies.
  • Easy selection of send as addresses for new emails via a new sender address selection box in Outlook.
  • Multiple users can send from the same sender address (i.e. send as sales@yourcompany.com or support@yourcompany.com)
  • Sender appearance fully configurable as "Any name" <any@address.com> for each individual email address. Does not show up as "sent on behalf of...".
  • Very simple installation and administration.
  • Administrator can restrict or allow user choices for the sender address and prevent users from sending as other users.
  • Works with Exchange 2010, 2007, 2003, 2000 and with Outlook 2010, 2007, 2003, 2002, 2000 versions.

ChangeSender in Outlook 2007 screenshot

Downloads
Download the free 30-day trial version of ChangeSender and test the full product without any restrictions until you are sure it meets all your requirements. Then just order license codes to remove the 30 day limit without re-installing.
ChangeSender consists of two separate components: A server component to be installed on the Exchange server and a Microsoft Outlook add-in component that is needed for each client. The Outlook add-in does not work without the server component installed as well.
Server component:
Download Exchange Send-as server component, Exchange 2000, 2003 version Install this on the Exchange Server (this version for Exchange 2000 or 2003)
Download Exchange Send-as server component, Exchange 2007, 2010 version Install this on the Exchange Server (this version for Exchange 2007 or 2010)
Client component / Outlook add-in:
Download Exchange Send-as Outlook add-in Install this on each user's system.

You can license ChangeSender Exchange Send-as online and will receive the license codes by email in just minutes.