I got that error to go away by switching from SSLv3 to SSLv2.
Gordan
On Tue, 30 Oct 2007, Vihan Pandey wrote:
> On 10/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> On Sep 7, 5:30 pm, [EMAIL PROTECTED] ("Vihan Pandey") wrote:
>>> Hello,
>>> I have courier-mta running on my GNU/Linux box with esmtp, pop,
>>> and imap running fine. I decided to statup smtps, imaps and pops as
>>> well but have run into problems.
>>>
>>> the smtps, imaps and pops daemons seem to be running properly :
>>>
>>> # netstat -an
>>>
>>> Active Internet connections (servers and established)
>>> Proto Recv-Q Send-Q Local Address Foreign Address
>>> State
>>> tcp 0 0 0.0.0.0:993 0.0.0.0:*
>>> LISTEN
>>> tcp 0 0 0.0.0.0:995 0.0.0.0:*
>>> LISTEN
>>> tcp 0 0 0.0.0.0:110 0.0.0.0:*
>>> LISTEN
>>> tcp 0 0 172.16.31.16:143 0.0.0.0:*
>>> LISTEN
>>> tcp 0 0 0.0.0.0:465 0.0.0.0:*
>>> LISTEN
>>>
>>> pop responds properly :
>>>
>>> # telnet 172.16.31.16 110
>>> Trying 172.16.31.16...
>>> Connected to foo.bar.com (172.16.31.16).
>>> Escape character is '^]'.
>>> +OK Hello there.
>>> USER foouser
>>> +OK Password required.
>>> PASS barpass
>>> +OK logged in.
>>> ^]
>>> telnet> c
>>> Connection closed.
>>>
>>> imap responds properly :
>>>
>>> # telnet 172.16.31.16 143
>>> Trying 172.16.31.16...
>>> Connected to foo.bar.com (172.16.31.16).
>>> Escape character is '^]'.
>>> * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
>>> THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION
>>> STARTTLS] Courier-IMAP ready. Copyright 1998-2005 Double Precision,
>>> Inc. See COPYING for distribution information.
>>> a001 LOGIN foouser barpass
>>> a001 OK LOGIN Ok.
>>> ^]
>>> telnet> c
>>> Connection closed.
>>>
>>> smtp responds properly :
>>>
>>> # telnet 172.16.31.16 25
>>> Trying 172.16.31.16...
>>> Connected to foo.bar.com (172.16.31.16).
>>> Escape character is '^]'.
>>> 220 foo ESMTP
>>> HELO foo.bar.com
>>> 250 foo Ok.
>>> mail from: <[EMAIL PROTECTED]>
>>> 250 Ok.
>>> rcpt to: <[EMAIL PROTECTED]>
>>> 250 Ok.
>>> data
>>> 354 Ok.
>>> testing
>>>
>>> foo bar
>>>
>>> testing
>>> .
>>> 250 Ok. 46E15C99.00006F4F
>>> ^]
>>> telnet> c
>>> Connection closed.
>>>
>>> drzook is a legitimate use and has a maildir and can send and receive
>>> mail properly.
>>>
>>> But this is what happens when i test smtps, imaps and pops :
>>>
>>> # openssl s_client -connect 172.16.31.16:465
>>> CONNECTED(00000003)
>>> write:errno=104
>>>
>>> # openssl s_client -connect 172.16.31.16:993
>>> CONNECTED(00000003)
>>> write:errno=104
>>>
>>> # openssl s_client -connect 172.16.31.16:995
>>> CONNECTED(00000003)
>>> write:errno=104
>>>
>>> i've noticed a few strange things :
>>>
>>> my /usr/lib/courier/etc/esmtpd.cnf refers to RANDFILE =
>>> /usr/lib/courier/share/esmtpd.rnd
>>> which exists
>>>
>>> -rw------- 1 root root 1.0K Sep 7 19:11 esmtpd.rnd
>>>
>>> and i use :
>>>
>>> # mkesmtpdcert
>>>
>>> to generate my certificate in /usr/lib/courier/share/esmtpd.pem which
>>> is owned by daemon(which is the user with which i start courier) and
>>> has permissions
>>>
>>> -rw------- 1 daemon root 2.2K Sep 7 19:11 esmtpd.pem
>>>
>>> however my /usr/lib/courier/etc/imapd.cnf refers to
>>> RANDFILE = /usr/lib/courier/share/imapd.rnd which did not exist by
>>> default so i changed that to RANDFILE =
>>> /usr/lib/courier/share/esmtpd.rnd in imapd.cnf
>>>
>>> also,
>>>
>>> my /usr/lib/courier/etc/pop3d.cnf refers to
>>> RANDFILE = /usr/lib/courier/share/pop3d.rnd which did not exist by
>>> default so i changed that to RANDFILE =
>>> /usr/lib/courier/share/esmtpd.rnd in pop3d.cnf as well
>>>
>>> then i did
>>>
>>> # mkimapdcert
>>>
>>> # mkpop3dcert
>>>
>>> and i got in /usr/lib/courier/share/ :
>>>
>>> -rw------- 1 daemon root 2.2K Sep 7 19:11 imapd.pem
>>>
>>> and
>>>
>>> -rw------- 1 daemon root 2.2K Sep 7 19:11 pop3d.pem
>>>
>>> So my question is how to get rid of the CONNECTED(00000003)
>>> write:errno=104 error and make smtps, pop3s, and imaps work.
>>>
>>> If any further information is required please let me know. Also, is
>>> there a command to list all of courier mta's variables at once - i can
>>> then post them.
>>>
>>> Thanks!!!
>>>
>>> Regards,
>>>
>>> - vihan
>>>
>>
>> Hi,
>> If you have time could you please let me know if you found a solution
>> to this problem as I have exactly the same problem.
>
> Well i was playing with Courier then and could not come to any
> definite solution to the problem. i think its time i re-visited it and
> will mail on the list if i figure out the solution. Also, its a
> convention on most lists(i do not know if it is so for this list as i
> am a newbie here) to post questions to the list and not to individual
> members. It makes sense to share what problems you discover and how
> you managed to solve them and let everyone benefit.
>
> Regards,
>
> - vihan
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> courier-users mailing list
> [email protected]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
