docs(deps): bump mkdocs-material to 7.1.6 (#2015)

* docs(deps): bump mkdocs-material to 7.1.6

* chore: trigger preview on changes to preview workflows too

* fix: replace deprecated admonition

Co-authored-by: Brennan Kinney <5098581+polarathene@users.noreply.github.com>

.github/workflows/docs-preview-prepare.yml

@@ -4,6 +4,8 @@ on:
   pull_request:
     paths:
       - 'docs/**'
+      - '.github/workflows/scripts/docs/build-docs.sh'
+      - '.github/workflows/docs-preview-prepare.yml'
 
 # If the workflow for a PR is triggered multiple times, previous existing runs will be canceled.
 # eg: Applying multiple suggestions from a review directly via the Github UI.
@@ -67,4 +69,3 @@ jobs:
           name: preview-build
           path: artifact.tar.zst
           retention-days: 1
-

.github/workflows/scripts/docs/build-docs.sh

@@ -6,7 +6,7 @@ docker run \
   --rm \
   --user "$(id -u):$(id -g)" \
   -v "${PWD}:/docs" \
-  squidfunk/mkdocs-material:7.1.5 build --strict
+  squidfunk/mkdocs-material:7.1.6 build --strict
 
 # Remove unnecessary build artifacts: https://github.com/squidfunk/mkdocs-material/issues/2519
 cd site || exit

docs/content/config/advanced/override-defaults/postfix.md

@@ -14,7 +14,7 @@ message_size_limit = 52428800
 
 That specific example is now supported and can be handled by setting `POSTFIX_MESSAGE_SIZE_LIMIT`.
 
-!!! seealso
+!!! note
 
     [Postfix documentation](http://www.postfix.org/documentation.html) remains the best place to find configuration options.
 

docs/content/config/best-practices/dkim.md

@@ -4,7 +4,7 @@ title: 'Best Practices | DKIM'
 
 DKIM is a security measure targeting email spoofing. It is greatly recommended one activates it.
 
-!!! seealso
+!!! note
     See [the Wikipedia page](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) for more details on DKIM.
 
 ## Enabling DKIM Signature

docs/content/config/best-practices/dmarc.md

@@ -4,7 +4,7 @@ hide:
   - toc # Hide Table of Contents for this page
 ---
 
-!!! seealso
+!!! note
     DMARC Guide: https://github.com/internetstandards/toolbox-wiki/blob/master/DMARC-how-to.md
 
 ## Enabling DMARC

docs/content/config/best-practices/spf.md

@@ -9,7 +9,7 @@ From [Wikipedia](https://en.wikipedia.org/wiki/Sender_Policy_Framework):
 !!! quote
     Sender Policy Framework (SPF) is a simple email-validation system designed to detect email spoofing by providing a mechanism to allow receiving mail exchangers to check that incoming mail from a domain comes from a host authorized by that domain's administrators. The list of authorized sending hosts for a domain is published in the Domain Name System (DNS) records for that domain in the form of a specially formatted TXT record. Email spam and phishing often use forged "from" addresses, so publishing and checking SPF records can be considered anti-spam techniques.
 
-!!! seealso
+!!! note
     For a more technical review: https://github.com/internetstandards/toolbox-wiki/blob/master/SPF-how-to.md
 
 ## Add a SPF Record

docs/content/examples/uses-cases/forward-only-mailserver-with-ldap-authentication.md

@@ -100,7 +100,7 @@ You see that besides `query_filter`, I had to customize as well `result_attribut
 
     For more details about using LDAP see: [LDAP managed mail server with Postfix and Dovecot for multiple domains](https://www.vennedey.net/resources/2-LDAP-managed-mail-server-with-Postfix-and-Dovecot-for-multiple-domains)
 
-!!! seealso
+!!! note
 
     Another solution that serves as a forward-only mailserver is this: https://gitlab.com/docker-scripts/postfix