Bug 18727

Summary: imapd/pop*d have internal SSL support but still use/depend on stunnel
Product: [Retired] Red Hat Linux Reporter: Christian Hechelmann <drdisk>
Component: imapAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: Dale Lovelace <dale>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: ametzler, dr
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-11-27 09:53:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Christian Hechelmann 2000-10-09 17:05:33 UTC
In the imap-4.7c2-12 package shipped with RH7.0 the imapd, ipop?d servers
are built with internal SSL support, i.e. when run from port imaps/pop-?s
they will detect and use SSL by themselves.

In the specfile however imapd and ipo?d are set to start via stunnel.
This is both redundant and unfortunate, since when run via stunnel the
daemons won't get the true client ip adress from which the connection
originated. Instead they get (localhost). This completely breaks
DRAC (dynamic relay authorization control) AKA POP-before-SMTP.

Comment 1 Nalin Dahyabhai 2000-10-10 16:50:37 UTC
The native SSL support was added some time after the stunnel setup was added to
the package.  We'll have to change this.  I'll mark this one as resolved when we
get a package built with the changes.

Comment 2 Andreas Metzler 2000-11-27 09:53:22 UTC
You can mark this resolved, v2000 has been uploaded. (even for RH6.x).

Comment 3 Arenas Belon, Carlo Marcelo 2000-12-19 16:54:30 UTC
fixed on errata :


* Tue Oct 10 2000 Nalin Dahyabahai <nalin@redhat.com>
- switch to internal SSL support instead of using stunnel (#18727)