Bug 150805
| Summary: | init script failure | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Thomas Zehetbauer <thomasz> |
| Component: | postfix | Assignee: | Thomas Woerner <twoerner> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-03-18 13:42:51 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: | |||
If you modify your alias database you have to run newaliases afterwards. Correct, one has to run newaliases after modifying the aliases file, so why does /etc/init.d/postfix insist on it's broken implementation of newaliases? The postalias call is there to check if the alias_database entry is correct: - syntactically valid - file/files existance - correct permissions - valid db files If there is an other way to check this, then I will replace it. alias_database = ${default_database_type}:/etc/postfix/aliases
is syntactically valid but causes the current initscript to fail
aliases_database is AFAIK only used by newaliases, the MTA processes use the
databases defined in alias_maps
postfix runs fine without an alias_database, even without alias_maps
|
postfix is perfectly fine using alias_database = ${default_database_type}:/etc/postfix/aliases unfortunately /etc/init.d/postfix insists on running postaliases `postconf -h alias_database` that fails in this configuration. The correct solution is to run newaliases instead or not try to update the aliases db at all.