Bug 204806 - /etc/hosts ignored for resolving remote hosts for delivery
Summary: /etc/hosts ignored for resolving remote hosts for delivery
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: postfix
Version: 4.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Thomas Woerner
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-31 17:42 UTC by Charles Gillet
Modified: 2007-11-17 01:14 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-25 16:03:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Charles Gillet 2006-08-31 17:42:56 UTC 
Description of problem:

/etc/hosts ignored for resolving aliases (hosts: files dns in nsswitch) after
upgrade to U4

Version-Release number of selected component (if applicable):
 
postfix-2.2.10-1.RHEL4.2

How reproducible: consistently


Steps to Reproduce:
1. Use base postfix setup
2. put an alias that points to another mail gateway for delivery
/etc/aliases:
test:  test.net

3. if gateway is only in /etc/hosts (not in DNS) postfix will bounce message as
undeliverable because it can't resolve the name
  
Actual results:

bounces message as undeliverable - unable to resolve host address

Expected results:

should look in /etc/hosts, resolve from that file, and send the message to the
remote system

Additional info:
Comment 1 Charles Gillet 2006-09-21 21:43:10 UTC 
Do I need to open a case with Redhat support to get an acknowledgement here? 
This change of behavior broke things on a production server.
Comment 2 Thomas Woerner 2006-09-25 12:50:41 UTC 
Please set "smtp_host_loopup = native". THis should solve your problem.
Comment 3 Thomas Woerner 2006-09-25 12:51:27 UTC 
smtp_host_lookup = native
Comment 4 Charles Gillet 2006-09-25 15:53:05 UTC 
"smtp_host_lookup = native" does fix it.  Thanks!
Comment 5 Thomas Woerner 2006-09-25 16:03:55 UTC 
Closing as "NOT A BUG".
Note You need to log in before you can comment on or make changes to this bug.