Bug 54027 - sendmail does not use system resolver
Summary: sendmail does not use system resolver
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sendmail
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Florian La Roche
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-09-25 20:42 UTC by Matthew Galgoci
Modified: 2007-04-18 16:37 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2003-02-28 03:28:09 UTC


Attachments (Terms of Use)

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.


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