| Summary: | postfix documentation is ambiguous about precedence order of canonical maps | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ondřej Lysoněk <olysonek> | ||||
| Component: | postfix | Assignee: | Jaroslav Škarvada <jskarvad> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Alois Mahdal <amahdal> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 7.3 | CC: | amahdal, carsten.grohmann, kvolny, psklenar, thozza | ||||
| Target Milestone: | rc | Keywords: | FastFix, Patch | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | postfix-2.10.1-7.el7 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-10-30 09:34:56 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: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1298243, 1420851, 1549614 | ||||||
| Attachments: |
|
||||||
VERIFIED with postfix-2.10.1-7.el7.x86_64 The patch has applied successfully. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3085 |
Created attachment 1207498 [details] patch Description of problem: Suppose you have two lookup tables listed in canonical_maps and each of these tables uses all three pattern types (user@domain, user, @domain). Then Postfix looks for a match when rewriting addresses in the following order: Look for a match of: - user@domain in the first table - user@domain in the second table - user in the first table - user in the second table - @domain in the first table - @domain in the second table However, the documentation could be misunderstood and one might think the search order is the following: Look for a match of: - user@domain in the first table - user in the first table - @domain in the first table - user@domain in the second table - user in the second table - @domain in the second table I'm attaching a patch (taken from upstream), which fixes the documentation.