Re: How to do these ??

Leonid Mamtchenkov wrote:

>Dear bindal,
>
>b> 2) Porting of Public Folders from Exchange Server to Linux ? is there a 
>b> way ?
>
>I believe you can use IMAP folders sharing to implement it.
>
Yes.  The implementation of shared folders is quite different from IMAP 
server to IMAP server, however.  You'll need to test all the IMAP 
clients you're interested in (start with Mozilla) to make sure they 
"notice" the shared folders.  If they do so automatically, that may save 
you significant client-side configuration.

>
>b> 3) Scheduling/ Calendering on Linux Sendmail
>
>This is a problem these days, if you ask me.  
>
Agreed.  It is a significant reason why I can't tell the company I just 
joined that "IMAP will solve all these problems".

>There are several
>alternatives, which are still in development.  KDE project (
>http://www.kde.org ) has korganizer ( http://korganizer.kde.org ), which is, 
>IMHO, the most developed and feature-full one.  It does not have any server 
>back-end though.  
>
And it is (presumably) thus single-user.  Group scheduling is probably a 
bigger blocking point.

>Ximian Evolution ...Calendar plug-in for Mozilla browser 
>
There is another option high on my list for testing: Bynari's server 
available at http://www.bynari.net.  It supposedly offers full 
calendaring support.  I may have a chance to try it in the next couple 
of weeks.

>b> 4) Porting of mail boxes fom Exchange server to Linux sendmail server.
>
>There are several ways to go about it.  One, from the top of my head is
>to use fethcmail :)
>
Fetchmail is wonderful.  It is even more wonderful after you know that 
the fetchmailconf tool will write the ~/.fetchmailrc that will control 
fetchmail for you in the future.

In outline, you'd leave your exchange box serving clients.  After moving 
all your messages into your INBOX, you pull them out with fetchmail. 
Fetchmail then delivers the messages to your new email server, where 
they end up in your new IMAP inbox...  (The learned are welcome to 
improve on this description.)

Alan
--
Alan Peery
[email protected]