diff options
| -rw-r--r-- | e-post/doman.mdwn | 37 |
1 files changed, 19 insertions, 18 deletions
diff --git a/e-post/doman.mdwn b/e-post/doman.mdwn index e48c93a..c01a5f5 100644 --- a/e-post/doman.mdwn +++ b/e-post/doman.mdwn @@ -68,8 +68,8 @@ According to [RFC 822 Section 6.3](https://tools.ietf.org/html/rfc822#section-6. addresses `postmaster@yourdomain.se` and `abuse@yourdomain.se` are both reserved and required, and *must* be routed to the person(s) responsible for your domain's mail system i.e. `admin@fripost.org`. For convenience -we also deliver such messages to the domain owner, but *beware that we -will also receive them*! +they are also automatically forwarded to the domain owner(s), but +*beware that we will also receive and read them*! On a related note, we encourage domain owners to create aliases for common roles and services such as `root@`, `hostmaster@`, `webmaster@`, @@ -77,27 +77,28 @@ etc. See [RFC 2142](https://tools.ietf.org/html/rfc2142) for details. ## I want my domain `example.net` to mirror my other domain `example.org`, but only add addresses under the later. -What you want is to make `example.net` a *domain alias*, and to point it +What you want is to make `example.net` a *domain alias* and point it to `example.org`. You won't be able to configure `example.org` directly (you won't be able to create `my-alias@example.net` for instance); instead any message to say, `whatever@example.net` will be routed to -`whatever@example.org` (hence it'll bounce if the latter doesn't exist). +`whatever@example.org` (if it exists; the message will bounce otherwise). Just drop us a line at `admin@fripost.org` if you want a domain alias, -and tell us its destination (as with regular aliases the destination -doesn't have to be hosted by Fripost). +and tell us its destination (just like with regular aliases, the +destination doesn't have to be hosted at Fripost). ## I want to receive messages sent to `anything@example.org`, but I can't create an infinite number of aliases! -No problem, we can add a catch-all address on your domain; it has the -lowest priority, so you can still have regular aliases and point them to +No problem, we can add a catch-all address on your domain; catch alls +have the lowest priority, so you can still have regular aliases and +point them to another address (`anything@example.org` will be delivered to the catch-all address *only* if `anything@example.org` is not an explicity existing address). Beware that you may receive a lot of Junk on your catch-all address, though! (Spammer like to shoot randomly, as it's a way to discover what are the valid recipients under a given domain.) -Also, please don't forget the reserved addresses `postmaster@` and -`abuse@`, which have a special treatment and will bypass your catchall -address, see above. +Also, don't forget that the reserved addresses `postmaster@` and +`abuse@` have a special treatment and will always bypass your catchall +address (see above). ## Why are my outgoing emails signed with Fripost's DKIM key? @@ -128,9 +129,9 @@ the last time it sees it, just before throwing it in the wild, and can guaranty its integrity on your behalf. If you use your own domain for outgoing mail, note however that the -fact that your messages are signed by Fripost's key and not your own -might be emphasized by the receiver's mail client (GMail -[surely does](https://support.google.com/mail/answer/1311182), for +receiver's mail client might emphasize that your messages are signed by +Fripost's key and not your own +(GMail [surely does](https://support.google.com/mail/answer/1311182), for instance). This doesn't really disclose anything as our domain can be found in the mail header anyway, but if you prefer to have your own key drop us a line, we will find something out. @@ -150,15 +151,15 @@ has a nice introduction to SPF; other references include the $ dig +short outgoing.fripost.org TXT "v=spf1 a ?all" -What it says is that `outgoing.fripost.org` is authorized to send mails -`@fripost.org` (more precisely, that the authorized sending hosts' IPs +This essentially says that `outgoing.fripost.org` is authorized to send mails +from `@fripost.org` addresses (more precisely, that the authorized sending hosts' IPs can be found in the A and AAAA records for `outgoing.fripost.org`). This host is used whenever you use our Mail Submission agent or webmail for instance; if a message from a `@fripost.org` address is being sent from another host, the `?all` (aka [NEUTRAL](http://www.openspf.org/SPF_Record_Syntax)) says that we don't know whether the host is authorized or not, and that the receiver -should proceeed as if there wasn't an SPF policy. With that information +should proceeed as if there wasn't any SPF policy. With that information at hand, the recipient may decide to classify the message as SPAM or HAM for instance. @@ -194,5 +195,5 @@ OpenSPF's [FAQ](http://www.openspf.org/FAQ), [Best Practices](http://www.openspf.org/Best_Practices) pages. There are e-mail based SPF testers; unfortunately the "official" `spf-test@openspf.net` doesn't work anymore, but you can use -[Port25](http://www.port25.com/support/authentication-center/email-verification/)'s +[Port25.com](http://www.port25.com/support/authentication-center/email-verification/)'s for instance. |