emails. This is because the backup or alternative gateways are often poorly maintained with out‐of‐ date blacklists and content filtering. Email can be intercepted anywhere between the originating email server and the destination email server. Email transport between organizations and agencies is usually over the internet or other unsecured public infrastructure so it is important that email interception is carefully managed and suitable controls applied. One effective measure is to use TLS to encrypt the email traffic between email servers. Enabling TLS on the originating and accepting email server will defeat passive attacks on the network, with the exception of cryptanalysis against email traffic. TLS encryption between email servers will not interfere with email content filtering schemes. Email servers will remain compatible with other email servers as IETF’s RFC 3207 specifies the encryption as opportunistic. The Sender Policy Framework (SPF) is an open standard specifying a technical method to prevent sender address forgery. An SPF‐protected domain is less attractive to spammers and phishers because the forged e‐mails are more likely to be caught in spam filters which check the SPF record. Because an SPF‐protected domain is less attractive as a spoofed address, it is less likely to be blacklisted by spam filters and so is less disruptive to email traffic. Having a proper Sender Policy Framework (SPF) record increases the chances people will get emails you send. Without one, your email has a greater chance of being marked as Spam. SPF and alternatives such as Sender ID aid in the detection of spoofed email server address domains. The SPF record specifies a list of IP addresses or domains that are allowed to send mail from a specific domain. If the email server that transmitted the email is not in the list, the verification fails (there are a number of different fail types available). DKIM enables a method of determining spoofed email content. The DKIM record specifies a public key that will sign the content of the message. If the signed digest in the email header doesn't match the signed content of the email the verification fails. 83

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents