docker/docker-mail
1
0
Fork 0
Code Issues 4 Pull Requests Actions Projects Releases 6 Wiki Activity

feat: add dkim, spf and dmarc validation #11

Merged
jon_nfc merged 5 commits from 1-message-authenticity into development 2022-02-17 03:57:26 +00:00
Conversation 18 Commits 5 Files Changed 6 +64 -4
jon_nfc commented 2022-02-16 07:28:16 +00:00 (Migrated from gitlab.com)
Copy Link

🚧 Tasks

  • DKIM Validation $enable_dkim_verification = 1; to amivis config

  • setup spf

  • spf validation

  • setup dmarc

  • dmarc validation

- Releated to #1 ### :construction: Tasks - [x] DKIM Validation `$enable_dkim_verification = 1;` to amivis config - [x] setup spf - [x] [spf validation](https://debian.pkgs.org/sid/debian-main-arm64/postfix-policyd-spf-python_2.9.3-1_all.deb.html) - [ ] setup dmarc - [ ] dmarc validation
jon_nfc (Migrated from gitlab.com) approved these changes 2022-02-16 07:28:16 +00:00
jon_nfc commented 2022-02-16 07:28:17 +00:00 (Migrated from gitlab.com)
Copy Link

assigned to @jon_nfc

assigned to @jon_nfc
jon_nfc commented 2022-02-16 07:30:17 +00:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
jon_nfc commented 2022-02-16 08:14:45 +00:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
jon_nfc commented 2022-02-17 02:47:10 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • 245aa724 - feat(spf): conduct spf check for inbound smtp

Compare with previous version

added 1 commit <ul><li>245aa724 - feat(spf): conduct spf check for inbound smtp</li></ul> [Compare with previous version](/nofusscomputing/projects/docker-mail/-/merge_requests/6/diffs?diff_id=333613500&start_sha=fb909c009a572138153831f338993de5b9a7579e)
jon_nfc commented 2022-02-17 03:10:15 +00:00 (Migrated from gitlab.com)
Copy Link

added 2 commits

  • 92e4e4b2 - feat(amavis): added DKIM verification
  • ac706ed2 - test: mail hostname set to non-existent domain

Compare with previous version

added 2 commits <ul><li>92e4e4b2 - feat(amavis): added DKIM verification</li><li>ac706ed2 - test: mail hostname set to non-existent domain</li></ul> [Compare with previous version](/nofusscomputing/projects/docker-mail/-/merge_requests/6/diffs?diff_id=333620431&start_sha=245aa724d2d8121c7a758da6e086fe0a59c751d8)
jon_nfc commented 2022-02-17 03:10:15 +00:00 (Migrated from gitlab.com)
Copy Link

marked the checklist item DKIM Validation $enable_dkim_verification = 1; to amivis config as completed

marked the checklist item **DKIM Validation `$enable_dkim_verification = 1;` to amivis config** as completed
jon_nfc commented 2022-02-17 03:19:21 +00:00 (Migrated from gitlab.com)
Copy Link

marked the checklist item spf validation as completed

marked the checklist item **[spf validation](https://debian.pkgs.org/sid/debian-main-arm64/postfix-policyd-spf-python_2.9.3-1_all.deb.html)** as completed
jon_nfc commented 2022-02-17 03:49:04 +00:00 (Migrated from gitlab.com)
Copy Link

marked the checklist item setup spf as completed

marked the checklist item **setup spf** as completed
jon_nfc commented 2022-02-17 03:49:04 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • a71e7691 - docs(spf): added basic spf guide

Compare with previous version

added 1 commit <ul><li>a71e7691 - docs(spf): added basic spf guide</li></ul> [Compare with previous version](/nofusscomputing/projects/docker-mail/-/merge_requests/6/diffs?diff_id=333631331&start_sha=ac706ed28b635efb0eec0112f6f86a2e276cd237)
jon_nfc commented 2022-02-17 03:50:53 +00:00 (Migrated from gitlab.com)
Copy Link
# Don't bounce mail (False). to bounce mail set to Fail
```suggestion:-0+0 # Don't bounce mail (False). to bounce mail set to Fail ```
jon_nfc commented 2022-02-17 03:52:02 +00:00 (Migrated from gitlab.com)
Copy Link

resolved all threads

resolved all threads
jon_nfc commented 2022-02-17 03:52:03 +00:00 (Migrated from gitlab.com)
Copy Link

changed this line in version 4 of the diff

changed this line in [version 4 of the diff](/nofusscomputing/projects/docker-mail/-/merge_requests/6/diffs?diff_id=333632168&start_sha=a71e7691a2188fb9372c2e7c9b32cb39adb4e8ce#cf30e86812c8e16b01b31f06791bfd1f5c77cf7e_7_7)
jon_nfc commented 2022-02-17 03:52:03 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • bde6c054 - refactor: conf config values updated

Compare with previous version

added 1 commit <ul><li>bde6c054 - refactor: conf config values updated</li></ul> [Compare with previous version](/nofusscomputing/projects/docker-mail/-/merge_requests/6/diffs?diff_id=333632168&start_sha=a71e7691a2188fb9372c2e7c9b32cb39adb4e8ce)
jon_nfc commented 2022-02-17 03:57:22 +00:00 (Migrated from gitlab.com)
Copy Link

approved this merge request

approved this merge request
jon_nfc commented 2022-02-17 03:57:26 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 91d65302cb

mentioned in commit 91d65302cbbc69bce98c2991c93043e1a9264844
jon_nfc (Migrated from gitlab.com) merged commit 91d65302cb into development 2022-02-17 03:57:26 +00:00
jon_nfc commented 2022-02-17 03:57:43 +00:00 (Migrated from gitlab.com)
Copy Link

added 5h 10m of time spent

added 5h 10m of time spent
jon_nfc commented 2022-02-17 04:11:56 +00:00 (Migrated from gitlab.com)
Copy Link

added 12m of time spent

added 12m of time spent
Sign in to join this conversation.
Reviewers
No Reviewers
jon_nfc
Labels
Clear labels
Bug
Used in discussion about a bug in comments or commits
CVE-2023-5764
Denotes items related to the CVE
CodeReview
Used in comments (issues/MR/commits) to denote code review related items
Documentation
Documentation items
Feature
Used in discussion about a Feature in comments or commits
Lint
Used in comments (issues/MR/commits) to denote lint tasks todo, done, fixed
Privacy
Used in comments (issues/MR/commits) to denote privacy related items
Security
Used in comments (issues/MR/commits) to denote Security related items
breaking-change
label used to denote that the issue/Merge Request does/will introduce a breaking change
bug::reproducable
Given to an issue when the bug has been confirmed as re-producable. Can also be used in comments and commits.
bug::unable to reproduce
Given to an issue when the bug that is not able to be reproduced. Can also be used in comments and commits.
code review::complete
code review::not started
code review::rejected
code review::underway
difficulty::Full Development
Level 3. Difficulty representing that the task to complete must be planned and created.
difficulty::Good First Issue
Level 1. Difficulty representing that the task is very simple and with limited knowledge can be completed.
difficulty::Prior Knowledge
Level 2. Difficulty representing that the task requires some prior knowledge of either the technology or the project for task completion.
documentation::complete
Issues, Merge Requests
documentation::no change required
Issues, Merge Requests and used to denote no documentation changes required
documentation::not started
Issues, Merge Requests
documentation::stalled
Issues, Merge Requests
documentation::underway
Issues, Merge Requests
impact::0
impact::1
impact::2
impact::3
impact::4
impact::5
ops::ansible-roles
OPS project tag
ops::automation
ops::gitlab-ci
OPS project tag
ops::marcas
OPS project tag
ops::python-gitlab-management
OPS project tag
ops::website
priority::0
priority::1
priority::2
priority::3
priority::4
priority::5
stage::Ready for Development
stage::develop
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::feedback required
stage::planning
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::test
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stale
Label given to issues/merge requests that are considered stale due to no collaboration and is a mark for closure.
triage
Tag given to issues/merge requests requiring triaging by the team.
triage::not_confidential
This tag is given by the triage bot so that URLs can be added to an issue/comment. A triage policy for NFC wide should remove this label.
type::CI / CD
type::automation
This type is used to denote an automation job
type::bug
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::compliance
type::discussion
Type for Issues. Can also be used in discussion in comments.
type::documentation
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::feature
type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::invalid
label given to tickets that require no action or are deem as invalid.
type::quality assurance
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::question
Type for Issues. Can also be used in discussion in comments.
type::security
Type for Issues and Merge Requests.
type::specification
Design specification
workflow::complete
Issues, Merge Requests
workflow::not ready
workflow::not ready::blocked
workflow::not started
Issues, Merge Requests
workflow::ready to commence
Issues, Merge Requests
workflow::stalled
Label given to issues/merge requests where no work has occured in x days iaw triage policy.
workflow::underway
Issues, Merge Requests
workflow::underway::develop
No Label
impact::0
priority::0
type::feature
Milestone
No items
No Milestone docker-mail - v0.1.0
Projects
Clear projects
No project
Assignees
Clear assignees
jon
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: docker/docker-mail#11
No description provided.
Delete Branch "1-message-authenticity"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?