hello friends! new(ish)!
Email: Difference between revisions
>Toynbeeidea |
>Toynbeeidea (→DNS) |
||
| Line 13: | Line 13: | ||
=== DNS === | === DNS === | ||
==== MX Record ==== | ==== MX Record ==== | ||
A '''Mail eXchanger Record (MX record)''' specifies a mail server responsible for accepting email messages on behalf of a recipient's domain, and a preference value is used to prioritize mail delivery if multiple mail servers are available. The set of MX records of a domain name specifies how email should be routed with the Simple Mail Transfer Protocol (SMTP). | |||
==== SPF Record ==== | ==== SPF Record ==== | ||
A '''Sender Policy Framework (SPF)''' record identifies which servers are | A '''Sender Policy Framework (SPF)''' record identifies which servers are ALLOWED to send email on behalf of your domain. The idea is to help prevent domain spoofing by spammers. If a spammer tries to use your domain to forge email, the receiver can check your SPF record and, if it doesn't match, reject it outright. These days most mail servers check for SPF records, and if they don't find one, they will also reject your mail - so you need one. | ||
*[http://www.openspf.org/ SPF Project Overview] | *[http://www.openspf.org/ SPF Project Overview] | ||
| Line 22: | Line 24: | ||
==== DKIM Record ==== | ==== DKIM Record ==== | ||
A ''DomainKeys Identified Mail'', or ''DKIM'' entry provides a 1024-bit public key, unique to your domain, that confirms that an email is actually from your server. It is a complementary check to SPF records. It is not as widely used as SPF yet, but should be set up anyhow. | A '''DomainKeys Identified Mail''', or ''DKIM'' entry provides a 1024-bit public key, unique to your domain, that confirms that an email is actually from a legitimate account on your server. It is a complementary check to SPF records. It is not as widely used as SPF yet, but is in use by gmail and Yahoo, and should be set up anyhow. | ||
*[http://dkim.org/ DomainKeys Identified Mail (DKIM)] | |||
*[http://www.dnswatch.info/dkim/create-dns-record DKIM DNS Wizard] | |||
=== Mail Transfer Agent (MTA) === | === Mail Transfer Agent (MTA) === | ||
Revision as of 16:42, 12 February 2014
Email Providers
If you care about your personal Freedom, you should check out these Privacy-Conscious Email Providers.
Email Clients
Self Hosted Email
See also: Setting_up_a_Server#Setting_Up_Email
The only way to have full control over your email is to host your own mail server.
DNS
MX Record
A Mail eXchanger Record (MX record) specifies a mail server responsible for accepting email messages on behalf of a recipient's domain, and a preference value is used to prioritize mail delivery if multiple mail servers are available. The set of MX records of a domain name specifies how email should be routed with the Simple Mail Transfer Protocol (SMTP).
SPF Record
A Sender Policy Framework (SPF) record identifies which servers are ALLOWED to send email on behalf of your domain. The idea is to help prevent domain spoofing by spammers. If a spammer tries to use your domain to forge email, the receiver can check your SPF record and, if it doesn't match, reject it outright. These days most mail servers check for SPF records, and if they don't find one, they will also reject your mail - so you need one.
DKIM Record
A DomainKeys Identified Mail, or DKIM entry provides a 1024-bit public key, unique to your domain, that confirms that an email is actually from a legitimate account on your server. It is a complementary check to SPF records. It is not as widely used as SPF yet, but is in use by gmail and Yahoo, and should be set up anyhow.