Specifically, global catalogues. In any Windows-based domain environment, the domain is hosted by one or more domain controllers.

In the case of a single domain controller, all domain server roles are serviced by a single machine. While this is simplest, it is also not fault-tolerant.

In the case of multiple domain controllers (not member servers), domain server roles can be delegated amongst the available servers. i.e. the main server can be the PDC (primary domain controller), hosting the Global catalog while other servers take the RID and Infrastructure roles. While the RID, PDC, and Infrastructure roles are generally only delegated to provide load balancing, the Global Catalog role should be shared by multiple servers. The reason? The looming death of your domain, that's what.

The Global Catalog is critical to the function of your domain. Without a live global catalog no one can authenticate. No authentication means to function. This was something I had missed. Small, superscripted in the corner of the documentation. Missed. I had 2 DC's, with full replication of all domain data, including both Active Directory and DNS. But I only had one server hosting the Global Catalog. That one server happened to be the one that pooched, resulting in a secondary domain controller that assumed all roles (as it should have) but did not have a copy of the catalog. There were hours of hope, when I toiled deep in the recesses of that dank and dusty dungeon of dns and domain services. Hours of hope that turned to bitter despair as I learned of my folly. Global Catalog! How did I miss thee!

Suffice it to say, it is now standard practice, to enable each domain controller as a global catalog. (Active Directory Sites and Services->Sites->Site->Servers->Server->NTDS Settings->Click the check box!). I will only have 3 DC's (and then 2 DC's when the VMWare server is retired), so having each DC as a Global Catalog won't cause any network congestion. It WILL cause some redundancy, allowing my users to continue functioning even in the event of a catastrophic failure of any one server. Note to self: test that theory.

The other item I learned, is that Veritas can be...difficult to use, when it comes to restoring exchange mailboxes to any server but the one you backed them up from. For this reason it is of no value; the only time I need to restore mailboxes is in the event that the original server is defunct. For this reason I will be moving to a lower-level database backup instead of mailbox backup, which should work more reliably on replacement servers. For now a full dump of the virtual machine will suffice.

Earlier this year: server hiccups. Restarts spontaneously. Noted event log with vague statement concerning raid device not responding. No hard errors on any drives, all drives optimal. Anomoly?

Middling this year: server...burps. Hangs on blue screen, to the effect of inaccessable device. Same event logged as previous. No hard errors on any drives, all drives optimal. Cold boot restored function. Problem repeated shortly therafter. Determined that secondary hang was caused by the RAID controller attempting to initialize the RAID array during operation. Some 2 years after being initialized during the install. Difinitive anomoly. Cancelled initialization, barred future auto-intilization. Server back up, running smooth.

5 weeks ago (several months after last hang). Server crashes, hard. Fails to boot to raid array. When array finally boots, fails to boot windows. Intermittantly returns a BSOD or Blue Screen. Tried to determine if it was a hard drive issue or controller issue. No errors found in either court. Shut down, disconnected power. Left. Fired up a Windows Server 2003 vmware guest, started the process of rebuilding the DC and all related services from scratch. Well, not entirely.

In the first 48 hours after the crash (my poor weekend), I was able to recover all user data from the downed server. I was also able to recover all exchange mailboxes from the downed server. As well as all financial data. Note that I DID have a viable copy of all critical data available if necessary. I would have recovered the mailboxes from the backup, if the Veritas backup was capable of restoring to exchange. It was not. Due to Veritas' epic failure as a usable backup system for Exchange....I've ditched it and will use a simpler yet still effective method. I'll still use Veritas for everything else, just not Exchange. Nemisis! I was...frustrated by that. Moving on. Moved all data to a newer server (leaving the VMWare server to do the thinking), and set to fixing the myriad of services obliterated by the server failure. Note that none of these services needed to fail. I'll comment on THAT nugget of wisdom later. To sum: everything is back up and running, and is STILL running.

Een paar opvallende punten voor versie 2007 zijn verder:

• Alle rollen worden virtueel ondersteund, behalve de Unified Messaging rol.
• Virtuele disks moeten een vaste grootte hebben en mogen dus niet dynamisch groeiend ingesteld worden.
• De Exchange-eigen methodes voor hoge beschikbaarheid (zoals Cluster Continuous Replication en Single Copy Clusters) mogen niet gecombineerd worden met soortgelijke methoden die de hypervisor zelf aanbiedt. Tevens wordt aanbevolen om de Exchange-eigen methoden te gebruiken.
• Het maken van snapshots van virtuele machines waar Exchange in draait wordt niet ondersteund.
• Het aantal virtuele processoren mag niet groter zijn dan twee maal het totale aantal logische processoren. Het begrip logische processor is gedefinieerd als een core binnen een fysieke processor.
• Omdat Exchange erg I/O intensief is, wordt het aanbevolen om op omgevingen waar de I/O niet rechtstreeks wordt afgehandeld, geen andere I/O intensieve applicaties te draaien op dezelfde fysieke server.
• Voor backups wordt aangeraden om dit bij voorkeur binnen de virtuele machine te regelen. Het mag ook op hypervisor-niveau als deze Volume Shadow Copy Services (VSS) ondersteuning voor de virtuele machines biedt.

Bron: Microsoft TechNet.

لقد تم تصميم Exchange Server 2003 بحيث يعمل بشكل متداخل مع عدة عملاء.

الرسم التوضيحي 1: خيارات آمنة ومرنة للاتصال بـ Exchange Server 2003

في الرسم التوضيحي 1، يتم إظهار كل عميل وهو يصل إلى Exchange Server 2003 من خلال الإنترنت ويحميه خليط من جدران الحماية، وفي هذه الحالة المعيّنة، يعمل (Microsoft Internet Security and Acceleration Server (ISA Server كعبّارة ذات أمان محسّن لـ Exchange Server ولبنية تحتية لملقمات أخرى.

توافق Outlook

باستطاعة Outlook 2003، وOutlook 2002، وOutlook 2000 الاتصال بـ Exchange Server 20031. ولقد تم تصميم Outlook 2003 وExchange Server 2003 للعمل عبر اتصالات بالشبكة بطيئة، أو كامنة، أو ضعيفة. الأمثلة هي خطوط الطلب الهاتفي وارتباطات لاسلكية بالبيانات مثل 1xRTT وGeneral Packet Radio Service (GPRS). ميزات Outlook 2003 الجديدة تشمل:

الوصول عن بعد

لقم تم تحسين Outlook Web Access في Exchange Server 2003 لتوفير استخدام أكثر سهولة، وسرعة، وأمان أكبر. وترجع شعبية Outlook Web Access إلى أسباب عديدة منها سهولة استخدامه وتقديم الدعم له وعدم الحاجة إلى أي تثبيت. وباستطاعة أي كمبيوتر يستند إلى المستعرض الوصول إلى Exchange Server بأمان أكبر، ويتوجب على معظم المستخدمين في واجهة المستخدم الجديدة، النظر مرتين لمعرفة ما إذا كانوا يستخدمون Outlook 2003 أو Outlook Web Access. الميزات تشمل:

كما أنك تحصل على اعتماد S/MIME في Outlook Web Access بحيث يمكنك التوقيع رقمياً على رسائل البريد الإلكتروني وتشفيرها.

ActiveSync في Exchange Server

إن الأجهزة النقّالة التي تستند إلى Microsoft Windows Mobile، مثل كمبيوتر الجيب يصحبها عميل Microsoft ActiveSync وPocket Outlook المضمّن، مما يمكّنك من إجراء تزامن لرسائل البريد الإلكتروني، والتقويم، وقوائم جهات الاتصال مباشرة مع Exchange Server 2003. وباستطاعة المسؤولين في Exchange Server 2003 تمكين هذا الأمر من الشاشة نفسها المستخدمة لإدارة حسابات البريد الإلكتروني في Exchange Server.

Outlook Mobile Access

كما هي الحال في Outlook Web Access بالنسبة إلى برامج الاستعراض المكتبية، فلقد تم تصميم Outlook Mobile Access للوصول المحسّن الأمان من برامج الاستعراض للأجهزة النقّالة. ومع Exchange Server 2003، يستطيع المستخدمون الوصول إلى علب البريد الخاصة بهم اعتباراً من الأجهزة النقّالة بواسطة برامج استعراض صغيرة تستند إلى HTML، و(XHTML (WAP 2.x، وCHTML.

سيناريوهات الإنتاجية الواسعة الانتشار

إن الخيارات المرنة للوصول إلى المعلومات والطرق الجديدة للبقاء على اتصال تمكّن العاملين في مجال المعرفة من أن يكونوا أكثر إنتاجية وتسمح بالتحكم بوقت الاتصال وكيفية إجرائه.

إذا كنت لا ترغب في حمل جهاز الكمبيوتر المحمول، فأجهزة كمبيوتر الجيب، وكمبيوتر الجيب مع الهاتف المضمّن والهواتف الذكية التي تستند إلى Windows Mobile تمكّنك من مزامنة الجهاز اللاسلكي مباشرة مع Exchange Server. فتصبح رسائل البريد الإلكتروني، وجهات الاتصال، والجداول، والمرفقات بمتناول يدك.

توفير في المصاريف مع Exchange Server 2003

إن أدوات الترقية والإدارة في Exchange Server 2003 تزيد من إنتاجية العاملين وتساعدك على دمج الملقمات توفيراً للمصاريف.

سيناريو الدمج

بالنسبة إلى المؤسسات التي تستخدم Exchange Server 5.5، توفر الترقية فرصة كبيرة لتخفيض التكلفة الإجمالية للملكية جراء ما يلي:

يتفوق Exchange Server 2003 على Exchange 2000 Server بتصميمه الذي يتضمّن قواعد بيانات متعددة (تصل إلى 20 قاعدة بيانات بالملقم الواحد). وهناك 1000 إلى 2000 مستخدم للملقم الواحد في مؤسسات Exchange Server 5.5 النموذجية، ويتحدد ذلك بشكل أساسي بسبب هندسة قاعدة البيانات الواحدة والوقت المطلوب لإجراء عمليات النسخ الاحتياطي والاستعادة وإدارتها. غير أنه باستطاعة العدد المعتمد للمستخدمين وعلب البريد أن يكون بسهولة ضمن نطاق يتراوح بين 3000 و5000 أو أكثر، وذلك وفقاً لملفات التعريف الخاصة بالمستخدمين، وأنماط حركة سير الرسائل، والقيود الموضوعة على حجم علب البريد.

الإنتاجية الإدارية

إن Exchange Server 2003 مصمّم لمساعدة موظفي تكنولوجيا المعلومات المسؤولين عن تبادل الرسائل على أن يكونوا أكثر إنتاجية. فالإدارة الجارية لبيئة Exchange Server تمثّل حوالي 20 إلى 25 بالمائة من التكلفة الإجمالية للملكية لـ Exchange Server. وتساعد الأدوات الجديدة والمحسّنة موظفي تكنولوجيا المعلومات على أداء وظيفتهم بطريقة أكثر فعالية. فقد يحتاج أحد المدراء التنفيذيين مثلاً إلى استرداد رسالة بريد إلكتروني قديمة ولكنها هامة جداً تم حذفها منذ بضعة أشهر. ويستطيع المسؤول، بواسطة الميزة الجديدة Recovery Storage Group، استرداد علبة البريد العائدة لأحد المستخدمين للعثور على رسالة البريد الإلكتروني الهامة التي تم حذفها في السابق. وتشمل الميزات الإدارية الجديدة الأخرى:

إضافة إلى ذلك، يقوم Exchange Server Management Pack for Microsoft Operations Manager بأتمتة عملية مراقبة بيئة Exchange Server بأكملها، مما يوفر إدارة فعالة وحلاً سريعاً لمشاكل Exchange Server.

سيناريو نموذجي: الترحيل إلى Exchange Server 2003 من Exchange Server 5.5

جدول عملية انتقالك إلى Exchange Server 2003 بحيث تتناسب مع جدولك وميزانيتك. وباستطاعة Exchange Server 2003 العمل ضمن Windows 2000 أو Windows Server 2003 وهو مصمّم للتشغيل المتداخل مع Exchange Server 5.5 وExchange 2000 Server.

وتساعدك أدوات وموارد جديدة على الترقية من بيئة Windows NT 4.0 وExchange Server 5.5 إلى بيئة Windows وExchange Server 2003 بطريقة أكثر سلاسة، وسهولة، وسرعة.

للحصول على مزيد من المعلومات حول ميزات Exchange Server 2003 وقدراته، انظر صفحة ميزات Exchange Server 2003.

إجمالاً، يعتبر Exchange 2003 المنتج الذي سيستحوذ على الطلب مستقبلاً في سوق التعاون.   بي.جي. كونوللي محلل مسؤول مركز اختبارات InfoWorld

إذا كنت تعمل ضمن بيئة Exchange Server 5.5، فإن Exchange Server 2003 يقدم توفيراً كبيراً في التكاليف وذلك بعمله على ملقمات أقل. وبواسطة الموارد والأدوات الجديدة، تُعتبر الترقية والترحيل إلى Exchange Server 2003 عملية سلسلة، وسريعة، واقتصادية.

ويتوفر Exchange Server 2003 في إصدارين:

لتحديد الإصدار الذي يتناسب بشكل أفضل مع احتياجاتك المهنية، استكشف الجداول الموجودة على على صفحة مقارنة الإصدارات.

Microsoft Exchange Server 2007: The Complete Reference shows you how to configure a robust messaging environment, manage recipients and servers, set up mailboxes and public folders, and seamlessly integrate with Outlook 2007 and Outlook Web Access 2007. You'll learn to provide a multi-layered defense against spam, create reliable system backups, work with PKI and data encryption, use replication and clustering services, and maintain high availability and optimal efficiency.

• Set up, customize, and manage Exchange Server 2007
• Upgrade from and coexist with previous versions
• Understand the Exchange Server 2007 messaging system architecture
• Implement the significant new features Exchange Server 2007 Service Pack 1 provides
• Administer Mailbox, Transport, Client Access, and Unified Messaging Servers
• Take full advantage of Outlook 2007 and Outlook Web Access 2007
• Secure transactions using PKI, authentication, encryption, and the Forefront suite
• Comply with applicable legal standards and regulations
• Back up and restore Exchange data using DPM and VSS
• Troubleshoot, monitor, and tune Exchange Server using the latest tools

Download 1/3>>

Download 2/3>>

Download 3/3>>

Fix: Launch Exchange Management Console, goto Recipient Configuration/Mail Contact container, open up contact you're having the issue with, on the 'general' tab change the 'Use MAPI rich text format' drop-down to 'Never' and test.

This install is on a Windows 2003 x64 server with Service Pack 2. I am installing Exchange 2007 SP1.

• Installed .Net Framework 2.0 SP1
• Since this will also be a CAS server, I need IIS on this box. Install IIS with the default options checked.
• Configured my EqualLogic SAN with LUN6 at 150GB - it is thin-provisioned at 25GB so only a small amount of space is currently used. This LUN will be used for our E:, F:, and G: drives at 50GB each. These are each for the Exchange databases.
• Configured my EqualLogic SAN with LUN7 at 32GB - it is thin-provisioned at 16GB. This LUN will be used for our H:, I:, and J: drives. These are for the Exchange Logs for each storage group.
• Based on the Exchange Calculator (Excel) I used yesterday, I increased the RAM on the virtual server from 3 GB to 8 GB.
• Installed PowerShell 1.0 for x64
• After a restart, I issued the Exchange setup command which "prepares legacy permissions"
  • setup /pl

Ran setup.com for Exchange with no parameters - same as using the Autorun from the CD. Steps 1 through 3 were "greyed out" since they had already been performed. I choose Step 4 "Install Microsoft Exchange Server 2007 SP1"

• Accepted the terms of the EULA
• Selected these roles to install on this server (see image)

Installed roles

• It tells me the disk space required is 1200MB
• Prompt for "Mail Flow Settings": I selected the only Exchange 2003 server that we have.
• At the first try for the install, the installer told me I needed to perform an update before installing the Hub Transport role.  I installed the update at    http://go.microsoft.com/fwlink/?LinkID=92858
• Actually, I was a bit surprised that more updates were not needed. Granted, this server has SP2 installed, but I have not done a full update of MS patches yet.
• On the second try, the install worked fine. The two longest items, the Hub Transport Role and the Mailbox role, took 5.5 minutes and 4.5 minutes respectively.
• After running the ExBPA tool, I went to our Exchange 2003 server and made a change to the regsitry. I encountered the ExBPA warning that the 'SuppressStateChanges' configuration parameter should be set to '1' on the Exchange 2003 mail server. I did that and left the reboot of that server for the weekend. Do a Google search for 'SuppressStateChanges' and [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RESvc\Parameters] and you will find references to this.
• Installed all of the Windows 2003 Microsoft patches that are available as of today.

1. Configure SAN for the drives that will house the 3 storage groups and appropriate log files. Did I mention that we currently have 1 storage group in Exchange 2003 which is less than 16 GB? We plan to extend this to 3 storage groups with 1 database each.
2. Install Windows 2003 Enterprise x64 with SP2.
3. Apply Schema changes for Exchange 2007 (from Exchange install CD).
4. Install PowerShell and other Exchange 2007 prerequisites.
5. Install Exchange 2007 on MAILPROD1. Install "Update Rollup 3 for Exchange Server 2007 SP1".
6. Install all Windows 2003 updates from Microsoft.
7. Setup security device for email.
8. Register for a "Unified Communications" site certificate with names MAILPROD1, etc at http://www.geocerts.com/products/unified/
9. Storage groups
   1. First storage Group/Database Alpha will reside on drive E: with logs on drive H:
   2. Second storage Group/Database Beta will reside on drive F: with logs on drive I:
   3. Third storage Group/Database Gamma will reside on drive G: with logs on drive J:
   4. Public store will reside on drive E: with logs on drive H:
10. Setup Mailboxes for 50% of people listed in #11 on a laptop with Outlook 2002 installed. Other 50% on a desktop with Outlook 2003 installed. Note: Some should be setup for using cached mail and some not cached (2003).
11. Morning: I will "watch the lights on the SAN" as the first group of users is moved (check to see if all SAN disks are used, even though 1 database is being used right now). Users should include Steve, Kady, Jerry, Aaron, Derek, Donna, Joyce, Rob, Wendi, Sarah, Connie, Jennifer, John, Keith, Tammy, and Christy. Please time these transfers.
12. Afternoon: Test incoming and outgoing mail for users in #11. Did mail clients automatically shift servers?
13. Test calendar and scheduling of appointments for users in #11. Are all appointments showing correctly? Can a user see the free/busy schedule for all users on 2003/2007 servers?
14. How fast are inboxes being transferred? What is the KB rate?
15. Once I am satisfied with the results so far, give MRS users at least 30-hour notice that their mailboxes will be moved. They will need to use maila.unionmarketing.com/exchange if checking mail from home (until further notice). Laptops would only be affected differently in that they would need to connect to the VPN at the new data center.
16. Test "my" Treo on maila.unionmarketing.com
17. Move mailboxes of 4 s-group users to test the effect of the move on Blackjack II users.
18. Poll the 4 s-group users to see if the functionality of the Blackjack II has changed now that it is speaking to Exchange 2007 at the backend.
19. Setup BackupExec for Exchange on MAILPROD1. Backup Exec will only be used until Sept. 1. September 1 will likely contain the backup on tape before fully utilizing the SAN data recovery features.
20. Move remaining 130 users. [Wait at least 1 week before part B of step 23.]
21. Move Public store.
22. Perform procedures to remove an Exchange 2003 server from the domain (lengthy procedure).
23. Remove Exchange 2003 from the 2003 server. Power down the former Exchange 2003 server for 24 hours to see what problems arise.
24. Configure MAILPROD1 and Fax server to properly work together (lengthy).
25. Use the EqualLogic HIT kit: install the Exchange-specific program. Configure the SAN to create a replica and replicate the replica of each database at an interval of every 15 or every 20 minutes.
26. Remove Backup Exec from MAILPROD1 once #25 is working properly.

Zimbra Collaboration Suite (ZCS) 5.0 is a truly modern, innovative messaging and collaboration application. Zimbra is the leading open source solution for enterprise, service provider, education, and government environments; offering administrators and their end-users unmatched benefits. It's no wonder Zimbra is a popular choice for today's growing Mac and Linux email server base. It has been recently bought by Yahoo!

ZCS Server supports various clients:
- Advanced Web Client (AJAX)
- Zimbra Desktop
- Standard Web Client (HTML)
- Outlook 2003, 2007 (MAPI)
- Apple Desktop
- iPhone
- Blackberry
- Standard Phones (J2ME)
- Symbian, Palm

The unique open source Zimlet technology makes it easy to include custom 'mash-ups' in the ZCS web client. Zimlets are a mechanism for integrating the Zimbra Collaboration Suite (ZCS) with third party information systems and content as well as creating "mash-up" user interfaces within the Zimbra suite itself. Zimlets save end users time by condensing common tasks, which typically force them to open multiple applications, into simple contextual ones within ZCS-- such mashing up calendar information to appear within the email.
Zimbra has both Network Edition and an Open Source Edition. Comparisons between Zimbra CS editions can be found here.

Apparently Microsoft has given a competitive breakdown of Microsoft Exchange versus Zimbra, and candidly admits Zimbra's superiority in several areas. You can see the web page at the link given here:
Zimbra Collaboration Suite 4.0 vs. Exchange Server 2007
Its as partner only document, but I got some insider information from some posts on internet.

Microsoft lists several Zimbra strengths that sound much more compelling than its defense of Exchange 2007:

* The open-source-software components [used by Zimbra] are proven solutions by themselves, many with large existing user bases (MySQL, OpenLDAP, Apache, PHP, SpamAssassin).
* Its' class of service architecture allows for simple tiered access to services.
* Searching via their Web interface is fast and robust (AJAX query builder).
* The Verity HTML converter allows for fast rendering of 200 documents to HTML.
* Zimlets, can provide a more interactive user experience compared to the Microsoft equivalent of SmartTags.
* The Documents solution provides integrated wiki-document sharing with powerful embedded document features.
* The AJAX interface is pleasing and has a "wow" factor due to speed and Zimlets. Additionally, its' interface is identical across Internet Explorer/Firefox/Opera.

How I did it ?

The host i am trying out is : sherweb.com

Well what i did was used my domain i have with startlogic.com ... This way end up costing me an extra $4 a month because although i have the domain with them inorder to for email servers to work(sherWeb and others) u need to tweak setting on the DNS (changing MX record and A record) .. my host is robbing me 4 bucks a month. to keep the settings i need.. So if you are going the path of having a domain just for email and not for actual hosting a website i recommend http://www.easydns.com their "Domain Name + DNS" service bundle .. so you get a domain name with them and also all tools you need to get it working with an exchange server.. its like 35 a year.

Pricing

I am paying Domain Name $8yr + $48yr(dns settings)+ SherWeb Yealy price wish is like $108 a year

I am now going to test how effective the email service is, so I will post my email address here to attract robots to fetch this address, and send spams to the address.

Kane@groje.com

More:
wiki - MS Exchange Server
MS Exchange Server 2007
Planning for Anti-Spam and Antivirus Features

OT:
I am looking for some virus database, because I would like to implement the basic anti-virus method -- pattern matching. Should you know any virus database that is useful, please let me know.

There are some little improvements, including better layout for single line display, and no longer telling you there is more to download when the entire message was pre-loaded. It also fixes some bugs the the sorting of inboxes.

Not much progress on IDLE I am afraid, but this has been due to pressure in other directions, and irritating problems resulting from Apple making changes to .mac at the weekend.

Here is the 'official' list of fixes etc in 50

• performance improvements to message decoder
• fixed problem working with Microsoft Exchange Server 2007
• fixed problem with multi-select delete not working for an even number of selected messages
• fixed problem with IDLE not appearing to be informed of new messages - caused by not selecting mailbox before initiating IDLE
• fixed bugs in sorting messages in Message List
• fixed incorrect title on network settings panel
• no longer any need to restart after changing user name and password details
• improved session reliability for send and receive
• fixed bug in passing user details to SMTP module
• changed to show messages as unloaded, preloaded and fully loaded
• fixed problem where small messages are shown as part loaded
• fixed protocol break caused by loosing a server response line

Also, it would appear that battery consumption is not as bad as it was!

Since early this year I have migrated from Exchange 2003 to Exchange 2007, replaced my existing anti-virus software with ForeFront Client Security, rolled out XP SP3 and Office 2007 SP1, installed a pilot program of Vista SP1, upgraded our AD from 2003 to 2008 and starting next week I am heading a full blown MOSS 2007 implementation. It makes me tired just typing it all.

Oh and I almost forgot that stuck in the middle of it all was TechEd 2008 in Orlando where I worked the System Center Essentials booth for Microsoft as well as doing a couple of talks and moderating a Birds of a Feather session for SMBs dealing with Microsoft and the overwhelming number of solutions they offer us. 

It's been crazy and incredibly busy, but what a great set of solutions we are getting set up for the future!

I will be blogging all about the transitions that we have been going through as well as some of the gotchas I discovered along the way.

Stay tuned...

To The Post

To The Blog

-

-

-

-

http://www.schoonmultimedia.com/tech

I restored sanity using an Ubuntu server as follows. Needless to say, this requires that (a) the exchange server allows IMAP access and (b) the SMTP server for your machine will relay mail outside of your domain.

Updated: to do it all via procmailrc, without .forward
Updated: to poll folders other than Inbox

1. Install fetchmail and edit /etc/fetchmailrc:

sudo apt-get install fetchmail
sudo nano -w /etc/fetchmailrc

2. Make /etc/fetchmailrc look something like this:

set daemon 300
poll your.exchange.server protocol imap username "user" password "pass" smtpname "user@gmail.com" ssl

replacing your.exchange.server, user (exchange), pass (exchange) and user@gmail.com (your GMail) as appropriate.

To poll folders other than "Inbox", you can append the "poll" line in fetchmailrc with the term "folder" and a comma-separated list of names, e.g.:

poll your.exchange.server protocol imap username "user" password "pass" smtpname "user@gmail.com" ssl folder "Junk E-mail","Inbox"

Just in case a real mail slipped into your Exchange junk.

Then:

sudo chmod 600 /etc/fetchmailrc

Finally:

sudo /etc/init.d/fetchmail start

and "tail -f /var/log/mail.log" to make sure that all is OK. You can also try "fetchmail -v" first and look for output similar to that given by this handy guide.

La solucion la puedes encontrar aqui:

http://support.microsoft.com/kb/911829

Y si quieres saber la razón del problema miratela aqui:

http://msexchangeteam.com/archive/2006/11/16/431521.aspx

Antes de instalarte este parche asegurate de tener Exchange Server 2003 con Service Pack 2 instalado. Si no lo tienes te lo puedes bajar desde:

http://www.microsoft.com/downloads/details.aspx?familyid=535BEF85-3096-45F8-AA43-60F1F58B3C40&displaylang=en

• EXC14 Message Hygiene in Exchange 2007 and the Anti-Spam Migration Tool
• EXC13 Transport Rules with Exchange 2007 Outlook 2007
• EXC12 Customizing Outlook Web Access in Exchange 2007

The last one on customizing OWA, I'd really like to have back. It was by far the worst one of the three.  I messed it up and I still have some supplemental work to do on it. It was a learning experience and I will be a better speaker as a result.