2494: Improve ISSUE_TEMPLATE.md r=mergify[bot] a=ghostwheel42
## What type of PR?
documentation
## What does this PR do?
I'm having trouble separating the user input from the instructions in the issue template.
This puts the instructions in comments so the rendered markdown is almost empty.
Co-authored-by: Alexander Graf <ghostwheel42@users.noreply.github.com>
2486: Quote SMTP SIZE to avoid splitting keyword and parameter in EHLO response r=mergify[bot] a=TheBeeZee
## What type of PR?
bug-fix
## What does this PR do?
Fixes a syntax issue in the nginx front EHLO response. As currently configured, the SIZE parameter and value are treated as separate keywords and as a result are returned on separate lines in an EHLO response:
```
...
250-SIZE
250-50000000
...
```
By adding quotes, nginx will return the correct response on a single line:
```
...
250-SIZE 50000000
...
```
### Related issue(s)
closes#2485
## Prerequisites
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
- [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/workflow.html#changelog) entry file.
Co-authored-by: Blaž Zupan <blaz@inlimbo.org>
2480: Fix a bunch of typos r=mergify[bot] a=DjVinnii
## What type of PR?
documentation
## What does this PR do?
Fix a bunch of typos in a variety of files
### Related issue(s)
- None
## Prerequisites
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
- [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/workflow.html#changelog) entry file.
Co-authored-by: Vincent Kling <v.kling@vinniict.nl>
Build base image before the other images.
Change cache key to make it is re-used for all builds. This is not
dangerous. The docker build process can determine itself whether
a cache can be safely re-used or not.
Vincent Kling