Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker MTA #7921

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Docker MTA #7921

wants to merge 2 commits into from

Conversation

buchi
Copy link
Member

@buchi buchi commented Apr 1, 2024

Provide MTA container for handling mail. Handles incoming and outgoing mail with Postfix.
This is meant for setups where we deploy only containers and replaces the functionality provided by Postfix installed on the host.

Additionaly the mail host can now be configured through the follwing environment variables:

- SMTP_HOST
- SMTP_PORT
- SMTP_USER
- SMTP_PASSWORD
- SMTP_FORCE_TLS
- SMTP_NO_TLS

For [CA-XXXX]

Checklist

Everything has to be done/checked. Checked but not present means the author deemed it unnecessary.

  • Changelog entry
  • Link to issue (Jira or GitHub) and backlink in issue (Jira)

Only applicable should be left and checked.

  • Upgrade-Steps:
    • SQL Operations do not use imported model (see docs)
    • Make it deferrable if possible
    • Execute as much as possible conditionally
    • DB-Schema migration
      • All changes on a model (columns, etc) are included in a DB-schema migration.
      • Constraint names are shorter than 30 characters (Oracle)
  • API change:
    • Documentation is updated
    • API Changelog entry (see guide)
    • If breaking:
      • api-change label added
      • #delivery channel notified about breaking change
      • Scrum master is informed
  • Bug fixed:
    • Resolved any Sentry issues caused by this bug
  • New functionality:
    • for document also works for mail
    • for task also works for forwarding
  • Further improvements needed:
    • Create follow-up stories and link them in the PR and Jira issue
  • Change could impact client installations, client policies need to be adapted
  • New translations
    • All msg-strings are unicode
  • Change in schema definition:
    • If missing_value is specified, then default has to be set to the same value

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant