mirror of
https://github.com/YunoHost/doc.git
synced 2024-09-03 20:06:26 +02:00
Correct spelling (#2296)
Mostly adress -> address Also reworded bits of a section in email.md
This commit is contained in:
parent
57f0439dea
commit
ffb294d92d
12 changed files with 15 additions and 15 deletions
|
@ -665,7 +665,7 @@ In an internet browser, type **{% if internetcube %}`https://internetcube.local`
|
||||||
|
|
||||||
!!! If this doesn't work, you can [look for the the local IP address of your server](/finding_the_local_ip). The address typically looks like `192.168.x.y`, and you should therefore type `https://192.168.x.y` in your browser's address bar.
|
!!! If this doesn't work, you can [look for the the local IP address of your server](/finding_the_local_ip). The address typically looks like `192.168.x.y`, and you should therefore type `https://192.168.x.y` in your browser's address bar.
|
||||||
{% else %}
|
{% else %}
|
||||||
You can perform the initial configuration with the web interface by typing in the adress bar of your web browser **the public IP address of your server**. Typically, your VPS provider should have provided you with the IP of the server.
|
You can perform the initial configuration with the web interface by typing in the address bar of your web browser **the public IP address of your server**. Typically, your VPS provider should have provided you with the IP of the server.
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
|
||||||
! During the first visit, you will very likely encounter a security warning related to the certificate used by the server. For now, your server uses a self-signed certificate. {% if not wsl %}You will later be able to add a certificate automatically recognized by web browsers as described in the [certificate documentation](/certificate). {% endif %} For now, you should add a security exception to accept the current certificate. (Though, PLEASE, do not take the habit of blindly accepting this kind of security alert!)
|
! During the first visit, you will very likely encounter a security warning related to the certificate used by the server. For now, your server uses a self-signed certificate. {% if not wsl %}You will later be able to add a certificate automatically recognized by web browsers as described in the [certificate documentation](/certificate). {% endif %} For now, you should add a security exception to accept the current certificate. (Though, PLEASE, do not take the habit of blindly accepting this kind of security alert!)
|
||||||
|
|
|
@ -13,7 +13,7 @@ routes:
|
||||||
|
|
||||||
Users are human being who have access to applications and other services on your server. The administrator can add and manage users through the web administration (in the User category) or through the command line (see `yunohost user --help`). After that, users obtain a personal email address (chosen by the admin), an XMPP account, and can log in the user portal to access applications they have permissions over and configure other parameters.
|
Users are human being who have access to applications and other services on your server. The administrator can add and manage users through the web administration (in the User category) or through the command line (see `yunohost user --help`). After that, users obtain a personal email address (chosen by the admin), an XMPP account, and can log in the user portal to access applications they have permissions over and configure other parameters.
|
||||||
|
|
||||||
The first user created also automatically gets email aliases `root@main.domain.tld` and `admin@main.domain.tld`, such that mail sent to these adresses will end up in the first user's mailbox.
|
The first user created also automatically gets email aliases `root@main.domain.tld` and `admin@main.domain.tld`, such that mail sent to these addresses will end up in the first user's mailbox.
|
||||||
|
|
||||||
! You should be careful about who you give your server access to. In terms of security, this largely increase the attack surface for someone who wants to mess with the server one way or another.
|
! You should be careful about who you give your server access to. In terms of security, this largely increase the attack surface for someone who wants to mess with the server one way or another.
|
||||||
|
|
||||||
|
|
|
@ -10,7 +10,7 @@ shortcode-ui:
|
||||||
tabs: lite
|
tabs: lite
|
||||||
---
|
---
|
||||||
|
|
||||||
DNS (Domain Name System) is a system that allows computers from around the world to translate human-readable domain names (such as `yolo.com`) to machine-understandable adresses called IP addresses (such as `11.22.33.44`). For this translation (and other features) to work, you must carefully configure DNS records.
|
DNS (Domain Name System) is a system that allows computers from around the world to translate human-readable domain names (such as `yolo.com`) to machine-understandable addresses called IP addresses (such as `11.22.33.44`). For this translation (and other features) to work, you must carefully configure DNS records.
|
||||||
|
|
||||||
YunoHost allows you to manage and serve several domains on the same server with the same public ip. For instance, you can host a blog and Nextcloud on a first domain `yolo.com`, and a web mail client on a second domain `swag.nohost.me`. Each domain is automatically configured to handle web services, mail services and XMPP services.
|
YunoHost allows you to manage and serve several domains on the same server with the same public ip. For instance, you can host a blog and Nextcloud on a first domain `yolo.com`, and a web mail client on a second domain `swag.nohost.me`. Each domain is automatically configured to handle web services, mail services and XMPP services.
|
||||||
|
|
||||||
|
|
|
@ -29,7 +29,7 @@ Desktop and mobile clients have the advantage of copying your emails to the devi
|
||||||
|
|
||||||
## Configuring email aliases and auto-forwards
|
## 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 adress 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.
|
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.
|
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.
|
||||||
|
|
||||||
|
@ -37,12 +37,12 @@ Groups also can use alias features, by default the group `admins` have `root@<do
|
||||||
|
|
||||||
## What happens if my server becomes unavailable?
|
## 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 hoster will regularly try to resend the email, until it drops it if it was unable to send it.
|
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
|
## Forms to remove its IP address from the blacklist
|
||||||
It is possible that the sent emails from your YunoHost instance are considered as spam by the big email services.
|
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.
|
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 into this blacklists and to remove it from them, follow this [link](/blacklist_forms).
|
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
|
## Migrating email from an email provider to a YunoHost instance
|
||||||
|
|
||||||
|
|
|
@ -14,7 +14,7 @@ This page provide an overview of the ecosystem of a YunoHost server. While this
|
||||||
|
|
||||||
Everything starts with the special user **admin**. This is the administrator of the machine who can install, configure and manage things on the server through the web administration interface, or via SSH and the command line interface. *(If you are already familiar with GNU/Linux, it is quite similar to root. YunoHost has this additional 'admin' user for several technical reasons.)*
|
Everything starts with the special user **admin**. This is the administrator of the machine who can install, configure and manage things on the server through the web administration interface, or via SSH and the command line interface. *(If you are already familiar with GNU/Linux, it is quite similar to root. YunoHost has this additional 'admin' user for several technical reasons.)*
|
||||||
|
|
||||||
The administrator can create users and install applications, among other admin actions. Users automatically have their own email adress as well as an XMPP account when they get created. Users will also be able to connect to the user portal (SSO) to access applications. Some applications can typically be installed either as publicly-accessible, or as private, i.e. only some users will have access to it.
|
The administrator can create users and install applications, among other admin actions. Users automatically have their own email address as well as an XMPP account when they get created. Users will also be able to connect to the user portal (SSO) to access applications. Some applications can typically be installed either as publicly-accessible, or as private, i.e. only some users will have access to it.
|
||||||
|
|
||||||
Applications and their features of the server rely on different services to work properly. Services (sometimes also called daemons) are programs that are constantly running on the server to ensure various tasks are done, such as answering to web requests from web browsers, or relaying emails.
|
Applications and their features of the server rely on different services to work properly. Services (sometimes also called daemons) are programs that are constantly running on the server to ensure various tasks are done, such as answering to web requests from web browsers, or relaying emails.
|
||||||
|
|
||||||
|
|
|
@ -13,7 +13,7 @@ This tutorial aim to get around dynamic IP issue which is: when the IP public ad
|
||||||
|
|
||||||
After setting up the solution proposed in this tutorial, the redirection from your domain name to the actual IP address of your server will not be lost anymore.
|
After setting up the solution proposed in this tutorial, the redirection from your domain name to the actual IP address of your server will not be lost anymore.
|
||||||
|
|
||||||
The method proposed here consists of automatizing the fact the box annonces its global IP adress change to the dynamic DNS, so that the DNS zone will automatically be updated.
|
The method proposed here consists of automatizing the fact the box announces its global IP address change to the dynamic DNS, so that the DNS zone will automatically be updated.
|
||||||
|
|
||||||
### Registrars
|
### Registrars
|
||||||
|
|
||||||
|
|
|
@ -23,7 +23,7 @@ Install the program and run *Filezilla*.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
2. Click **New Site** and give a name the server you will be using : *Family* here. Fill the settings as on the screenshot (replace the server adress with your own), and click on **Connect**. (N.B. : if you want to interact with the [custom webapp](https://github.com/YunoHost-Apps/my_webapp_ynh) files, you should use a different user than `admin`. Refer to the custom webapp documentation.)
|
2. Click **New Site** and give a name the server you will be using : *Family* here. Fill the settings as on the screenshot (replace the server address with your own), and click on **Connect**. (N.B. : if you want to interact with the [custom webapp](https://github.com/YunoHost-Apps/my_webapp_ynh) files, you should use a different user than `admin`. Refer to the custom webapp documentation.)
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
|
|
|
@ -37,7 +37,7 @@ then erase everything below, and replace it with the configuration generated by
|
||||||
|
|
||||||
You should follow this part if you have a dynamic IP.
|
You should follow this part if you have a dynamic IP.
|
||||||
|
|
||||||
Find out if your ISP provides you with a dynamic IP adress [here](/isp).
|
Find out if your ISP provides you with a dynamic IP address [here](/isp).
|
||||||
|
|
||||||
Let's create a DynHost id.
|
Let's create a DynHost id.
|
||||||
|
|
||||||
|
|
|
@ -50,7 +50,7 @@ Follow the following steps. (As for Thunderbird, you might need to accept certif
|
||||||
|
|
||||||
The first time you can simply choose "Add account". If you already have an account configured, tap the hamburger menu then tap the gear, choose Mail, Accounts and press the '+'-symbol.
|
The first time you can simply choose "Add account". If you already have an account configured, tap the hamburger menu then tap the gear, choose Mail, Accounts and press the '+'-symbol.
|
||||||
|
|
||||||
Then you choose IMAP. Fill in the fields and press Next. Now Dekko will look for the configuration. Check that all fields are correct. Make sure you have your yunohost username, NOT your mailadress and choose "Allow untrusted certificates". Do this for IMAP and SMTP and press Next. Dekko will now synchronise the account after which you are done. Congratz!
|
Then you choose IMAP. Fill in the fields and press Next. Now Dekko will look for the configuration. Check that all fields are correct. Make sure you have your yunohost username, NOT your email address and choose "Allow untrusted certificates". Do this for IMAP and SMTP and press Next. Dekko will now synchronise the account after which you are done. Congratz!
|
||||||
|
|
||||||

|

|
||||||

|

|
||||||
|
|
|
@ -62,7 +62,7 @@ Make sure it is filled with:
|
||||||
|
|
||||||
Save.
|
Save.
|
||||||
|
|
||||||
Now, the adressbook is accessible.
|
Now, the address book is accessible.
|
||||||
|
|
||||||
## Useful links
|
## Useful links
|
||||||
|
|
||||||
|
|
|
@ -9,7 +9,7 @@ routes:
|
||||||
|
|
||||||
[](https://install-app.yunohost.org/?app=emailpoubelle) [](https://dash.yunohost.org/appci/app/emailpoubelle)
|
[](https://install-app.yunohost.org/?app=emailpoubelle) [](https://dash.yunohost.org/appci/app/emailpoubelle)
|
||||||
|
|
||||||
*EmailPoubelle* (Trash email) is a script to create temporay email adresses that aims to your real email address.
|
*EmailPoubelle* (Trash email) is a script to create temporary email addresses that aims to your real email address.
|
||||||
A YunoHost version of EmailPoubelle by David Mercereau. All thanks to David.
|
A YunoHost version of EmailPoubelle by David Mercereau. All thanks to David.
|
||||||
|
|
||||||
### Disclaimers / important information
|
### Disclaimers / important information
|
||||||
|
|
|
@ -22,7 +22,7 @@ In order to do so, go to Actions -> Configuration -> feed tab -> OPML section ->
|
||||||
You can read your feeds on Android using ttrss-reader application: **[ttrss-reader](https://f-droid.org/packages/org.ttrssreader/)**
|
You can read your feeds on Android using ttrss-reader application: **[ttrss-reader](https://f-droid.org/packages/org.ttrssreader/)**
|
||||||
|
|
||||||
To use it, you need to go to Actions -> Configuration, in Tiny Tiny RSS web interface and select "Activate API".
|
To use it, you need to go to Actions -> Configuration, in Tiny Tiny RSS web interface and select "Activate API".
|
||||||
Then, in your android ttrss-reader, fill the Tiny Tiny RSS server adress: https://yourdomain.org/ttrss, username, password (no need to use HTTP authentification).
|
Then, in your android ttrss-reader, fill the Tiny Tiny RSS server address: https://yourdomain.org/ttrss, username, password (no need to use HTTP authentication).
|
||||||
|
|
||||||
**Note**: you may need to uninstall and reinstall the Tiny Tiny RSS application through the YunoHost admin panel in order to be able to connect.
|
**Note**: you may need to uninstall and reinstall the Tiny Tiny RSS application through the YunoHost admin panel in order to be able to connect.
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue