RE: ANNOUNCE - indimail-mta (qmail+ucsp-tcp+daemontools with all patches)

"Bill Olson" <[email protected]>
Newsgroups gmane.mail.qmail.general
Message-ID <[email protected]>
This is the command I was using:

 

openssl s_client -starttls smtp -crlf -connect 192.168.9.223:587

 

Bill Olson

 <mailto:[email protected]> [email protected]

Nelson and Wright, Inc.

Tel 207-929-8238

Fax 207-929-4278

 <http://www.nelsonandwright.com/> http://www.nelsonandwright.com

 

From: Manvendra Bhangui [mailto:[email protected]] 
Sent: Monday, April 11, 2016 11:04 AM
To: Bill Olson <[email protected]>
Cc: qmail <[email protected]>
Subject: Re: ANNOUNCE - indimail-mta (qmail+ucsp-tcp+daemontools with all patches)

 

On 11 April 2016 at 20:24, Bill Olson <[email protected] <mailto:[email protected]> > wrote:

My own qmail 2.0 install can be found here:

http://freebsdrocks.net/index.php/documents/17-qmail-2-0

 

My guide is basically an updated version of the old qmailrocks from 2001 and I have been able to keep it updated. I basically wrote the guide myself after testing the guide hundreds of times. I have always used the setup with secure SSL and never had a use for TLS before until someone started bugging me about it. Apple is the reason I need TLS to work.

 

After over 20+ failed installations with TLS I am starting to think it has something to do with FreeBSD running on amd64. I would rather not move away from FreeBSD because I have so much experience with it. 

 

IMHO This cannot be an issue with FreeBSD
 

 

See attached working tls and non-working tls file. The working tls is on i386 and the non-working tls is on amd64. On AMD64 when I capture the log file this is what I see:

 

016-04-11 10:51:22.939190500 33876 > 220 qmailtest10.nwi.local ESMTP

snip ... 

016-04-11 10:51:22.940528500 33876 < STARTTLS

016-04-11 10:51:22.941518500 33876 > 220 ready for tls

 

It looks like it wants to accept TLS but because of the encryption … I can’t read it. 

 

Any thoughts on this?


You probably need to do something like this instead of using telnet

openssl s_client -starttls smtp -crlf -connect 127.0.0.1:25 <http://127.0.0.1:25>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.