-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code review: real-postfix #3
base: master
Are you sure you want to change the base?
Conversation
…server is not in the user's IPv4 pool
…rewrite -> @scripts.mit.edu happens before transport_maps.
…port_maps, so we need to avoid returning virtual aliases
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've reviewed, I think, all of this except for the virtual_alias_{maps,domains} and smtp_generic_maps part -- which is to say, about half the files, and I think much less than that of the complexity. Files remaining to review:
- generic_strip_pool
- pass-scripts.mit.edu{,-suffix}
- main.cf.j2
- virtual-alias-domains-ldap.cf.j2
- virtual-alias-maps-ldap{,-reserved}.cf.j2
- virtual-alias-maps-relay{,-user,-user-suffix}-ldap.cf.j2
I've got some comments, but they're mostly ~style things -- I wouldn't have a problem with merging the portion I've reviewed as-is if you wanted.
@@ -0,0 +1,7 @@ | |||
# N.B. If this /does/ match, the user is /blocked/. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This feels unnecessarily confusing. While I appreciate a desire to match the authorized_submit_users
config option name, I think it'd be better to name this file blocked-submit-users-ldap.cf
or similar, which then wouldn't need a comment to understand.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We talked about this some today, and I think the conclusion was that while renaming would make sense, there's a lack of enthusiasm to mess with what's not broken, which seems reasonable.
ansible/roles/real-postfix/templates/postfix/mailbox-command-maps-ldap.cf.j2
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have more concerns with this batch, especially as it relates to domains on the other pool. If this was pre-commit code review, I'd want to see them addressed before merging.
ansible/roles/real-postfix/templates/postfix/virtual-alias-domains-ldap.cf.j2
Show resolved
Hide resolved
ansible/roles/real-postfix/templates/postfix/virtual-alias-domains-ldap.cf.j2
Show resolved
Hide resolved
ansible/roles/real-postfix/templates/postfix/virtual-alias-maps-relay-ldap.cf.j2
Show resolved
Hide resolved
ansible/roles/real-postfix/templates/postfix/virtual-alias-maps-relay-user-ldap.cf.j2
Show resolved
Hide resolved
ansible/roles/real-postfix/templates/postfix/virtual-alias-maps-relay-user-suffix-ldap.cf.j2
Show resolved
Hide resolved
I also wrote some comments on what virtual_alias_domains is doing that may be useful -- it's at dehnert@05ea851. |
My little test script:
|
This is a placeholder PR for tracking the code review of the real-postfix role. It consists of the current master (commit 40aaee3), plus commits to ansible-realserver (commit b908d64) that modify ansible/roles/real-postfix (
git filter-repo --path ansible/roles/real-postfix/
plus some cherry-picking onto master). It shouldn't actually get merged (and may or may not be a reasonable way to code review this...).