Bug 891258

Summary:	Missing resolv.conf in chroot jail for postfix
Product:	[Fedora] Fedora	Reporter:	Gendre Sébastien <paradoxe>
Component:	postfix	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	17	CC:	jskarvad, mlichvar
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-01 01:54:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gendre Sébastien 2013-01-02 11:00:25 UTC

Description of problem:
When I activate the chroot of some daemons of postfix in the file /etc/postfix/master.cf, postfix can't resolve domain.

I discover this problem in my server when, in my /etc/postfix/main.cf file at "smtpd_sender_restrictions", I have added "reject_unknown_sender_domain" and enabled the chroot of smtp and smtpd in /etc/postfix/master.cf. Postfix reject all e-mails because he can't resolve all domain. 

I have added a copy of /etc/resolv.conf in /var/spool/postfix and now I can have a chrooted postfix.


Version-Release number of selected component (if applicable):
Version: 2.9.4
Revision: 3.fc17

How reproducible:
Install postfix and modify /etc/postfix/master.cf to enable chroot of smtp and smtpd.
  
Actual results:
Postfix can't resolve all domain.

Expected results:
Postfix must resolve all domain.

Comment 1 Fedora End Of Life 2013-07-03 23:19:17 UTC

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2013-08-01 01:55:01 UTC

Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.