mirror of
https://github.com/YunoHost/doc.git
synced 2024-09-03 20:06:26 +02:00
53 lines
3.5 KiB
Markdown
53 lines
3.5 KiB
Markdown
---
|
||
title: Emails
|
||
template: docs
|
||
taxonomy:
|
||
category: docs
|
||
routes:
|
||
default: '/email'
|
||
---
|
||
|
||
YunoHost comes with a complete mail stack allowing you to host your own email server, and therefore to have your own email addresses in `something@your.domain.tld`.
|
||
|
||
The mail stack includes a SMTP server (postfix), an IMAP server (Dovecot), an antispam (rspamd) and DKIM configuration.
|
||
|
||
## Making sure your setup is right
|
||
|
||
Email is a complicated ecosystem and quite a few details can prevent it from working properly.
|
||
|
||
To validate your setup:
|
||
- if you are self-hosting at home and not using a VPN, ensure [your ISP won't block port 25](/isp) ;
|
||
- route ports according to [this documentation](/isp_box_config) ;
|
||
- carefully configure mail DNS records according to [this documentation](/dns_config) ;
|
||
- test your configuration using the diagnostic features (`Webadmin > Diagnosis > Email`). You can also use [mail-tester.com](https://mail-tester.com), a score of at least 8~9/10 is a reasonnable goal <small>(be careful : only 3 tests per domain per day are allowed)</small>
|
||
|
||
## Email clients
|
||
|
||
To interact with the email sever (read and send emails), you can either install a webclient such as Roundcube or Rainloop on your server - or configure a desktop/mobile client as described in [this page](/email_configure_client).
|
||
|
||
Desktop and mobile clients have the advantage of copying your emails to the device, allowing offline viewing and relative protection against possible hardware failures of your server.
|
||
|
||
## Configuring email aliases and auto-forwards
|
||
|
||
Mail aliases and forwards can be configured for each users. For instance, the first user created on the server automatically has an alias `root@the.domain.tld` configured - meaning that an email sent to this address will end in the inbox of the first user. Automatic forwards may be configured, for instance if an user doesn't want to configure an additional email account and just wants to receive emails from the server on, say, his/her gmail address.
|
||
|
||
Another feature which few people know about is the use of suffixes beginning with "+". For example, emails sent to `johndoe+booking@the.domain.tld` will automatically land in the `booking` dir (lowercase) of John Doe's mailbox or in John Doe's inbox if `booking` directory doesn't exist . It is a practical technique for example to provide an e-mail address to a website, then easily sort (via automatic filters) the mail coming from this website.
|
||
|
||
Groups also can use alias features, by default the group `admins` have `root@<domain.tld>` or `webmaster@<domain.tld>`. [More information to use-it with the dedicated page](/groups_and_permissions#config-alias-group).
|
||
|
||
## What happens if my server becomes unavailable?
|
||
|
||
If your server becomes unavailable, emails sent to your server will stay in a pending queue on the sender's side for as long as ~5 days. The sender's host will regularly try to resend the email, until it drops it if it was unable to send it.
|
||
|
||
## Forms to remove its IP address from the blacklist
|
||
It is possible that the emails sent from your YunoHost instance are considered as spam by the big email services.
|
||
Is it possible that the IP address from your server have been previously been used to sent spam or that these email services consider your server as a spam sender.
|
||
To ensure that your servers’ IP address isn't on these blacklists and to remove it from them, follow this [link](/blacklist_forms).
|
||
|
||
## Migrating email from an email provider to a YunoHost instance
|
||
|
||
See [this page](/email_migration).
|
||
|
||
## Configuring SMTP relay
|
||
|
||
See [this page](/email_configure_relay).
|