1639: Add FAQ entry for how to use webdav(radicale) r=mergify[bot] a=Diman0
## What type of PR?
documentation
## What does this PR do?
Add faq entry for how to use webdav (radicale).
### Related issue(s)
- Auto close an issue like: closes#1591
## Prerequistes
Before we can consider review and merge, please make sure the following list is done and checked.
If an entry in not applicable, you can check it or remove it from the list.
- [x] In case of feature or enhancement: documentation updated accordingly
- [n/a] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/guide.html#changelog) entry file.
Co-authored-by: Dimitri Huisman <diman@huisman.xyz>
1611: Adds own server on port 80 for letsencrypt and redirect r=mergify[bot] a=elektro-wolle
## What type of PR?
Bugfix
## What does this PR do?
Handle letsencrypt route to `.well-known` by own server configuration within nginx.
### Related issue(s)
closes#1564
## Prerequistes
Before we can consider review and merge, please make sure the following list is done and checked.
If an entry in not applicable, you can check it or remove it from the list.
- [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/guide.html#changelog) entry file.
Co-authored-by: Wolfgang Jung <w.jung@polyas.de>
1640: Update stale.yml r=mergify[bot] a=Diman0
Add label backlog to exempt labels in stale.yml. We will use label backlog to collect bugs/features that we want to consider for a future release. Thus we do not want to auto-close those issues.
Co-authored-by: Dimitri Huisman <52963853+Diman0@users.noreply.github.com>
Add label backlog to exempt labels. We will use label backlog to collect bugs/features that we want to consider for a future release. Thus we do not want to auto-close those issues.
1635: Add support for AUTH LOGIN authentication mechanism for relaying emai… r=mergify[bot] a=Diman0
…l via smart hosts.
## What type of PR?
Feature
## What does this PR do?
This PR adds support to postfix for AUTH LOGIN authentication mechanism. This enables using smart hosts which only offer AUTH LOGIN.
### Related issue(s)
- Auto close an issue like: closes#1633
## Prerequistes
Before we can consider review and merge, please make sure the following list is done and checked.
If an entry in not applicable, you can check it or remove it from the list.
- [n/a] In case of feature or enhancement: documentation updated accordingly
- [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/guide.html#changelog) entry file.
Co-authored-by: Dimitri Huisman <diman@huisman.xyz>
1613: Add warnings about Dockers IPv6 solution r=mergify[bot] a=Simonmicro
## What type of PR?
enhancement
## What does this PR do?
Added some warnings and explanations about the current Docker ipv6 situation as suggested in https://github.com/Mailu/Mailu/issues/1578.
### Related issue(s)
closes#1578
## Prerequistes
- [x] In case of feature or enhancement: documentation updated accordingly
- [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/guide.html#changelog) entry file.
1617: relax TLS settings on port 25 r=mergify[bot] a=lub
Because basically every MTA out there uses opportunistic TLS _in
the best case_, it's actually counter productive to use such strict
settings.
The alternative to a handshake error is often an unencrypted submission,
which is basically the opposite of what strict ssl_protocols and
ssl_ciphers tries to achieve.
Even big and established providers like Amazon SES are incompatible with the current
settings.
This reverts commit 2ddf46ad2b.
## What type of PR?
bug-fix
## What does this PR do?
### Related issue(s)
- this reverts #1398
- the settings in this PR were initially introduced in #1321 and intentionally divert from tls.conf
cc @bladeswords as they introduced the current config
1636: Add config file for the "stale" robot to clean up issues r=mergify[bot] a=Nebukadneza
## What type of PR?
enhancement
## What does this PR do?
With this, and the already activated github-app, the stale robot will
mark and subsequently close issues as specified in the config.
Currently we mark after 21 days, close after 7 more days, and ignore
issues with an assigned priority or milestone.
### Related issue(s)
Related: #1582
## Prerequistes
- No: In case of feature or enhancement: documentation updated accordingly
- No: Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/guide.html#changelog) entry file.
Co-authored-by: Simonmicro <simon@simonmicro.de>
Co-authored-by: lub <git@lubiland.de>
Co-authored-by: Dario Ernst <dario.ernst@rommelag.com>
1629: Add mergify team-members r=Nebukadneza a=Nebukadneza
## What type of PR?
enhancement
## What does this PR do?
Sync the newly added team-members to the mergify team-regex so that they will benefit from the "team needs only one approve" rule
### Related issue(s)
## Prerequistes
- [x] In case of feature or enhancement: documentation updated accordingly
- [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/guide.html#changelog) entry file.
Co-authored-by: Dario Ernst <dario.ernst@rommelag.com>
With this, and the already activated github-app, the stale robot will
mark and subsequently close issues as specified in the config.
Currently we mark after 21 days, close after 7 more days, and ignore
issues with an assigned priority or milestone.
1615: Create ISSUE_TEMPLATE.md r=Nebukadneza a=Diman0
Add bug template to be used for reporting issues.
## What type of PR?
Feature?
## What does this PR do?
Add bug template which we will use to get better quality bug reports.
### Related issue(s)
- Auto close an issue like: closes#1331
## Prerequistes
Before we can consider review and merge, please make sure the following list is done and checked.
If an entry in not applicable, you can check it or remove it from the list.
- [N/A] In case of feature or enhancement: documentation updated accordingly
- [N/A] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/guide.html#changelog) entry file.
Co-authored-by: Dimitri Huisman <52963853+Diman0@users.noreply.github.com>
Co-authored-by: Dario Ernst <dario@kanojo.de>
Because basically every MTA out there uses opportunistic TLS _in
the best case_, it's actually counter productive to use such strict
settings.
The alternative to a handshake error is often an unencrypted submission,
which is basically the opposite of what strict ssl_protocols and
ssl_ciphers tries to achieve.
Even big and established providers like Amazon SES are incompatible with the current
settings.
This reverts commit 2ddf46ad2b.
this enables usage of e.g. docker swarm secrets instead of exposing the
passwords directly via environment variables
just use DB_PW_FILE and SECRET_KEY_FILE instead of DB_PW and SECRET_KEY
Dario Ernst
lub