Differences

This shows you the differences between two versions of the page.

--- pages:files:start [2023/01/01 16:02] – mischerh
+++ pages:files:start [2024/06/18 09:34] (current) – mischerh
@@ Line 2: / Line 2: @@
   * {{ :pages:files:dns-abuse-handling-final_1425362607.pdf |ICANN - DNS abuse handling }}
   * {{ :pages:files:ripe-690.pdf|RIPE NCC-690}} - Best Current Operational Practice for Operators: IPv6 prefix assignment for end-users - persistent vs non-persistent, and what size to choose
+  * {{ :pages:files:m3aawg_managing-spf_records-2017-08.pdf | M3AAWG Best Practices for Managing SPF Records}} - Defining and maintaining a Sender Policy Framework (SPF) record is an important part of establishing an email sender’s online identity. SPF, as defined by the IETF (Internet Engineering Task Force) standard RFC 7208 (https://www.rfc-editor.org/rfc/rfc7208.txt) 1, enables senders to identify servers that are authorized to send email on behalf of a domain owner.
   * {{ :pages:files:m3aawg_email_authentication_update-2015.pdf|M3AAWG Trust in Email Begins with Authentication }} - The Internet’s growth allows us to interact with people all over the world. Unfortunately, some of those people do not make good neighbors. Along with the effort to detect and filter the problematic traffic they generate, there is a complementary effort to identify trustworthy participants. In security technology parlance, the first seeks to identify Bad Actors, whereas the second creates ways of distinguishing Good Actors.
+  * {{ :pages:files:m3aawg-email-authentication-recommended-best-practices-09-2020.pdf | M3AAWG Email Authentication Recommended Best Practices 2020}} This document recommends a set of best practices for authenticating email messages using the security protocols Sender Policy Framework (SPF), Domain Keys Identified Mail (DKIM), Domain-based Message Authentication, Reporting & Conformance) DMARC and Authenticated Received Chain (ARC). (Another security protocol, SMTP authentication, meaning the presentation of credentials during the submission of a message by a Mail User Agent (MUA) or Mail Submission Agent (MSA) to a Mail Transfer Agent (MTA) serves a different purpose and is outside the scope of this document.)
+  * {{ :pages:files:m3aawg-sendingdomains10102019nk-2.pdf | M3AAWG Sending Domains Best Common Practices}} When preparing for bulk or transactional email sending, two items require special attention: outbound IP addresses, and the domain names to be used for these communications. For the latter, ESPs (Email Service Providers) go through this set-up process frequently and have to review the same readiness checklist each time. This process may involve individual client preferences and constraints, both legal and technical.
   * {{ :pages:files:parted_0.pdf | Red Hat - Partitioning Disks with parted}}
   * {{ :pages:files:tr-4067.pdf |NetApp - NFS Best Practice and Implementation Guide}}
@@ Line 12: / Line 15: @@
   * {{ :pages:files:1tr112_v13.pdf | Technical Specification of the Broadband-Access-Interfaces in the network of Deutsche Telekom 1 TR 112}}
   * [[pages:files:hettis_hacking_schummelzettel|Hettis Hacking Schummelzettel]]
+  * {{ :pages:files:lit2016-strace.pdf | Mit "strace" zum Linux- und BASH-Versteher / Linux-Versteher dank strace}}
+  * {{ :pages:files:zypper-cheat-sheet-1.pdf |}}
+  * {{ :pages:files:zypper-cheat-sheet-2.pdf |}}