Fix support for /etc/aliases #29
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prior to this commit we used postmap to create the database for all files, including /etc/aliases. However, the traditional sendmail format of /etc/aliases differs from the expected input for postmap. The sendmail format uses a colon and whitespace to separate keys and values, whereas postfix's lookup format, just uses whitespace. This necessitates using postalias when creating databases for sendmail alias files. I'm not sure how the postfix acceptance test passed prior to this change, but at least in my testing this change is required for it to pass.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to this commit we used postmap to create the database for all files, including /etc/aliases. However, the traditional sendmail format of /etc/aliases differs from the expected input for postmap. The sendmail format uses a colon and whitespace to separate keys and values, whereas postfix's lookup format, just uses whitespace. This necessitates using postalias when creating databases for sendmail alias files.
I'm not sure how the postfix acceptance test passed prior to this change, but at least in my testing this change is required for it to pass.