Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 39762 - courier imap starttls fails to work, but normal sslv3 will work on the ssl imap port
Summary: courier imap starttls fails to work, but normal sslv3 will work on the ssl im...
Status: RESOLVED DUPLICATE of bug 39653
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-29 07:09 UTC by aeonflux
Modified: 2005-07-17 13:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description aeonflux 2004-01-29 07:09:34 UTC
courier imap, starttls will fail to start on the normal 143 port.  However ssl imap on the port 993, will function correctly.  it is just the tls1 service that will not function.  This is because the port choices to install couriertcpd and use it, instead of couriertls regardless of whether or not it's compiled with SSL.  The problem DOES not exist when compiled from source, also the scripts used to start imap (ie gentoo-imap.rc) are hardcoded to use couriertcpd rather then couriertls like the scripts created by the source's make file.

Reproducible: Always
Steps to Reproduce:
1.compile port
2. enable starttls
3. telnet to localhost 143 and realize starttls is not available

Actual Results:  
the gentoo-imapd.rc script runs couriertcpd rather then couriertls regardless of
whether starttls has been abled or not.  This is perhaps because the port coder
wasn't familar with the courier imap software.

Expected Results:  
the gentoo-imapd.rc script should have run couriertls, if starttls was enabled.
 The port should have also installed the binary for couriertls

The port should be upgraded to courier imap 2.2.1 which is the latest anyways.
Comment 1 SpanKY gentoo-dev 2004-01-29 15:23:31 UTC

*** This bug has been marked as a duplicate of 39653 ***