Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 13583 - Always tries relay test
Always tries relay test
Product: Red Hat Linux
Classification: Retired
Component: gnome-lokkit (Show other bugs)
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Alan Cox
: Security
Depends On:
  Show dependency treegraph
Reported: 2000-07-07 17:10 EDT by Frank Sweetser
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-08-03 19:14:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Frank Sweetser 2000-07-07 17:10:19 EDT
Under the paranoid setting at least, gnome-lokkit always attempts to
perform the open relay test through abuse.org  This will fail under a
number of circumstances, ranging from not being dialed up to an upstream
router/firewall blocking port 25.  While the rules seem to be left in a
working state, the program should at least handle the relay test failing or
being cancelled gracefully.
Comment 1 Alan Cox 2000-07-12 08:29:55 EDT
The rules are done before the test, so you can gracefully quit. I think that bit
is a UI
issue more than a bug as such. The trying relay test when it shouldnt case I can
duplicate and will go and fix.  The relay test times out if it cannot connect to
abuse.org. mail-abuse itself should eventually timeout if the connect back
If not then I suspect its their bug but I need to code around it
Comment 2 Alan Cox 2000-08-03 19:14:49 EDT
Gnome Lokkit 0.41 released to fix this
Comment 3 Frank Sweetser 2000-08-11 16:57:07 EDT
Still fails (as expected), but does allow you to not performe the relaying at
all, and fails and quits gracefully and quickly if it can't resolve.

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