Bug 111784 - e-mail user agent setup isn't quite right for imaps
Summary: e-mail user agent setup isn't quite right for imaps
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rhel-rg
Version: 3.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Andrius Benokraitis
QA Contact: John Ha
Depends On:
TreeView+ depends on / blocked
Reported: 2003-12-10 03:05 UTC by Pierre F. Maldague
Modified: 2015-07-14 04:24 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2003-12-12 21:47:42 UTC

Attachments (Terms of Use)

Description Pierre F. Maldague 2003-12-10 03:05:09 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922

Description of problem:
In section (securing email client communications), I see
2 mistakes.

First, to create a self-signed certificate, you instruct the
reader to cd to /usr/share/ssl/certs/ and run make imapd.pem.
This is good, except that rpm installs an imapd.pem file by
default, which must be removed first (otherwise 'make' reports
that all is up to date.)

Second, once the certificate has been created you instruct the
reader to run /sbin/services with the imaps option. But this does
not work, because there is no imaps script in /etc/init.d. The
correct option is to edit the imaps file in /etc/xinetd.d/imaps
file so that the value of the 'disable' field is set to no instead
of yes.

Even though I am reporting a bug, finding the workaround wasn't bad
and my mail server has been up and running in record time. Keep up
the good work and keep fixing all these little details!!

Version-Release number of selected component (if applicable):
rhel-rg(EN)-3-HTML-RHI (2003-07-25T17:13)

How reproducible:

Steps to Reproduce:
1.type 'make imapd.pem' in /usr/share/ssl/certs/ and watch it reply
that imapd.pem is up to date.
2. type '/sbin/services imaps' and watch it respond that imaps is an
unknown service.

Actual Results:  1. 'imapd.pem' is up to date
2. imaps: unknown service

Expected Results:  1. "How are you today?" (Just kidding -- I expected
a few questions like name, company, domain name, address etc.)
2. command prompt with no errors

Additional info:

Note You need to log in before you can comment on or make changes to this bug.