mirror of
https://github.com/mailcow/mailcow-dockerized.git
synced 2025-12-13 01:45:59 +00:00
[Web] Updated lang.zh-cn.json (#6552)
Co-authored-by: Easton Man <me@eastonman.com>
This commit is contained in:
@@ -390,7 +390,7 @@
|
||||
"iam_username_field": "Username 域",
|
||||
"iam_binddn": "Bind DN",
|
||||
"iam_use_ssl": "使用 SSL",
|
||||
"iam_use_tls": "使用 TLS",
|
||||
"iam_use_tls": "使用 StartTLS",
|
||||
"iam_version": "版本",
|
||||
"ignore_ssl_error": "忽略 SSL 错误",
|
||||
"iam_auth_flow_info": "除了在单点登录(SSO)中使用的 Authorization Code 流程(在 Keycloak 中是标准流程)之外,mailcow 还支持使用 Credentials 的身份认证流程。Mailpassword 流程尝试通过 Keycloak 的 Admin REST API 验证用户凭据,mailcow 会从 Keycloak 中的 <code>mailcow_password</code> 属性中获取哈希后的密码。",
|
||||
@@ -404,7 +404,8 @@
|
||||
"quicklink_text": "显示或隐藏登陆表单下面指向其他登陆页面的快捷链接",
|
||||
"user_quicklink": "隐藏指向用户登陆页面的快捷链接",
|
||||
"admin_quicklink": "隐藏指向管理员登陆页面的快捷链接",
|
||||
"force_sso": "强制要求单点登录(SSO)"
|
||||
"force_sso": "强制要求单点登录(SSO)",
|
||||
"user_link": "自定义链接"
|
||||
},
|
||||
"danger": {
|
||||
"access_denied": "访问被拒绝或者表单数据无效",
|
||||
@@ -690,7 +691,7 @@
|
||||
"sieve_desc": "简短描述",
|
||||
"sieve_type": "过滤器类型",
|
||||
"skipcrossduplicates": "跳过其他文件夹中已存在的邮件(保留已经存在的邮件)",
|
||||
"sogo_access": "直接转发给 SOGo",
|
||||
"sogo_access": "直接转到 SOGo",
|
||||
"sogo_access_info": "登录后,用户会自动跳转到 SOGo。",
|
||||
"sogo_visible": "SOGo 显示的别名",
|
||||
"sogo_visible_info": "此设置只影响 SOGo 上可显示的对象 (指向本地邮箱的共享或非共享别名地址)。如果设置为隐藏,则别名地址不会作为可选发件人的下拉项显示。",
|
||||
@@ -905,7 +906,7 @@
|
||||
"recipient_map": "收件人映射",
|
||||
"recipient_map_info": "收件人映射用于在邮件被发送前替换收件人的地址。",
|
||||
"recipient_map_new": "新收件人",
|
||||
"recipient_map_new_info": "新收件人必须为合法的邮箱地址。",
|
||||
"recipient_map_new_info": "收件人映射的目标必须为合法的邮件地址或域名。",
|
||||
"recipient_map_old": "原收件人",
|
||||
"recipient_map_old_info": "原收件人必须为合法的邮箱地址。",
|
||||
"recipient_maps": "收件人映射",
|
||||
|
||||
Reference in New Issue
Block a user