| GitHub | https://github.com/Souliboi/ |
| Codeberg | https://codeberg.org/Souliboi |
| Procrastinating work on | https://pokke.moe |
| Pronouns | any/all |
| GitHub | https://github.com/Souliboi/ |
| Codeberg | https://codeberg.org/Souliboi |
| Procrastinating work on | https://pokke.moe |
| Pronouns | any/all |
does someone here knows how dmarc is implemented nowadays?
What happens if an Organizanional Domain cannot be build, since the sender domain is an eTLD. The spec does not cover this [1]
example: nhs.uk – that's an eTLD and at the same time a spf records indicates, that mail can origin from `*@nhs.uk`
[1]: https://datatracker.ietf.org/doc/html/rfc7489#section-3.2
Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling. Originators of Internet Mail need to be able to associate reliable and authenticated domain identifiers with messages, communicate policies about messages that use those identifiers, and report about mail using those identifiers. These abilities have several benefits: Receivers can provide feedback to Domain Owners about the use of their domains; this feedback can provide valuable insight about the management of internal operations and the presence of external domain name abuse. DMARC does not produce or encourage elevated delivery privilege of authenticated email. DMARC is a mechanism for policy distribution that enables increasingly strict handling of messages that fail authentication checks, ranging from no action, through altered delivery, up to message rejection.
psa wg congresstickets: nutzt sofortüberweisungen damit das voucher schneller wiederkommt