Allow to set the encryption method for IMAP access for bounce mail processing
What does this MR do?
Introduce the configuration variable BOUNCE_IMAP_SERVICE_OPTION
for bounce mail processing. This makes it possible to change Server configuration without changing the Sourcecode.
How confident are you it won't break things if deployed?
Should only break bounce mail processing, what would lead to annoying mails for me but no impact for users. Needs to be merged before the next release otherwise the bounce mail processing will not work anymore
Links to related issues
https://yunity.slack.com/archives/C1T1ZM9A4/p1659427513549549
How to test
? Only in Prod possible and I changed the sourcecode manually there
Checklist
- [N] added a test, or explain why one is not needed/possible...
- [Y] no unrelated changes
- [?] asked someone for a code review
- [Y] set a "for:" label to indicate who will be affected by this change
- [Y] added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label)
- [N] added an entry to
CHANGELOG.md
- [N] added a short text that can be used in the release notes
- [N] Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
- Consider writing a detailed description in German.
- Describe in a few sentences, what should be tested from a user perspective.
- Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
- Be aware, that also non technical people should understand.