General discussion of the Mew MIME mail reader for Emacs/XEmacs

Harri Kiiskinen | 13 Feb 2012 12:08

[mew-int 3035] Exchange 2010 problems

Hi,

my organization just moved to Microsoft Exchange 2010, but I'd still
like to continue using Mew. To begin with, the IMAP is turned on on the
server, as Evolution manages to contact and communicate well.

Also mew manages to _connect_ to the server using mewstunnel and
stunnel4, but does not _communicate_.

I tested the server by using openssl:

openssl s_client -connect mail.server.my:993

the connection is set up finely but the commands elicit no response.
However, when using

openssl s_client -connect mail.utu.fi:993 -crlf

to connect to the server, everything works ok.

Now, seeing that 'mew-imap-process-send-string' ends each string sent to
the server with 'mew-cs-eol' which is hard-coded to "\n", I suspect that
the problem lies here. I'm trying to test it further, but setting
'mew-cs-eol' to "\r\n" in .emacs does not seem to fully help. The
communications seems to end ok, but for example the "update folders" 
C-uZ does not actually retrieve anything.

Any suggestions? 

I'm currently running Mew 6.3 from Debian Stable, but if there is a

(Continue reading)

headers

Harri Kiiskinen | 13 Feb 2012 13:00

[mew-int 3036] Re: Exchange 2010 problems

FOrget this mail. I have no idea what I managed to do, but suddenly
the communication began to work as it should. Yes, I kept restarting
Emacs all the time, but somehow I probably managed to find the right
setting. Weird.

All the best, and sorry for the bother,

Harri K.

From: Harri Kiiskinen <harri.kiiskinen <at> utu.fi>
Subject: [mew-int 3035] Exchange 2010 problems
Date: Mon, 13 Feb 2012 13:08:36 +0200

> Hi,
> 
> my organization just moved to Microsoft Exchange 2010, but I'd still
> like to continue using Mew. To begin with, the IMAP is turned on on the
> server, as Evolution manages to contact and communicate well.
> 
> Also mew manages to _connect_ to the server using mewstunnel and
> stunnel4, but does not _communicate_.
> 
> I tested the server by using openssl:
> 
> openssl s_client -connect mail.server.my:993
> 
> the connection is set up finely but the commands elicit no response.
> However, when using
> 
> openssl s_client -connect mail.utu.fi:993 -crlf

(Continue reading)

headers

Harald Hanche-Olsen | 13 Feb 2012 15:06

[mew-int 3037] Re: Exchange 2010 problems

[Harri Kiiskinen <harri.kiiskinen <at> utu.fi> (2012-02-13 12:00:07 UTC)]

> FOrget this mail. I have no idea what I managed to do, but suddenly
> the communication began to work as it should. Yes, I kept restarting
> Emacs all the time, but somehow I probably managed to find the right
> setting. Weird.

Would you mind sending us the relevant parts of your working setup
anyhow? I am interested because of an imminent threat of being
migrated to an Exchange server in the not too distant future,
something I don't look forward to.

- Harald

headers

Kazu Yamamoto | 23 Feb 2012 03:11

[mew-int 3040] Re: Exchange 2010 problems

Hello,

> Also mew manages to _connect_ to the server using mewstunnel and
> stunnel4, but does not _communicate_.

Mew supports stunnel only. If your stunnel is linked to libwrap,
please re-install stunnel without libwrap.

--Kazu