Bug 99227 - Unable to allow additional ports
Summary: Unable to allow additional ports
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-securitylevel
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-07-16 08:43 UTC by John Horne
Modified: 2007-04-18 16:55 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-07-29 13:37:06 UTC
Embargoed:


Attachments (Terms of Use)

Description John Horne 2003-07-16 08:43:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
Installed RHL9 with 'high' firewall setting. Then ran Ximian's evolution and
tried to get email using imap from local server. It failed. Ran
redhat-config-securitylevel but there is no option add (customize) to allow
additional ports -I would like to add the IMAP port. Same will probably occur
for POP email.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install RHL9. Specify a 'high' or 'medium' firewall setting.
2. Startup evolution and try to receive email using IMAP (or POP). 

Actual Results:  The firewall (iptables) prevents receiving imap/POP mail.

Expected Results:  Okay, so the firewall prevents it, but I should be able to
reconfigure it using redhat-config-securitylevel to allow additional ports -
just as occurs during the installation process.
Not tested yet but I assume if I specify the IMAP port during installation, it
will work. I'll test today.

Additional info:
PS -  http://bugzilla.redhat.com defaults to redhat linux version 8 - surely it
should default to '9' by now?

Comment 1 John Horne 2003-07-29 10:14:35 UTC
I see this has been fixed in the 'Severn' beta version. Thanks.

Comment 2 Brent Fox 2003-07-29 13:37:06 UTC
Ok then.  Closing.


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