ꦫꦣꦺꦤ꧀ꦄꦤ꧀ꦠꦱꦺꦤ

PATH: home / centosnipponia / public_html / ticketing.nipponia.com / include / i18n / zh_CN / help / tips

#This is popup help messages for the Admin Panel -> Emails -> Add New Email
#Fields:
#title - Shown in bold at the top of the popover window
#content - The body of the help popover
#links - List of links shows below the content
#title - Link title
#href - href of link (links starting with / are translated to the
#helpdesk installation path)
#The key names such as 'helpdesk_name' should not be translated as they
#must match the HTML #ids put into the page template.
---
new_ticket_help_topic:
 title: 新咨询帮助主题
 content: >
 选择自动与通过此电子邮件地址创建的咨询相关联的帮助主题。 与帮助主题相关联的表单将添加至咨询，但没有任何数据。
 links:
 - 
 title: 管理帮助主题
 href: /scp/helptopics.php
new_ticket_priority:
 title: 新咨询优先级
 content: >
 选择通过此电子邮件地址创建新咨询的优先级。
new_ticket_department:
 title: 新咨询部门
 content: >
 选择通过此电子邮件地址创建新咨询，并将其发送至的部门。
 links:
 - 
 title: 管理部门
 href: /scp/departments.php
auto_response:
 title: 新咨询自动回复
 content: >
 您可在通过此电子邮件地址创建新咨询时禁用发送至用户的自动回复。
userid:
 title: 用户名
 content: >
 The Username is utilized in the email authentication process. We accept single address strings, shared mailbox strings, servername + username strings, and a combination of all.
 links:
 - 
 title: 更多信息
 href: https://docs.osticket.com/en/latest/Admin/Emails/Emails.html
username:
 title: 用户名
 content: >

password:
  title: 密码
  content: >

login_information:
 title: 电子邮件登录信息
 content: >
 从 IMAP / POP 邮箱中获取电子邮件以及通过 SMTP 发送电子邮件需要的用户名和密码。
mail_account:
 title: 正在获取电子邮件
 content: >
 从远程 IMAP 或 POP 邮件中获取电子邮件并将其转换至帮助中心中的咨询。
 links:
 - 
 title: 管理电子邮件轮询 &amp; 自动执行计划任务设置。
 href: /scp/settings.php?t=emails
host_and_port:
 title: 远程主机
 content: >
 Enter the hostname and port number for your mail server. This may be available in the documentation for your hosting account or from your email administrator. If using non-standard port number with encryption enabled then prefix the hostname with ssl:// or tls:// scheme to hint to supported encryption. To force a plain connection even when using a standard encryption port then use plain:// scheme.
mailbox_folder:
 title: Mail Folder
 content: >
 Enter the Folder name that you wish to fetch mail from. If left empty the system will fetch from the INBOX.
protocol:
 title: 邮箱协议
 content: >
 Select the mail box protocol supported by your remote mail server. IMAP on a secure port highly recommended.
authentication:
 title: 身份验证
 content: >
 osTicket OAuth2 Plugin is required for Modern Authentication support.
 links:
 - 
 title: Download osTicket Plugins
 href: https://osticket.com/download/
fetch_frequency:
 title: 获取频率
 content: >
 输入系统轮询邮箱的频率（以分钟为计量单位）。 这将定义用户发送电子邮件至此邮箱后接受自动回复的平均延迟。
emails_per_fetch:
 title: 每次获取电子邮件数
 content: >
 一次性输入处理的电子邮件数。
fetched_emails:
 title: 已获取电子邮件
 content: >
 确定已处理电子邮件的步骤： 移动至文件夹：这可将电子邮件从收件箱备份至您指定的文件夹。如果文件夹不存在，系统将尝试自动创建。（推荐）<hr> 删除邮件：执行此操作将在处理后删除您收件箱中的电子邮件。<hr> 不执行任何操作：该操作可将电子邮件保留在您的收件箱中。系统将记录您的电子邮件消息 ID 并尝试不重新进行获取。但是，此选项可能导致重复创建咨询。（不推荐）
smtp_settings:
 title: SMTP 设置
 content: >
 可通过 SMTP 服务器发送从帮助中心发出的电子邮件。如有可能，推荐执行上述操作。同时，此操作将增加电子邮件发送几率并降低其被标记为垃圾邮件的几率。
header_spoofing:
 title: 允许标题欺骗
 content: >
 启用此功能，即可允许邮箱通过与上述电子邮件地址设置给出的不同地址发送电子邮件。 从此邮箱别名发送电子邮件时通常使用此高级设置。
strict_matching:
 title: Strict Email Matching
 content: >
 Enable this option to require the Email Address and the Token's Resource Owner to match. This is useful for preventing accidental authorization of a completely different account. Disable this option to allow a different Resource Owner for the Token than the Email Address. This is useful for Shared Mailboxes/Aliases/etc. where you need to use a Service Account or Global Admin to authorize on behalf of the email.

[+] ..
[-] manage.helptopic.yaml [edit]
[-] install.yaml [edit]
[-] tickets.queue.yaml [edit]
[-] emails.banlist.yaml [edit]
[-] settings.tasks.yaml [edit]
[-] settings.users.yaml [edit]
[-] dashboard.my_profile.yaml [edit]
[-] staff.departments.yaml [edit]
[-] emails.diagnostic.yaml [edit]
[-] org.yaml [edit]
[-] forms.yaml [edit]
[-] staff.yaml [edit]
[-] settings.kb.yaml [edit]
[-] staff.agents.yaml [edit]
[-] staff.team.yaml [edit]
[-] staff.agent.yaml [edit]
[-] settings.autoresponder.yaml [edit]
[-] staff.staff_members.yaml [edit]
[-] knowledgebase.category.yaml [edit]
[-] settings.agents.yaml [edit]
[-] settings.alerts.yaml [edit]
[-] manage.custom_list.yaml [edit]
[-] emails.email.yaml [edit]
[-] dashboard.audit_logs.yaml [edit]
[-] staff.department.yaml [edit]
[-] manage.api_keys.yaml [edit]
[-] manage.pages.yaml [edit]
[-] dashboard.dashboard.yaml [edit]
[-] dashboard.system_logs.yaml [edit]
[-] tasks.queue.yaml [edit]
[-] settings.ticket.yaml [edit]
[-] knowledgebase.canned_response.yaml [edit]
[-] manage.sla.yaml [edit]
[-] settings.pages.yaml [edit]
[-] emails.template.yaml [edit]
[-] settings.email.yaml [edit]
[-] staff.groups.yaml [edit]
[-] knowledgebase.faq.yaml [edit]
[-] dashboard.staff_directory.yaml [edit]
[-] manage.schedule.yaml [edit]
[-] settings.system.yaml [edit]
[-] manage.filter.yaml [edit]