Jump to content

Infrastructure/Email: Difference between revisions

From KDE Community Wiki
Add anchor 'SMTP' to section 4 for greater facility with extra-wiki hyperlinks and prepare page for translation
Krop (talk | contribs)
reformat. Move the Gmail trick to a subsection
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<translate>
As it is common for contributors to move between different email providers, email aliases (forwarding addresses) are provided to allow for a consistent email address to be given by a contributor. These are currently offered under two domains: <code>kdemail.net</code> and <code>kde.org</code>.
As it is common for contributors to move between different email providers, email aliases (forwarding addresses) are provided to allow for a consistent email address to be given by a contributor. These are currently offered under two domains: </translate><code>kdemail.net</code> <translate>and </translate><code>kde.org</code>. <translate>


== Requesting an alias ==
== Requesting an alias ==


Any contributor to the KDE project is able to request a </translate><code>kdemail.net</code> <translate>address by submitting a [https://go.kde.org/u/systickets ticket], including the initial destination address of the alias. </translate><code>kdemail.net</code> <translate>addresses must be in the form <code>firstname.lastname</translate>@kdemail.net</code>, <translate>and do not include a mailbox (forwarding, only).
Any contributor to the KDE project is able to request a <code>kdemail.net</code> address by submitting a [https://go.kde.org/u/systickets ticket], including the initial destination address of the alias. <code>kdemail.net</code> addresses must be in the form <code>[email protected]</code>, and do not include a mailbox (forwarding, only).


If a contributor wishes to request a </translate><code>kde.org</code> <translate>address, then they need either the support of two existing </translate><code>kde.org</code> <translate>address holders, or they need to be a member of the KDE e.V. (as an eV-member you are already supported by two persons in the past). Contributors who meet these requirements should file a ticket, mentioning the criteria they qualify under, the desired alias, and the initial destination address of the alias.
If a contributor wishes to request a <code>kde.org</code> address, then they need either the support of two existing <code>kde.org</code> address holders, or they need to be a member of the KDE e.V. (as an eV-member you are already supported by two persons in the past). Contributors who meet these requirements should file a ticket, mentioning the criteria they qualify under, the desired alias, and the initial destination address of the alias.


== Updating your alias ==
== Updating your alias ==


All changes to both kdemail.net and kde.org aliases should be made by filing a [https://go.kde.org/u/systickets ticket]. It is necessary (for authentication purposes) that the ticket is filed using a Identity account associated with the email alias in question.
All changes to both kdemail.net and kde.org aliases should be made by filing a [https://go.kde.org/u/systickets ticket]. It is necessary (for authentication purposes) that the ticket is filed using an Identity account associated with the email alias in question.


Changes can include adding further destination addresses to your alias or removing existing destination addresses.
Changes can include adding further destination addresses to your alias or removing existing destination addresses.
Line 20: Line 19:
For those contributors with either kde.org or kdemail.net aliases who are concerned about losing mail due to this can request that a copy of the filter logs for each day is sent to them by filing a [https://go.kde.org/u/systickets ticket].
For those contributors with either kde.org or kdemail.net aliases who are concerned about losing mail due to this can request that a copy of the filter logs for each day is sent to them by filing a [https://go.kde.org/u/systickets ticket].


</translate><span id="SMTP"></span> <translate>
== Sending email via mail.kde.org ==


== Sending email via mail.kde.org ==
<!-- Please avoid renaming this section. Because this breaks the link that points to it from https://kdemail.net/ If you still feel that rename is necessary, don't forget to send a corresponding MR on https://invent.kde.org/websites/kdemail-net -->


If you wish to use your @kdemail.net or @kde.org address for sending - not just receiving - email, you should do so through mail.kde.org, the primary KDE email server. As an additional benefit, email sent via mail.kde.org from a kde.org address will be signed using DKIM, allowing the recipient to verify the email is legitimate.
If you wish to use your @kdemail.net or @kde.org address for sending - not just receiving - email, you should do so through mail.kde.org, the primary KDE email server. As an additional benefit, email sent via mail.kde.org from a kde.org address will be signed using DKIM, allowing the recipient to verify the email is legitimate.
Line 30: Line 29:
''In 2018 the mail server moved host from postbox.kde.org to letterbox.kde.org, however it is recommended that people use the canonical hostname mail.kde.org in their settings for SMTP as that will point to the correct host even if it changes again''
''In 2018 the mail server moved host from postbox.kde.org to letterbox.kde.org, however it is recommended that people use the canonical hostname mail.kde.org in their settings for SMTP as that will point to the correct host even if it changes again''


The following details should work in most email clients. You should use your Identity username and password to authenticate.</translate>
The following details should work in most email clients. You should use your Identity username and password to authenticate.


<pre>Host Name: mail.kde.org
<pre>Host Name: mail.kde.org
Line 42: Line 41:
Connection Security: STARTTLS
Connection Security: STARTTLS
Authentication: PLAIN</pre>
Authentication: PLAIN</pre>
=== Workarounds ===
Some email clients can't finish setup of <code>kdemail.net</code> address, because of sending-only nature of them.
==== For Gmail users ====
Gmail users can create a [https://support.google.com/mail/answer/22370 sending alias].
The process is straight-forward, just make sure to replace the <code>letterbox.kde.org</code> server suggestion with <code>mail.kde.org</code>. When done, you will be able to select your kdemail alias as sender when using the Gmail webmail.
You may also add it as sending alias to the corresponding Gmail address in your favorite email client.

Latest revision as of 07:10, 22 June 2021

As it is common for contributors to move between different email providers, email aliases (forwarding addresses) are provided to allow for a consistent email address to be given by a contributor. These are currently offered under two domains: kdemail.net and kde.org.

Requesting an alias

Any contributor to the KDE project is able to request a kdemail.net address by submitting a ticket, including the initial destination address of the alias. kdemail.net addresses must be in the form [email protected], and do not include a mailbox (forwarding, only).

If a contributor wishes to request a kde.org address, then they need either the support of two existing kde.org address holders, or they need to be a member of the KDE e.V. (as an eV-member you are already supported by two persons in the past). Contributors who meet these requirements should file a ticket, mentioning the criteria they qualify under, the desired alias, and the initial destination address of the alias.

Updating your alias

All changes to both kdemail.net and kde.org aliases should be made by filing a ticket. It is necessary (for authentication purposes) that the ticket is filed using an Identity account associated with the email alias in question.

Changes can include adding further destination addresses to your alias or removing existing destination addresses.

Filtering

All email destined for kde.org and kdemail.net address is subject to both spam filtering and virus scanning. All mail which is determined to be definite spam or infected by malware will be rejected and not accepted for delivery.

For those contributors with either kde.org or kdemail.net aliases who are concerned about losing mail due to this can request that a copy of the filter logs for each day is sent to them by filing a ticket.

Sending email via mail.kde.org

If you wish to use your @kdemail.net or @kde.org address for sending - not just receiving - email, you should do so through mail.kde.org, the primary KDE email server. As an additional benefit, email sent via mail.kde.org from a kde.org address will be signed using DKIM, allowing the recipient to verify the email is legitimate.

Before doing so, you will need to file a ticket asking for your account to be provisioned with the rights to send email through mail.kde.org. This is not enabled for all accounts by default in order to mitigate the abuse by compromised accounts.

In 2018 the mail server moved host from postbox.kde.org to letterbox.kde.org, however it is recommended that people use the canonical hostname mail.kde.org in their settings for SMTP as that will point to the correct host even if it changes again

The following details should work in most email clients. You should use your Identity username and password to authenticate.

Host Name: mail.kde.org
Port: 465
Connection Security: SASL/TLS
Authentication: PLAIN

or

Host Name: mail.kde.org
Port: 587
Connection Security: STARTTLS
Authentication: PLAIN

Workarounds

Some email clients can't finish setup of kdemail.net address, because of sending-only nature of them.

For Gmail users

Gmail users can create a sending alias.

The process is straight-forward, just make sure to replace the letterbox.kde.org server suggestion with mail.kde.org. When done, you will be able to select your kdemail alias as sender when using the Gmail webmail.

You may also add it as sending alias to the corresponding Gmail address in your favorite email client.