headers
Jason Helfman | 1 Aug 17:58

Connection failed. errno: 111

Help me. I have to use Outlook, now! Ugh!!!!

I keep getting this, no matter what version of mutt I am using:

Connection failed. errno: 111...

Could not connect to exchange1.slo-off.truelink.com (Connection
refused).

mutt_index_menu[623]: Got op 144

I was getting this before:

read_rfc822_header(): no date found, using received time from msg
separator

I am connecting via Imap.

Thanks,

Jason
Permalink | Reply | 1 comment |
headers
Kyle Wheeler | 1 Aug 18:15

Re: Connection failed. errno: 111


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)
Permalink | Reply | 0 comments |
headers
Kevin Rolfes | 1 Aug 18:38
Favicon

sendmail_wait and ssmtp


Hi, I recently discovered something about the use of "sendmail_wait" with
ssmtp and wanted to share that with the Mutt community.

My computer uses ssmtp as the MTA and forwards all my email to an external
relay. (snark mode on) I use DreamHost as the relay, which means that the 
external relay isn't always available. (snark mode off - they've had a lot 
of downtime lately)

I had sendmail_wait set to 10, probably from an earlier time when I used
sendmail instead of ssmtp. What I found was that after ten seconds, Mutt
would tell me it was sending in the background, but instead ssmtp would
silently putting the message into dead.letter - there was no background
attempt nor any message to the user indicating that the send failed. 
Looking at ssmtp's man page, there's no support for background delivery, 
so this is clearly a misconfiguration on my part. With sendmail_wait
set to 0 it behaves in a sane manner no matter if the external relay is 
up or down.

I'm thinking it would be nice to have a comment in the stock .muttrc
for the "sendmail_wait" variable, to the effect of: "if you are using 
a mail transport agent other than sendmail which does not support
background delivery (e.g. ssmtp, ...), you do not want to set this
variable to a value other than zero."

I'm currently using Mutt 1.4.2.1i under Cygwin. It is also entirely 
possible that this is Cygwin-specific behavior, but I no longer have 
access to a *nix box to double check this.

By the way, on the mailing lists page:
(Continue reading)

Permalink | Reply | 0 comments |
headers
cl | 1 Aug 19:09

Unwanted SSL certificate message

Using mutt at Gradwell.Net I get an "SSL Certificate check" whether I
like it or not, is there any way to turn this off?

--

-- 
Chris Green (chris <at> halon.org.uk)
Permalink | Reply | 2 comments |
headers
Jason Helfman | 1 Aug 19:52

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 <at> mutt.org [mailto:owner-mutt-users <at> mutt.org] On
Behalf Of Kyle Wheeler
Sent: Tuesday, August 01, 2006 9:16 AM
To: mutt-users <at> mutt.org
Subject: Re: Connection failed. errno: 111

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, August  1 at 08:58 AM, quoth Jason Helfman:
(Continue reading)

Permalink | Reply | 2 comments |
headers
Rado S | 1 Aug 19:55
Picon
Favicon

Re: Unwanted SSL certificate message

=- cl <at> isbd.net wrote on Tue  1.Aug'06 at 18:09:48 +0100 -=

> Using mutt at Gradwell.Net I get an "SSL Certificate check" whether I
> like it or not, is there any way to turn this off?

Yes, Brendan helpfully added it to the wiki-faq.

--

-- 
© Rado S. -- You must provide YOUR effort for your goal!
Even if it seems insignificant, in fact EVERY effort counts
for a shared task, at least to show your deserving attitude.
Permalink | Reply | 1 comment |
headers
cl | 1 Aug 20:14

Re: Unwanted SSL certificate message

On Tue, Aug 01, 2006 at 07:55:01PM +0200, Rado S wrote:
> =- cl <at> isbd.net wrote on Tue  1.Aug'06 at 18:09:48 +0100 -=
> 
> > Using mutt at Gradwell.Net I get an "SSL Certificate check" whether I
> > like it or not, is there any way to turn this off?
> 
> Yes, Brendan helpfully added it to the wiki-faq.
> 
Brilliant, thank you, exactly what I needed was there.

I must admit I'd forgotten there's a mutt Wiki now, I must remember.

--

-- 
Chris Green (chris <at> halon.org.uk)
Permalink | Reply | 0 comments |
headers
Eric Smith | 1 Aug 21:21
Favicon

Mutt 1.5.12 and attachment functionality

Hi

I am using Mutt 1.5.12 and cannot seem to get %X to work in the
index_format nor attachment patch commands like
attach-exclude  message/external-body
to work. It jsut reports zero.

Especially importatn for me is to show the number of attachments
in a message on the index_format.

Any ideas?

$ mutt -v
Mutt 1.5.12 (2006-07-14)

System: Linux 2.6.9 (i686) [using ncurses 5.5] [using libidn 0.5.18 (compiled with 0.5.18)]
Compile options:
-DOMAIN
-DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  
+USE_FCNTL  -USE_FLOCK   -USE_INODESORT   
+USE_POP  +USE_IMAP  -USE_GSS  -USE_SSL_OPENSSL  -USE_SSL_GNUTLS  -USE_SASL  +HAVE_GETADDRINFO  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  -CRYPT_BACKEND_GPGME  
-BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  +LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET  +HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  -USE_HCACHE  
ISPELL="/usr/bin/ispell"
(Continue reading)

Permalink | Reply | 1 comment |
headers
Kyle Wheeler | 1 Aug 21:51

Re: FW: Connection failed. errno: 111


On Tuesday, August  1 at 10:52 AM, quoth Jason Helfman:
> 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.

HEH. Sounds like you found your problem. It's quite possible that your 
power outage corrupted many things on your computer, including mutt. 
I'd say, at the very least, reinstall mutt and all the libraries it 
depends on.

If you're VERY CERTAIN that it was not the power outage and that 
neither your mutt nor anything else on your computer was, in fact, 
damaged by the power outage, then you should compile mutt with 
debugging enabled, and generate a trace file. Then you'll be able to 
see what mutt sent to the IMAP server, what it received back, and what 
it thought of it.

~Kyle
--

-- 
It is the test of a good religion whether you can joke about it.
                                                   -- G. K. Chesterton
Permalink | Reply | 0 comments |
headers
Charles Killian | 1 Aug 22:07

Re: FW: Connection failed. errno: 111

I think before you go recompiling Mutt and such, you might just try a
simple test:

Start->Run:
telnet exchange1.slo-off.truelink.com 143

Assuming it is running imap on the default port, that telnet session
should connect.  From a linux box connecting to another imap server, I
get this response to my telnet:

Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
* OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS LOGINDISABLED] localhost.localdomain IMAP4rev1
2003.339 at Tue, 1 Aug 2006 13:05:35 -0700 (PDT)

Yours may vary somewhat.  If you cannot connect to the server, then your
problem is that the server is not listening on the imap port.  My guess
is that your outlook is using the exchange protocol to connect, and
could easily still work even if the imap port is closed.  

Assuming that's your problem, you'll have to contact your network
support to fix the exchange server.

-C

On Tue, Aug 01, 2006 at 10:52:46AM -0700, Jason Helfman wrote:
> No just IMAP. Not using SSL. Didn't compile SSL into mutt. Standard port
> number is being used.
>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane