The Sender Policy Framework (SPF), is a technical standard and otentikasi email technique that helps protect email senders and recipients from spam, spoofing, and phishing.
Siap untuk melihat Bird beraksi?
Memahami SPF
The Sender Policy Framework (SPF), is a technical standard and email authentication technique that helps protect email senders and recipients from spam, spoofing, and phishing.
Secara khusus, ini mendefinisikan cara untuk memvalidasi pesan email yang dikirim dari server email yang sah untuk mendeteksi pemalsuan dan mencegah spam. Protokol ini dirancang untuk melengkapi SMTP, protokol dasar yang digunakan untuk mengirim email, karena SMTP sendiri tidak menyertakan mekanisme autentikasi.
Bagaimana cara kerja SPF?
SPF establishes a method for receiving mail servers to verify that incoming email from a domain was sent from a host authorized by that domain’s administrators. It piggybacks on the well-established Domain Name System (DNS). In general terms, the process works like this:
Administrator domain menerbitkan kebijakan yang menentukan server email yang diizinkan untuk mengirim email dari domain tersebut. Kebijakan ini disebut catatan SPF, dan terdaftar sebagai bagian dari keseluruhan catatan DNS domain.
Ketika server email masuk menerima email masuk, server ini akan mencari aturan untuk domain bounce (Return-Path) di DNS. Server email masuk kemudian membandingkan alamat IP pengirim email dengan alamat IP resmi yang ditentukan dalam catatan SPF.
Server email penerima kemudian menggunakan aturan yang ditentukan dalam catatan SPF domain pengirim untuk memutuskan apakah akan menerima, menolak, atau menandai pesan email tersebut.
Apa yang dimaksud dengan catatan SPF?
Rekor SPF disertakan dalam basis data DNS organisasi. Rekor SPF adalah versi yang diformat secara khusus dari rekor TXT DNS standar. Rekor SPF terlihat seperti ini:
mydomain.com TXT "v=spf1 include:myauthorizeddomain.com include:sparkpostmail.com ~all”
Reading left-to-right in plain Inggris, this record is saying that any email that claims to be from “mydomain.com” should be validated with SPF (that’s the “v=spf1” prefix ke record). It then specifies that the SPF records for “myauthorizeddomain.com” and “sparkpostmail.com” also should be included when validating email from mydomain.com (those are the parts labeled “include:”). In practical terms, that usually is done to indicate that the other domains authorized to send email on its behalf. Finally, the record concludes by stating that any other servers claiming to send mail should be flagged as questionable, and possibly failing, the SPF test (“~all”).
Catatan SPF bisa lebih rumit daripada contoh ini, tetapi mekanisme dasarnya tetap sama.
Bagaimana SPF terkait dengan DKIM, DMARC, atau standar lainnya?
SPF, DKIM, dan DMARC merupakan standar yang memungkinkan berbagai aspek autentikasi email. Semua standar ini menangani masalah-masalah yang saling melengkapi.
SPF memungkinkan pengirim untuk menentukan alamat IP mana yang diizinkan untuk mengirim email untuk domain tertentu.
DKIM provides an encryption key and digital signature that verifies that an email message was not faked or altered.
DMARC unifies the SPF and DKIM authentication mechanisms into a common framework and allows domain owners to declare how they would like email from that domain to be handled if it fails an authorization test.
Apakah saya memerlukan SPF?
If you are a business sending commercial or transactional email, you definitely need to implement one or more forms of email authentication to verify that an email is actually from you or your business. Properly configuring email authentication standards like SPF is one of the most important steps you can take to improve your deliverability. However, SPF by itself only goes so far; SparkPost and other email experts recommend also implementing DKIM and DMARC to define a more complete email authentication policy.
Apakah SparkPost mendukung SPF?
Yes. SparkPost implements and adheres to email authentication standards including SPF. In fact, SparkPost handles the SPF part of that automatically, so all email from your account is already SPF-compliant.
Bagaimana cara memverifikasi pengaturan SPF saya?
SparkPost’s free email tools for developers make working with email authentication standards like SPF easy. Our Inspektur SPF lets you quickly check who’s authorized to send email for your domain. And our Pembangun SPF is an easy way to create a working SPF record for your domain.
Baca lebih lanjut tentang praktik terbaik SPF
Learn more about SPF with these resources from SparkPost’s email experts and elsewhere on the web.
Gambaran Umum Proyek Kerangka Kerja Kebijakan Pengirim (Sender Policy Framework/SPF). The group that developed the SPF standard has published detailed explanations, how-to’s, and news about SPF.
RFC 7208. This document published by the Internet Engineering Taskforce (IETF) formally defines the SPF technical standard.
Otentikasi SPF: Tinjauan Umum dan Praktik Terbaik. Practical, hands-on advice for implementing SPF from our email deliverability experts.
Memahami SPF and DKIM In Sixth Grade Inggris. An easy-to-understand explanation of how SPF and DKIM work together to ensure email is authenticated.