Re: IMAP server - upgrading to SuSE 9.2

From: David Wright (david_c_wright_at_hotmail.com)
Date: 01/23/05 

Date: Sun, 23 Jan 2005 14:24:02 +0000

James Knott wrote:

> David Wright wrote:
>
>> James Knott wrote:
>>
>>> I'm planning on upgrading my desktop system to SuSE 9.2 shortly. On
>>> this
>>> system, I also run an IMAP server (IMAP4, not Courier or Cyrus). I was
>>> wondering what the preferred IMAP server is, and what issues I'll run
>>> into, while switching from IMAP4.
>>>
>>> tnx jk
>>
>> IMAP4 and Cyrus are both on the DVD (haven't looked to see if Courier is
>> also there), so there shouldn't be any change in that respect. The only
>> issue you should possibly face is if the version of IMAP4 has changed and
>> the syntax in the config files has changed or some options have been
>> superceded...
>
> One other concern, which I forgot to mention, is that I use fetchmail.
> Does it work with Cyrus or Courier?

I beleive so, from reading the how-to. Problem is, as I was setting up IMAP
on my network, I picked up a customer using Exchange Server 2003, so I
switched to ES for the time being so that I can test things out here before
making them live on his system (I have a Windows SBS 2003 license as part
of the Action Pack).

I am not overly impressed with it, especially from the ease of use front.

For example, I wanted to open up the IMAP service so I could access it from
my Linux machines (Evolution's plug-in doesn't support Exchange Server 2003
by the look of it :-( ); I looked in the exchange server snap-in and there
was an option to launch the IMAP service.

I tried to start the service, but it kept failing. Trawling the MS Knowledge
Base, it turns out to start the IMAP server in Exchange, you first have to
start the IMAP server (not the Exchange IMAP server, but the IMAP server
which Exchange installs), once that IMAP server is running, you can then
start the Exchange IMAP server! Erm, why do I need to start 2 IMAP
services? And why when I try to start the wrong one first doesn't it tell
me that the IMAP service needs to be started before I can start the IMAP
service? Or even better (and I would have thought logical) to warn you when
you start the IMAP service that the "other" IMAP service isn't running and
offer to start it for you... I thought Windows was supposed to be user
friendly and have a lower TCO, sending users round in circles isn't very
friendly or efficient.

Hopefully I'll switch back to Open Exchange or IMAP in the near future.

Dave

Relevant Pages

  • Re: imap service does not start automatically on reboot
    ... That's the thing, there's nothing in there about imap, or any other errors ... about Windows 2003 or Exchange 2003... ... >> I seem to have a problem in that my imap service doesn't start ... >> automatically on rebooting the windows 2003 server. ...
    (microsoft.public.exchange2000.admin)
  • Re: Save Attachments - No "If Attachment Exists" in recent Entourage Rule engine?
    ... the Attachment criterion _is_ there for Exchange ... Just not IMAP. ... message to an IMAP server by AppleScript since the resulting message with ID ... Entourage FAQ Page: ...
    (microsoft.public.mac.office.entourage)
  • Re: TREO (IMAP)
    ... requirement is connecting to an IMAP server. ... so he'll know that IMAP is running on the exchange box? ... Your Exchange admin should know all about IMAP. ...
    (microsoft.public.exchange2000.general)
  • Re: Testin Exchange 2007 + IMAP
    ... I have small problem with Exchange 2007 ... Hub transport is OK ... IMAP Service is enabled ... IMAP is good to go ...
    (microsoft.public.exchange.setup)
  • Setting up (secure) IMAP
    ... trying to setup IMAP for users that have mobile SPV M2000's for ... I've enabled the IMAP service in Exchange. ...
    (microsoft.public.windows.server.sbs)