We are still actively working on the spam issue.
Difference between revisions of "Email"
m |
({{Stub}}, {{Cleanup}}, some cleanup) |
||
| Line 1: | Line 1: | ||
| + | {{Stub}} | ||
| + | {{Cleanup}} | ||
| + | |||
== Email Providers == | == Email Providers == | ||
| − | If you care about your personal [[ | + | If you care about your personal [[freedom]], you should check out these [http://prxbx.com/email/ Privacy-Conscious Email Providers]. |
== Email Clients == | == Email Clients == | ||
| Line 16: | Line 19: | ||
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). | 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). | ||
| − | *[http://www.petri.co.il/configure_mx_records_for_incoming_smtp_email_traffic.htm Configure MX Records for Incoming SMTP E-Mail Traffic] | + | * [http://www.petri.co.il/configure_mx_records_for_incoming_smtp_email_traffic.htm Configure MX Records for Incoming SMTP E-Mail Traffic] |
==== SPF Record ==== | ==== 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. | 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] |
| − | *[http://spfwizard.com/ EasySPF] | + | * [http://spfwizard.com/ EasySPF] |
| − | *[http://www.spfwizard.net/ SPF Wizard] | + | * [http://www.spfwizard.net/ SPF Wizard] |
==== 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 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 | + | 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://dkim.org/ DomainKeys Identified Mail (DKIM)] |
| − | *[http://www.dnswatch.info/dkim/create-dns-record DKIM DNS Wizard] | + | * [http://www.dnswatch.info/dkim/create-dns-record DKIM DNS Wizard] |
=== Mail Transfer Agent (MTA) === | === Mail Transfer Agent (MTA) === | ||
| Line 43: | Line 46: | ||
== External Links == | == External Links == | ||
| − | http://flurdy.com/docs/postfix/ | + | * [http://flurdy.com/docs/postfix/ How to set up a mail server on a GNU / Linux system] - flurdy.com |
Revision as of 03:32, 14 February 2014
This dongle is a 
Contents
Email Providers
If you care about your personal freedom, you should check out these Privacy-Conscious Email Providers.
Email Clients
Recommended_software#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.
Mail Transfer Agent (MTA)
Postfix
Mail Delivery Agent (MDA)
Dovecot
Spam Prevention
SpamAssassin
Security
External Links
- How to set up a mail server on a GNU / Linux system - flurdy.com
