FW: Connection failed. errno: 111
No just IMAP. Not using SSL. Didn't compile SSL into mutt. Standard port
number is being used.
set spoolfile=imap://exchange1.slo-off.truelink.com/INBOX
set folder=imap://exchange1.slo-off.truelink.com/INBOX
mbox not set.
I haven't changed this configuration in months, and nothing has changed
in months on the Exchange Server. I'm not certain how Outlook is
connecting, but I haven't changed anything in either client, and mutt is
the only one that is not working now. It is just connecting to the
Exchange Server.
Yesterday we had a power outage. I was able to use mutt before that, but
after... No go.
Jason
-----Original Message-----
From: owner-mutt-users@xxxxxxxx [mailto:owner-mutt-users@xxxxxxxx] On
Behalf Of Kyle Wheeler
Sent: Tuesday, August 01, 2006 9:16 AM
To: mutt-users@xxxxxxxx
Subject: Re: Connection failed. errno: 111
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, August 1 at 08:58 AM, quoth Jason Helfman:
>I keep getting this, no matter what version of mutt I am using:
>
>Connection failed. errno: 111...
That's not much information...
>I am connecting via Imap.
.... oookay ....
First answer these questions: how does Outlook connect? Is it using
IMAP? Is it using IMAPS instead? Is it using an unusual port number?
Is it using SSL? Is it using TLS?
Then answer these questions: how have you told mutt to connect? What
is the value of $folder, $spoolfile, and $mbox? Have you compiled SSL
support into mutt?
Most likely, you aren't telling mutt to connect in the same way that
Outlook is.
~Kyle
- --
If Mr. Einstein doesn't like the natural laws of the universe, let him
go back to where he came from.
-- Robert Benchley (1889-1945)
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFEz34pBkIOoMqOI14RAoN9AJ0VkDNpEGVFMF+ecKmuksAqoOpR1wCePs6e
GrSCymn7tw2VJG/qU0bZFwg=
=5yyN
-----END PGP SIGNATURE-----