Bug 1089650

Summary: exim.service should not be enabled by default
Product: [Fedora] Fedora Reporter: Lars Seipel <ls>
Component: eximAssignee: David Woodhouse <dwmw2>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: dwmw2, fschwarz, jskarvad, luto, marcosfrm
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:23:40 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:
Bug Depends On: 1091506    
Bug Blocks: 1090684    

Description Lars Seipel 2014-04-21 10:52:02 UTC
As a persistent network service Exim should not be enabled by default[0]. Still, when installing the package on a fresh rawhide VM it is running after reboot.

This is with exim-4.82-1.fc21.x86_64 but note that F20 is also affected.

Steps to Reproduce:
1. yum install exim
2. reboot
3. exim is listening on {::,0.0.0.0}:{25,465,587}

Additional info:
Discussion on -devel: https://lists.fedoraproject.org/pipermail/devel/2014-April/198293.html
[0] https://fedoraproject.org/wiki/Starting_services_by_default

Comment 1 Andy Lutomirski 2014-04-24 16:29:37 UTC
The culprit seems to be alternatives --initscript

Comment 2 Jaroslav Reznik 2015-03-03 15:43:14 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 3 Fedora End Of Life 2016-07-19 11:23:40 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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