Problem / Motivation
Currently, when creating a user in Stalwart, we can define a specific "Locale" (e.g., Turkish) and "Time Zone" for the account. However, Bulwark Webmail does not seem to respect these settings upon the first login. Instead, it defaults to English, ignoring the predefined user preferences in the Stalwart backend.
Proposed Solution
Bulwark should ideally fetch and apply the user's locale and time zone settings directly from Stalwart during the initial session establishment. If Bulwark already supports the language defined in the user's Stalwart profile, the interface should automatically switch to that language to provide a seamless localized experience from the start.
Alternatives Considered
The only alternative currently is for users to manually change their language and time zone settings in the Bulwark settings menu after their first login, which is not ideal for localized deployments.
Feature Area
Internationalization
Mockups / Examples
I have attached a screenshot showing the locale and time zone configuration within the Stalwart admin interface. Bulwark should listen to these specific values:
Additional Context
This improvement would greatly benefit administrators managing multi-language environments, ensuring that users are greeted in their preferred language immediately after their account is created.
Problem / Motivation
Currently, when creating a user in Stalwart, we can define a specific "Locale" (e.g., Turkish) and "Time Zone" for the account. However, Bulwark Webmail does not seem to respect these settings upon the first login. Instead, it defaults to English, ignoring the predefined user preferences in the Stalwart backend.
Proposed Solution
Bulwark should ideally fetch and apply the user's locale and time zone settings directly from Stalwart during the initial session establishment. If Bulwark already supports the language defined in the user's Stalwart profile, the interface should automatically switch to that language to provide a seamless localized experience from the start.
Alternatives Considered
The only alternative currently is for users to manually change their language and time zone settings in the Bulwark settings menu after their first login, which is not ideal for localized deployments.
Feature Area
Internationalization
Mockups / Examples
I have attached a screenshot showing the locale and time zone configuration within the Stalwart admin interface. Bulwark should listen to these specific values:
Additional Context
This improvement would greatly benefit administrators managing multi-language environments, ensuring that users are greeted in their preferred language immediately after their account is created.