atom feed29 messages in net.sourceforge.lists.courier-usersRe: [courier-users] courieresmtp - "N...
FromSent OnAttachments
Lindsay HaisleyDec 5, 2008 1:57 pm 
Sam VarshavchikDec 5, 2008 3:35 pm 
Lindsay HaisleyDec 5, 2008 8:18 pm 
Lindsay HaisleyDec 5, 2008 8:57 pm 
Sam VarshavchikDec 6, 2008 5:25 am 
Gordon MessmerDec 6, 2008 7:38 am 
Lindsay HaisleyDec 6, 2008 10:55 am 
Lindsay HaisleyDec 6, 2008 11:59 am 
Lindsay HaisleyDec 6, 2008 12:20 pm 
Gordon MessmerDec 6, 2008 12:23 pm 
Gordon MessmerDec 6, 2008 12:41 pm 
Lindsay HaisleyDec 6, 2008 12:41 pm 
Lindsay HaisleyDec 6, 2008 1:12 pm 
Gordon MessmerDec 6, 2008 1:31 pm 
Lindsay HaisleyDec 6, 2008 2:31 pm 
Sam VarshavchikDec 6, 2008 2:41 pm 
Sam VarshavchikDec 6, 2008 2:43 pm 
Lindsay HaisleyDec 6, 2008 2:58 pm 
Lindsay HaisleyDec 6, 2008 3:08 pm 
Sam VarshavchikDec 6, 2008 3:29 pm 
Lindsay HaisleyDec 6, 2008 3:47 pm 
Sam VarshavchikDec 6, 2008 5:27 pm 
Lindsay HaisleyDec 6, 2008 6:04 pm 
Sam VarshavchikDec 6, 2008 7:05 pm 
Lindsay HaisleyDec 6, 2008 10:00 pm 
Lindsay HaisleyDec 7, 2008 9:09 pm 
Sam VarshavchikDec 8, 2008 8:34 am 
Lindsay HaisleyDec 8, 2008 5:30 pm 
Sam VarshavchikDec 8, 2008 6:40 pm 
Subject:Re: [courier-users] courieresmtp - "No such file or directory"
From:Lindsay Haisley (fmou@fmp.com)
Date:Dec 6, 2008 12:20:01 pm
List:net.sourceforge.lists.courier-users

On Sat, 2008-12-06 at 07:38 -0800, Gordon Messmer wrote:

You shouldn't need to worry about the "various" files, just courierd. Check its COURIERTLS and TLS_TRUSTCERTS settings.

I've done a bit more testing and confirmed everything I noted last night.

* Setting ESMTP_USE_STARTTLS=0 in courierd makes the problem go away. I can set this to 1, elicit the error, set it to 0 and restart courier, run the queue on this msg, and the transaction goes through.

* All the remote SMTP servers where I get this local failure advertise TLS and STARTTLS, e.g.:

220 mail.slunsky.com . Sat, 6 Dec 2008 20:23:02 +0100 ehlo fmp.com 250-mail.slunsky.com Hello [216.110.12.105] 250-TURN 250-SIZE 250-ETRN 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-8bitmime 250-BINARYMIME 250-CHUNKING 250-VRFY 250-TLS 250-STARTTLS 250-X-EXPS GSSAPI NTLM LOGIN 250-X-EXPS=LOGIN 250-AUTH GSSAPI NTLM LOGIN 250-AUTH=LOGIN 250-X-LINK2STATE 250-XEXCH50 250 OK

* All the remote SMTP servers where I _do not_ get such a failure do not advertise TLS or STARTTLS in response to an ehlo.