Bug 54027

Summary:	sendmail does not use system resolver
Product:	[Retired] Red Hat Linux	Reporter:	Matthew Galgoci <mgalgoci>
Component:	sendmail	Assignee:	Florian La Roche <laroche>
Status:	CLOSED NOTABUG	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1	CC:	sulli
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-02-28 03:28:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Galgoci 2001-09-25 20:42:24 UTC

Description of Problem:

Sendmail does not appear to use the system resolver libraries, and the 
way that sendmail does name resolution on its own has issues with the 
way that we change resolv.conf files.

It appears that when sendmail first starts, that it opens the /etc/resolv.conf
file and retains a reference to this file by inode. If the /etc/resolv.conf
file is moved to /etc/resolv.conf.bak and a new /etc/resolv.conf file is 
generated, sendmail will still reference the file that is now known as 
/etc/resolv.conf.bak

This presents problems with our network initscripts that can be configured
to specify a set of new name servers.

This problem is painfully apparent if you happen to being up a cipe interface
that specifies internal name servers in the context of a vpn that uses
rfc1918 addresses to resolve the rfc1918 addresses.

Immagine trying to use fetchmail on a laptop in this situation.

This problem first surfaced with the release of Red Hat Linux 7.0, is
present in 7.1 as well as the current beta.

Please fix sendmail.

Comment 1 Matthew Galgoci 2003-02-28 03:28:09 UTC

This is a glibc-ism, not an issue with sendmail.