GitLab

Otherwise it's possible to submit the form without selecting e.g. any
flavor, which would need additional handling on the server side.

Add towncrier newsfragment

Regex quantifier should be lazy to make port separation work.

1788: Fix bug #1660 (don't replace nested headers) (bp #1785) r=mergify[bot] a=mergify[bot]

This is an automatic backport of pull request #1785 done by [Mergify](https://mergify.io).

---


<details>
<summary>Mergify commands and options</summary>

<br />

More conditions and actions can be found in the [documentation](https://docs.mergify.io/).

You can also trigger Mergify actions by commenting on this pull request:

- `@Mergifyio refresh` will re-evaluate the rules
- `@Mergifyio rebase` will rebase this PR on its base branch
- `@Mergifyio update` will merge the base branch into this PR
- `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch

Additionally, on Mergify [dashboard](https://dashboard.mergify.io/) you can:

- look at your merge queues
- generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/


</details>
Co-authored-by: Florent Daigniere <nextgens@freenetproject.org>

(cherry picked from commit 97be7359fe1d2de4fcf9022325dcb66b387999c2)

(cherry picked from commit 513d2a4c5ef6930fe4d6f6e7371039233227dfb5)

1782: Set sensible cookie flags on the admin app (bp #1765) r=mergify[bot] a=mergify[bot]

This is an automatic backport of pull request #1765 done by [Mergify](https://mergify.io).

---


<details>
<summary>Mergify commands and options</summary>

<br />

More conditions and actions can be found in the [documentation](https://docs.mergify.io/).

You can also trigger Mergify actions by commenting on this pull request:

- `@Mergifyio refresh` will re-evaluate the rules
- `@Mergifyio rebase` will rebase this PR on its base branch
- `@Mergifyio update` will merge the base branch into this PR
- `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch

Additionally, on Mergify [dashboard](https://dashboard.mergify.io/) you can:

- look at your merge queues
- generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/


</details>
Co-authored-by: Florent Daigniere <nextgens@freenetproject.org>

1781: show flash messages again (bp #1763) r=mergify[bot] a=mergify[bot]

This is an automatic backport of pull request #1763 done by [Mergify](https://mergify.io).

---


<details>
<summary>Mergify commands and options</summary>

<br />

More conditions and actions can be found in the [documentation](https://docs.mergify.io/).

You can also trigger Mergify actions by commenting on this pull request:

- `@Mergifyio refresh` will re-evaluate the rules
- `@Mergifyio rebase` will rebase this PR on its base branch
- `@Mergifyio update` will merge the base branch into this PR
- `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch

Additionally, on Mergify [dashboard](https://dashboard.mergify.io/) you can:

- look at your merge queues
- generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/


</details>
Co-authored-by: lub <git@lubiland.de>

(cherry picked from commit 0dcc059cd6950422588a694c3727a443cf56feab)

(cherry picked from commit aa8cb9890693b1563cb873df79d50a2fab6230e3)

This basically restores the behaviour, that got removed in
ecdf0c25 during refactoring.

(cherry picked from commit 88f992de16ff6273b345136a0dca068c33cea9cc)

1768: Remove "CHUNKING" capability from nginx-smtp (bp #1767) r=ofthesun9 a=mergify[bot]

This is an automatic backport of pull request #1767 done by [Mergify](https://mergify.io).

---


<details>
<summary>Mergify commands and options</summary>

<br />

More conditions and actions can be found in the [documentation](https://docs.mergify.io/).

You can also trigger Mergify actions by commenting on this pull request:

- `@Mergifyio refresh` will re-evaluate the rules
- `@Mergifyio rebase` will rebase this PR on its base branch
- `@Mergifyio update` will merge the base branch into this PR
- `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch

Additionally, on Mergify [dashboard](https://dashboard.mergify.io/) you can:

- look at your merge queues
- generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/


</details>
Co-authored-by: Dario Ernst <dario@kanojo.de>

1771: For travis Ci: Need to docker login before pulling images (bp #1748) r=mergify[bot] a=mergify[bot]

This is an automatic backport of pull request #1748 done by [Mergify](https://mergify.io).

---


<details>
<summary>Mergify commands and options</summary>

<br />

More conditions and actions can be found in the [documentation](https://docs.mergify.io/).

You can also trigger Mergify actions by commenting on this pull request:

- `@Mergifyio refresh` will re-evaluate the rules
- `@Mergifyio rebase` will rebase this PR on its base branch
- `@Mergifyio update` will merge the base branch into this PR
- `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch

Additionally, on Mergify [dashboard](https://dashboard.mergify.io/) you can:

- look at your merge queues
- generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/


</details>
Co-authored-by: ofthesun9 <olivier@ofthesun.net>

(cherry picked from commit 788d069b5379b0ae86e5d955994e144cc4d246f8)

To avoid triggering the Download rate limite

(cherry picked from commit 612632e4fc7b498d8fb1fc714af1a02d0e1a1859)

With `CHUNKING`set as a capability, nginx advertises this capability to
clients at a stage where the SMTP dialog does not seem to be forwarded
to the proxy-target (postfix) yet. Nginx' SMTP parser itself does not
support the `BDAT` command issued as part of a chunke-d dialog. This makes
Nginx respond with a `250 2.0.0 OK` and close the connection, after the
mail-data got sent by the client — without forwarding this to the
proxy-target.

With this, users mail can be lost.

Furthermore, when a user uses a sieve filter to forward mail, dovecot
sometimes chunks the forwarded mail when sending it through `front`.
These forwards then fail.

Removing `CHUNKING` from the capabilities fixes this behavior.

(cherry picked from commit b6716f0d74681919384733414b8ca93c0dbf3dca)

1688: Fix letsencrypt access to certbot for the mail-letsencrypt flavour (bp #1687) r=mergify[bot] a=mergify[bot]

This is an automated backport of pull request #1687 done by Mergify
---


<details>
<summary>Mergify commands and options</summary>

<br />

More conditions and actions can be found in the [documentation](https://docs.mergify.io/).

You can also trigger Mergify actions by commenting on this pull request:

- `@Mergifyio refresh` will re-evaluate the rules
- `@Mergifyio rebase` will rebase this PR on its base branch
- `@Mergifyio update` will merge the base branch into this PR
- `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch

Additionally, on Mergify [dashboard](https://dashboard.mergify.io/) you can:

- look at your merge queues
- generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/


</details>
Co-authored-by: ofthesun9 <olivier@ofthesun.net>

1708: Bump cryptography from 2.6.1 to 3.2 in /core/admin (bp #1693) r=mergify[bot] a=mergify[bot]

This is an automated backport of pull request #1693 done by Mergify
---


<details>
<summary>Mergify commands and options</summary>

<br />

More conditions and actions can be found in the [documentation](https://docs.mergify.io/).

You can also trigger Mergify actions by commenting on this pull request:

- `@Mergifyio refresh` will re-evaluate the rules
- `@Mergifyio rebase` will rebase this PR on its base branch
- `@Mergifyio update` will merge the base branch into this PR
- `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch

Additionally, on Mergify [dashboard](https://dashboard.mergify.io/) you can:

- look at your merge queues
- generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/


</details>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>