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

I18N for automatic messages (bounces) #841

Open
7 tasks
chibenwa opened this issue Oct 5, 2023 · 0 comments
Open
7 tasks

I18N for automatic messages (bounces) #841

chibenwa opened this issue Oct 5, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@chibenwa
Copy link
Member

chibenwa commented Oct 5, 2023

Why?

Today TeamMail generates bounces in english. Regardless of the "locale" of the recipient.

Those bounces includes:

  • Over quota
  • Recipient do not exist
  • Unspecified Error
  • Relay denied
  • Size exceeded
  • Impossible to relay
  • RRT error
  • Virus

How?

(Ideally do not recreate the wheel and do not re-implement the wheel, ie do not re-implement Bounce)

  • In Apache James define an API that given a mail provides all text part to assemble for assembling a Bounce / DSNBounce message
  • Do a default, static implementation that does today behaviour (no breaking change)
  • In TMail provide an implementation of this interface:
    • Use the Accept-Language header and fallback to the Content-Language header to determine user locale.
    • Use a template engine (moustache) with per-locale predefined templates
    • Use configuration to supply one message per locale
  • Update tmail configuration to adopt this i18n in all deployments

Supported locale: en, fr, vn, ru, ar

Related

Position Content-Language and Accept-Language on frontend side: linagora/tmail-flutter#2215

This makes this approach compliant with: tmail, thunderbird, office365 at least, likely more.

@chibenwa chibenwa added the enhancement New feature or request label Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant