[I18N] *: export translations
closes odoo/documentation#6078
X-original-commit: a2bbd060ed
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux
+478
-166
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo saas-16.1\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2023-09-14 05:10+0000\n"
|
||||
"POT-Creation-Date: 2023-10-10 06:13+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@@ -1604,331 +1604,643 @@ msgid "In addition, when email is received to the catchall email address, Odoo w
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:3
|
||||
msgid "Email Templates"
|
||||
msgid "Email templates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:5
|
||||
msgid "We all know writing good emails is vital to get a high response rate, but you do not want to rewrite the same structure every time, do you? That is where email templates come in. Without the need to rewrite the entire email structure every time, you save time to focus on the content. Multiple templates also let you deliver the right message to the right audience, improving their overall experience with the company."
|
||||
msgid "Email templates are saved emails that are used repeatedly to send emails from the database. They allow users to send quality communications, without having to compose the same text repeatedly."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:12
|
||||
msgid "The email templates use QWeb. The composer allows you to edit emails in their final rendering, making customizations more robust as you don’t have to edit code."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:8
|
||||
msgid "Creating different templates that are tailored to specific situations lets users choose the right message for the right audience. This increases the quality of the message and the overall engagement rate with the customer."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:16
|
||||
msgid "Defining a default reply to on your mail template"
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:13
|
||||
msgid "Email templates in Odoo use QWeb or XML, which allows for editing emails in their final rendering, making customizations more robust, without having to edit any code whatsoever. This means that Odoo can use a Graphical User Interface (GUI) to edit emails, which edits the backend code. When the received email is read by the end user's program, different formatting an graphics will appear in the final form of it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:18
|
||||
msgid "Although the field *reply to* is available within the mail templates, **this field is only used for mass mailing** mode (this means when sending templates on what we call bulk emailing). You can send emails in bulk in almost every app that has a list view. Select the records you want and click on the action button. If you have an option to send an email, you will see a mail composer with possible values to define:"
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:19
|
||||
msgid "Access email templates in :ref:`developer mode <developer-mode>` by navigating to :menuselection:`Settings app --> Technical menu --> Email --> Email Templates`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:23
|
||||
msgid "Editing email templates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:25
|
||||
msgid "The *powerbox* feature can be used when working with email templates. This feature provides the ability to directly edit the formatting and text in an email template, as well as the ability to add links, buttons, appointment options, or images."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:29
|
||||
msgid "Additionally, the XML/HTML code of the email template can be edited directly, via the :guilabel:`</>` icon. Dynamic placeholders (referencing fields within Odoo) are also available for use in the email template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:34
|
||||
msgid "Powerbox"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:36
|
||||
msgid "The *powerbox* feature is an enriched text editor with various formatting, layout, and text options. It can also be used to add XML/HTML features in an email template. The powerbox feature is activated by typing a forward slash `/` in the body of the email template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:40
|
||||
msgid "When a forward slash `/` is typed in the body of an email template, a drop-down menu appears with the following options:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:43
|
||||
msgid ":guilabel:`Structure`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:45
|
||||
msgid ":guilabel:`Bulleted list`: Create a simple bulleted list."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:46
|
||||
msgid ":guilabel:`Numbered list`: Create a list with numbering."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:47
|
||||
msgid ":guilabel:`Checklist`: Track tasks with a checklist."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:48
|
||||
msgid ":guilabel:`Table`: Insert a table."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:49
|
||||
msgid ":guilabel:`Separator`: Insert a horizontal rule separator."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:50
|
||||
msgid ":guilabel:`Quote`: Add a blockquote section."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:51
|
||||
msgid ":guilabel:`Code`: Add a code section."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:52
|
||||
msgid ":guilabel:`2 columns`: Convert into two columns."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:53
|
||||
msgid ":guilabel:`3 columns`: Convert into three columns."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:54
|
||||
msgid ":guilabel:`4 columns`: Convert into four columns."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:56
|
||||
msgid ":guilabel:`Format`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:58
|
||||
msgid ":guilabel:`Heading 1`: Big section heading."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:59
|
||||
msgid ":guilabel:`Heading 2`: Medium section heading."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:60
|
||||
msgid ":guilabel:`Heading 3`: Small section heading."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:61
|
||||
msgid ":guilabel:`Switch direction`: Switch the text's direction."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:62
|
||||
msgid ":guilabel:`Text`: Paragraph block."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:64
|
||||
msgid ":guilabel:`Media`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:66
|
||||
msgid ":guilabel:`Image`: Insert an image."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:67
|
||||
msgid ":guilabel:`Article`: Link an article."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:69
|
||||
msgid ":guilabel:`Navigation`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:71
|
||||
msgid ":guilabel:`Link`: Add a link."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:72
|
||||
msgid ":guilabel:`Button`: Add a button."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:73
|
||||
msgid ":guilabel:`Appointment`: Add a specific appointment."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:74
|
||||
msgid ":guilabel:`Calendar`: Schedule an appointment."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:76
|
||||
msgid ":guilabel:`Widgets`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:78
|
||||
msgid ":guilabel:`3 Stars`: Insert a rating over three stars."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:79
|
||||
msgid ":guilabel:`5 Stars`: Insert a rating over five stars."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:81
|
||||
msgid ":guilabel:`Basic Blocks`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:83
|
||||
msgid ":guilabel:`Signature`: Insert your signature."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:85
|
||||
msgid ":guilabel:`Marketing Tools`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:87
|
||||
msgid ":guilabel:`Dynamic Placeholders`: Insert personalized content."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:90
|
||||
msgid "To use any of these options, click on the desired feature from the powerbox drop-down menu. To format existing text with a text-related option (e.g. :guilabel:`Heading 1`, :guilabel:`Switch direction`, etc.), highlight the text, then type in the activator key (forward slash) `/`, and select the desired option from the drop-down menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:0
|
||||
msgid "Powerbox feature in the email template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:100
|
||||
msgid ":ref:`Using dynamic placeholders <email_template/dynamic-placeholders>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:103
|
||||
msgid "XML/HTML code editor"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:105
|
||||
msgid "To access the XML/HTML editor for an email template, first enter :ref:`developer mode <developer-mode>`. Then, click the :guilabel:`</>` icon in the upper-right corner of the template, and proceed to edit the XML/HTML. To return to the standard text editor, click the :guilabel:`</>` icon again."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:-1
|
||||
msgid "Composer in mass mailing mode after selecting multiple quotations."
|
||||
msgid "HTML editor in the email template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:28
|
||||
msgid "You can also define them by default on the template:"
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:115
|
||||
msgid "The XML/HTML editor should be accessed with caution as this is the backend code of the template. Editing the code can cause the email template to break immediately or when upgrading the database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:122
|
||||
msgid "Dynamic placeholders"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:124
|
||||
msgid "*Dynamic placeholders* reference certain fields within the Odoo database to produce unique data in the email template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:128
|
||||
msgid "Many companies like to customize their emails with a personalized piece of customer information to grab attention. This can be accomplished in Odoo by referencing a field within a model by inserting a dynamic placeholder. For example, a customer's name can be referenced in the email from the :guilabel:`Customer` field on the :guilabel:`Sales Order` model. The dynamic placeholder for this field is: `{{ object.partner_id }}`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:134
|
||||
msgid "Dynamic placeholders are encoded to display fields from within the database. Dynamic placeholders can be used in the :guilabel:`Body` (:guilabel:`Content` Tab) of the email template. They can also be used in the fields present in the :guilabel:`Email Configuration` tab, the :guilabel:`Subject` of the email, and the :guilabel:`Language`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:139
|
||||
msgid "To use the dynamic placeholders in the :guilabel:`Body` of an email open the **powerbox** feature by typing in `/` into the body of the email template under the :guilabel:`Content` tab. Scroll to the bottom of the options list, to :guilabel:`Marketing Tools`. Next, select :guilabel:`Dynamic Placeholder`. Then select the dynamic placeholder from a list of available options and follow the prompts to configure it with the desired corresponding Odoo field. Each dynamic placeholder will vary in configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:-1
|
||||
msgid "Using dynamic placeholders in an email template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:151
|
||||
msgid "Each unique combination of :guilabel:`Fields`, :guilabel:`Sub-models` and :guilabel:`Sub-fields` creates a different dynamic placeholder. Imagine it as a combination to the field that is being created."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:155
|
||||
msgid "To search the available fields, simply type in the front-end name (on user-interface) of the field in the search. This will find a result from all of the available fields for the model that the email template is created for."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:160
|
||||
msgid "Customizing email templates are out of the scope of Odoo Support."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:163
|
||||
msgid "Rich text editor"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:165
|
||||
msgid "A rich text editor toolbar can be accessed by highlighting text in the email template. This can be used to change the heading, font size/style, color, add a list type, or a link."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:-1
|
||||
msgid "Rich text editor in the email template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:173
|
||||
msgid "Resetting email templates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:175
|
||||
msgid "Should the email template not work because the code has been altered it can be reset to restore it back to the out-of-box default template. Simply click on the :guilabel:`Reset Template` button in the upper left-hand of the screen and the template will be reset."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:-1
|
||||
msgid "Resetting the email template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:184
|
||||
msgid "Default reply on email templates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:186
|
||||
msgid "Under the :guilabel:`Email Configuration` tab on an email template, there is a :guilabel:`Reply To` field. In this field, add email addresses to which replies are redirected when sending emails en masse using this template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:191
|
||||
msgid "Add multiple email addresses by adding a comma `,` between the addresses or dynamic placeholders."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:-1
|
||||
msgid "Reply-to field on template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:34
|
||||
msgid "Because of this, setting a value in this field is useless as the value defined will be totally ignored. The default *reply-to* value is the default catchall email address to ensure a communication between your customer and your Odoo database. For more information about the way the catchall works, please check :ref:`how to manage inbound messages <email_communication/inbound_messages>`."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:198
|
||||
msgid "The :guilabel:`Reply To` field is **only** used for mass mailing (sending emails in bulk). Bulk emails can be sent in almost every Odoo application that has a list view option."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:40
|
||||
msgid "Transactional emails and corresponding URL for each company"
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:201
|
||||
msgid "To send mass mails, while in :guilabel:`list` view, check the boxes next to the desired records where the emails are to be sent, click the :guilabel:`Action` button (represented by a :guilabel:`⚙️ (gear)` icon), and select the desired email option from the :guilabel:`Action` drop-down menu. Email options can vary by the particular list view and application."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:42
|
||||
msgid "When using Odoo, multiple events trigger the sending of automated emails. These emails are known as transactional emails and sometimes contain links pointing to your Odoo database."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:206
|
||||
msgid "If it is possible to send an email, a mail composer pop-up window appears, with values that can be defined and customized. This option will be available on the :guilabel:`Action` button on pages where emails can be sent in bulk---for example, on the :guilabel:`Customers` page of the CRM app. This action occurs throughout the Odoo database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:45
|
||||
msgid "By default, links generated by the database use the dynamic web.base.url key defined in the system parameters. More information about this :ref:`parameter <domain-name/web-base-url>`."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:-1
|
||||
msgid "Email composer in mass mailing mode with reply-to highlighted."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:48
|
||||
msgid "If the website application isn't installed, the web.base.url key will always be the default parameter used to generate all the links."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:216
|
||||
msgid "Transactional emails and corresponding URLs"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:51
|
||||
msgid "It’s important to know that this key can only have a single value, meaning that in a multi-website/company database environment, even if you have a specific domain name for each website, the links generated to share a document or within a transactional email might remain the same, whatever the website/company related to the sending of the email/document."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:218
|
||||
msgid "In Odoo, multiple events can trigger the sending of automated emails. These emails are known as *transactional emails*, and sometimes contain links redirecting to the Odoo database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:56
|
||||
msgid "This is not always the case as some Odoo applications have a link established in the database with the website application, meaning that in this case, if a specific domain is defined for the websites, the URL generated in the email template will use the domain defined on the corresponding website of the company."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:221
|
||||
msgid "By default, links generated by the database use the dynamic `web.base.url` key defined in the system parameters. For more information about this, see :ref:`system parameters <domain-name/web-base-url>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:62
|
||||
msgid "A document shared using the documents application will always use the web.base.url key, as the document shared isn't associated with any particular website. Meaning that the URL will always be the same (the web.base.url key value), whatever the company it's shared from, this is a known limitation!"
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:225
|
||||
msgid "If the *Website* application is not installed, the `web.base.url` key will always be the default parameter used to generate all the links."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:67
|
||||
msgid "On the other hand, sales orders made by a customer on one of your Odoo e-commerce websites have a link established with the website from which the order was made. As a result, the e-mail sent for the sales orders uses the domain name defined for the corresponding website to generate the links."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:229
|
||||
msgid "The `web.base.url` key can only have a single value, meaning that, in a multi-website or multi-company database environment, even if there is a specific domain name for each website, the links generated to share a document (or the links within a transactional email) may remain the same, regardless of which website/company is related to the sending of the email/document."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:71
|
||||
msgid "For more information about how to configure your domains, we invite you to check :doc:`our domain name documentation </administration/maintain/domain_names>`."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:235
|
||||
msgid "If the :guilabel:`Value` of the :guilabel:`web.base.url` system parameter is equal to `https://www.mycompany.com` and there are two separate companies in Odoo with different website URLs: `https://www.mycompany2.com` and `https://www.mycompany1.com`, the links created by Odoo to share a document, or send a transactional email, come from the domain: `https://www.mycompany.com`, regardless of which company sends the document or email."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:75
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:241
|
||||
msgid "This is not always the case, as some Odoo applications (*eCommerce*, for example) have a link established in the database with the *Website* application. In that case, if a specific domain is defined for the website, the URL generated in the email template uses the domain defined on the corresponding website of the company."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:247
|
||||
msgid "When a customer makes a purchase on an Odoo *eCommerce* website, the order has an established link with that website. As a result, the links in the confirmation email sent to the customer use the domain name for that specific website."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:252
|
||||
msgid "A document shared using the *Documents* application will **always** use the `web.base.url` key, as the document shared is not associated with any particular website. This means that the URL will always be the same (the `web.base.url` key value), no matter what company it's shared from. This is a known limitation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:257
|
||||
msgid "For more information about how to configure domains, check out the :doc:`domain name documentation </administration/maintain/domain_names>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:261
|
||||
msgid "Updating translations within email templates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:77
|
||||
msgid "Email templates are automatically translated. Changing the translations shouldn’t be necessary. However, if for a specific reason you’d like to change some of the translations, this can be done."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:263
|
||||
msgid "In Odoo, email templates are automatically translated for all users in the database for all of the languages installed. Changing the translations shouldn't be necessary. However, if for a specific reason, some of the translations need to be changed, it can be done."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:80
|
||||
msgid "Like any modification in the code, keep in mind that modifications that aren’t done correctly (for example modifications leading to bad syntax) can break the template, as a result, the template will appear blank."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:268
|
||||
msgid "Like any modification in the code, if translation changes are not done correctly (for example, modifications leading to bad syntax), it can break the template, and as a result, the template will appear blank."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:84
|
||||
msgid "In order to edit your translations, follow these steps from the template."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:272
|
||||
msgid "In order to edit translations, first enter :ref:`developer mode <developer-mode>`. Then, on the email template, click on the :guilabel:`Edit` button, and then click on the language button, represented by the initials of the language currently being used (e.g. :guilabel:`EN` for English)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:86
|
||||
msgid "Click on the edit button, then on the language button"
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:-1
|
||||
msgid "Edit the language of a template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:0
|
||||
msgid "Edit the language of a template"
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:281
|
||||
msgid "If there aren't multiple languages installed and activated in the database, or if the user does not have administration access rights, the language button will not appear."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:92
|
||||
msgid "A pop-up window with the different languages installed on the database will be displayed. From here, editing the translations will be possible. Don't forget to hit the save button to preserve your changes."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:284
|
||||
msgid "A pop-up window with the different languages installed on the database appears. From this pop-up, editing of translations is possible. When the desired changes have been made, click the :guilabel:`Save` button to save the changes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:0
|
||||
msgid "Translation of the body of the Application template in the different languages installed."
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:-1
|
||||
msgid "Translation of the body of the Appointment Booked template."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/email_template.rst:293
|
||||
msgid "When editing the translations, the default language set in the database appears in **bold**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:3
|
||||
msgid "FAQ"
|
||||
msgid "Email issues"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:5
|
||||
msgid "This document contains an explanation of the most recurring mailing concerns."
|
||||
msgid "This document contains an explanation of the most recurring emailing issues in Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:7
|
||||
msgid "We will start by addressing issues of outgoing emails (ex: my client has not received my email), and then, of incoming emails (ex: I do not receive responses from my customers in the database)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:11
|
||||
#: ../../content/applications/general/email_communication/faq.rst:8
|
||||
msgid "Outgoing emails"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:16
|
||||
msgid "What do you have to check if your email is not sent?"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:13
|
||||
msgid "Email is not sent"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:18
|
||||
msgid "The first indicator showing you that the email has not been sent is the red envelope next to the date and time of the message."
|
||||
#: ../../content/applications/general/email_communication/faq.rst:15
|
||||
msgid "The first indicator showing that an email has not been sent is the presence of a red :guilabel:`✉️ (envelope)` icon, next to the date and time of the message, located in the chatter."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:-1
|
||||
msgid "Red envelope displayed in chatter"
|
||||
msgid "Red envelope icon displayed in chatter."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:26
|
||||
#: ../../content/applications/general/email_communication/faq.rst:22
|
||||
msgid "Unsent emails also appear in the Odoo email queue. In :ref:`developer mode <developer-mode>`, the email queue can be accessed by going to :menuselection:`Settings app --> Technical menu --> Email --> Emails`. Unsent emails appear in turquoise, while sent emails appear in grey."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:27
|
||||
msgid "Common error messages"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:31
|
||||
msgid "You reached your daily limit:"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:32
|
||||
msgid "Daily limit reached"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:-1
|
||||
msgid "Warning in Odoo upon email limit reached"
|
||||
msgid "Warning in Odoo upon email limit reached."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:37
|
||||
msgid "Each email service provider has its own email sending limits. The limits may be daily, hourly, and sometimes even per minute. This is the same for Odoo, we have to limit our customers to prevent our e-mail servers from being blacklisted."
|
||||
#: ../../content/applications/general/email_communication/faq.rst:38
|
||||
msgid "Each email service provider has its own email sending limits. The limits may be daily, hourly, or sometimes, per minute. This is the same for Odoo, which limits a customer's sending to prevent Odoo's email servers from being blacklisted."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:41
|
||||
#: ../../content/applications/general/email_communication/faq.rst:42
|
||||
msgid "Here are the default limits for new databases:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:43
|
||||
msgid "200 emails/day for Odoo Online and Odoo.sh databases with an active subscription,"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:44
|
||||
msgid "20 emails/day for one-app free databases,"
|
||||
msgid "**200 emails per day** for Odoo Online and Odoo.sh databases with an active subscription."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:45
|
||||
msgid "50 emails/day for trial databases,"
|
||||
msgid "**20 emails per day** for one-app free databases."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:46
|
||||
msgid "in case of migration, your daily limit might be reset to 50 emails a day."
|
||||
msgid "**50 emails per day** for trial databases."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:48
|
||||
msgid "In case you hit the limit, you can:"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:47
|
||||
msgid "In the case of migration, the daily limit might be reset to 50 emails per day."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:50
|
||||
msgid "Ask our support team to increase your daily limit. We will analyze the situation of your database depending on (non-exhaustive list):"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:49
|
||||
msgid "If the daily limit is reached:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:53
|
||||
msgid "How many users in your database,"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:51
|
||||
msgid "Contact the Odoo support team, who may increase the daily limit depending on the following factors:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:54
|
||||
msgid "Which apps are installed,"
|
||||
msgid "How many users are in the database?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:55
|
||||
msgid "Your bounce rate: the percentage of email addresses that did not receive your emails because it was returned by a mail server on its way to the final recipient. You can contact the `support <https://www.odoo.com/help>`_."
|
||||
msgid "Which apps are installed?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:56
|
||||
msgid "The bounce rate: the percentage of email addresses that did not receive emails because they were returned by a mail server on its way to the final recipient."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:59
|
||||
msgid "Use your own outgoing email server to be independent of Odoo’s mail limit (please refer to :doc:`the corresponding documentation </applications/general/email_communication/email_servers>`),"
|
||||
msgid "Use an external outgoing email server to be independent of Odoo's mail limit (refer to the corresponding :doc:`email documentation </applications/general/email_communication/email_servers>`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:61
|
||||
msgid "Wait until 11pm UTC for the reset and click on the retry button: The :ref:`Developer mode <developer-mode>` must be activated. Then, go to :menuselection:`Settings --> Technical --> Emails`"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:62
|
||||
msgid "Wait until 11 PM (UTC) for the daily limit to reset, and retry sending the email. In :ref:`developer mode <developer-mode>`, go to :menuselection:`Settings app --> Technical menu --> Email --> Emails`, then click the :guilabel:`Retry` button next to an unsent email."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:-1
|
||||
msgid "Retry button of an emails"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:67
|
||||
msgid "The daily email limit is comprehensive to the database. By default, any internal message, notification, logged note, etc. counts as an email in the daily limit if it notifies someone via email. This can be mitigated by receiving :ref:`notifications in Odoo <discuss_app/notification_preferences>`, instead of emails."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:69
|
||||
msgid "The daily limit is global to your database and can rise quickly! By default an internal message, a notification, a note, etc. counts as an email in your daily limit if it notifies someone."
|
||||
#: ../../content/applications/general/email_communication/faq.rst:73
|
||||
msgid "SMTP error"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:72
|
||||
msgid "You can mitigate this by receiving your :ref:`notifications in Odoo <discuss_app/notification_preferences>` instead of by emails."
|
||||
#: ../../content/applications/general/email_communication/faq.rst:75
|
||||
msgid "Simple Mail Transport Protocol (SMTP) error messages explain why an email wasn't transmitted successfully. :abbr:`SMTP (Simple Mail Transport Protocol)` is a protocol to describe the email structure, and transmits data from messages over the Internet. The error messages generated by email services are helpful tools to diagnose and troubleshoot email problems."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:76
|
||||
msgid "SMTP Error"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:81
|
||||
msgid "This is an example of a 554 SMTP permanent delivery error: `554: delivery error: Sorry, your message to ------@yahoo.com cannot be delivered. This mailbox is disabled (554.30). - mta4471.mail.bf1.yahoo.com --- Below this line is a copy of the message.`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:78
|
||||
msgid "You can find out why an email wasn't transmitted successfully by reviewing the Simple Mail Transport Protocol (SMTP) error messages. SMTP is a protocol to describe the email structure and transmit it over the Internet, and the error messages generated by email services are helpful tools to diagnose and troubleshoot email problems."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:84
|
||||
msgid "No Error"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:86
|
||||
msgid "Odoo is not always capable of providing information for the reason it failed. The different providers implement a personalized policy of the bounce emails and it is not always possible for Odoo to interpret it correctly."
|
||||
#: ../../content/applications/general/email_communication/faq.rst:85
|
||||
msgid "The debug menu can be used to investigate SMTP sending issues from a database. To access the menu, :ref:`developer mode <developer-mode>` must be activated. Once activated, navigate to the :menuselection:`Debug Menu` in the top right of the menu bar (the :guilabel:`🐞 (bug)` icon), :menuselection:`Debug Menu --> Manage Messages`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:90
|
||||
msgid "If you have this problem on a recurring basis with the same client or the same domain, please do not hesitate to contact `Odoo Support <https://www.odoo.com/help>`_ for help in finding a reason."
|
||||
msgid "The :guilabel:`Manage Messages` menu opens a list of all the messages sent in a particular record. Within each message there is information on sending, including the type, and subtype, of the message."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:93
|
||||
msgid "Note: in such case, one of the most common reasons is related to :ref:`SPF <email_communication/spf_compliant>` and/or :ref:`DKIM <email_communication/DKIM_compliant>` configuration."
|
||||
#: ../../content/applications/general/email_communication/faq.rst:94
|
||||
msgid "Other information includes to whom the message was sent, and whether Odoo received a bounce-back message from an email server."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:97
|
||||
msgid "Why is my email sent late?"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:-1
|
||||
msgid "Manage messages menu option on the debug menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:99
|
||||
msgid "It may happen that you schedule an email campaign but it is not sent on time. We know that we use a delayed job to send emails that we consider as not urgent (Newsletters concept such as mass mailing, marketing automation, events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. We use that policy in order to avoid cluttering the mail servers and prioritize the communication."
|
||||
#: ../../content/applications/general/email_communication/faq.rst:102
|
||||
msgid "A user must be on a view in Odoo that has a chatter in order for the :guilabel:`Manage Messages` menu option to appear."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:105
|
||||
msgid "The emails considered urgent (communication from one person to another one such as Sales Orders, Invoices, Purchase Orders, etc.) are sent directly."
|
||||
#: ../../content/applications/general/email_communication/faq.rst:106
|
||||
msgid "No error populated"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:108
|
||||
msgid "Odoo is not always capable of providing information for the reason it failed. The different email providers implement a personalized policy of bounced emails, and it is not always possible for Odoo to interpret it correctly."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:112
|
||||
msgid "If this is a recurring problem with the same client, or the same domain, do not hesitate to contact `Odoo Support <https://www.odoo.com/help>`_ for help in finding a reason."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:116
|
||||
msgid "One of the most common reasons for an email failing to send with no error message is related to :ref:`SPF <email_communication/spf_compliant>` and/or :ref:`DKIM <email_communication/DKIM_compliant>` configuration. Also, check to make sure the `mail.bounce.alias` is defined in the *system parameters*. Access system parameters in :ref:`developer mode <developer-mode>` by navigating to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:124
|
||||
msgid "Email is sent late"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:126
|
||||
msgid "Email campaigns send at a scheduled time, using a delay pre-programed in the database. Odoo uses a delayed task to send emails that are considered \"not urgent\" (newsletter formats, such as: mass mailing, marketing automation, and events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. Odoo uses that policy in order to avoid cluttering the mail servers and, instead, prioritizes individual communication. This **cron** is called :guilabel:`Mail: Email Queue Manager`, and can be accessed in :ref:`developer mode <developer-mode>` by going to :menuselection:`Settings app --> Technical menu --> Automation --> Scheduled Actions`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:-1
|
||||
msgid "Email scheduled to be sent later."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:112
|
||||
msgid "By default, the Mass Mailing cron runs every 60 minutes. So, you should wait maximum an hour before the campaign is actually sent."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:116
|
||||
msgid "Incoming emails"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:118
|
||||
msgid "When you have an issue with incoming emails, there might not be an indication per se in Odoo. This is the client who tries to contact a database who will get a bounce (most of the time 550: mailbox unavailable)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:123
|
||||
msgid "Emails are not received"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:125
|
||||
msgid "Depending on the platform you are using:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:127
|
||||
msgid "The **Odoo.sh** users can find their live logs on the folder :file:`~/logs/`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:129
|
||||
msgid "The folder :file:`~/logs/` (preferably accessed by the command line) of an Odoo.sh contains a list of files containing the logs of the database. The log files are created everyday at 5:00 AM UTC. The two last days are not compressed, while the older ones are, in order to gain space. The naming of the files for Today and Yesterday are :file:`odoo.log` and :file:`odoo.log.1`. For the following, they are named with their dates and compressed. See the Odoo.sh documentation about :ref:`logs <odoosh/logs>`. Use the command ``grep`` and ``zgrep`` (for the compressed ones) to search through the files."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:137
|
||||
msgid "**Odoo Online** users won’t have access to their logs. However you can still contact `Odoo Support <https://www.odoo.com/help>`_ , if you have a recurring issue with the same client or domain."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:142
|
||||
msgid "Get help from support"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:140
|
||||
msgid "What is a **cron**? A cron is an action that Odoo runs in the background to execute particular code to complete a task."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:144
|
||||
msgid "In order to get helped efficiently, please provide as much information as possible. Here is a list of what can be helpful:"
|
||||
msgid "By default, the *Mass Mailing cron* runs every 60 minutes. This can be changed to no less than 5 minutes. However, running the action every 5 minutes would bog down the Odoo database (stress the system), so this is not recommended. To edit the mass mailing cron, select the scheduled action :guilabel:`Mail: Email Queue Manager`, and proceed to make any necessary adjustments."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:147
|
||||
msgid "The **EML** of the email, stating for *Electronic Mail*, is the file format containing all the technical information required for an investigation. The documentation of your own email provider might help you on how to get your EML files. Once you get the EML of the email, adding it in the attachment of your ticket is the most efficient way for us to investigate. The support will mainly focus on redundant issues."
|
||||
#: ../../content/applications/general/email_communication/faq.rst:149
|
||||
msgid "Emails that are considered urgent (communication from one person to another, such as sales orders, invoices, purchase orders, etc.) are sent immediately."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:154
|
||||
msgid "`Gmail documentation <https://support.google.com/mail/answer/29436>`_"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:153
|
||||
msgid "Incoming emails"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:156
|
||||
msgid "`Outlook documentation <https://support.microsoft.com/en-us/office/view-internet-message-headers-in-outlook-cd039382-dc6e-4264-ac74-c048563d212c#tab=Web>`_"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:155
|
||||
msgid "When there is an issue with incoming emails, there might not be an indication, per se, in Odoo. It is the sending email client, who tries to contact a database, that will get a bounce-back message (most of the time a :guilabel:`550: mailbox unavailable` error message)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:159
|
||||
msgid "The exact flow you are following in order to normally receive those emails in Odoo. Here are examples of questions whose answers can be useful:"
|
||||
#: ../../content/applications/general/email_communication/faq.rst:160
|
||||
msgid "Email is not received"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:162
|
||||
msgid "Is this simply a reply from an email going out from Odoo ?"
|
||||
msgid "The steps that should be taken depend on the Odoo platform where the database is hosted."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:164
|
||||
msgid "Are you using an incoming email server or somehow redirecting?"
|
||||
msgid "**Odoo.sh** users can find their live logs on the folder :file:`~/logs/`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:166
|
||||
msgid "Can you provide us with an example of an email that has been correctly forwarded ?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:168
|
||||
msgid "Providing answers to the following questions:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:170
|
||||
msgid "Is it a generic issue or is it specific to a use case? If yes, which one exactly?"
|
||||
msgid "Logs are a stored collection of all the tasks completed in a database. They are a text-only representation, complete with timestamps of every action taken on the Odoo database. This can be helpful to track emails leaving the database. Failure to send can also be seen by logs that indicate that the message tried to send repeatedly. Logs will show every action to the email servers from the database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:172
|
||||
msgid "Is it working as expected? In case the email is sent using Odoo, the bounce email should reach the Odoo database and display the :ref:`red envelope <red_envelop>`."
|
||||
msgid "The folder :file:`~/logs/` (accessed by the command line or on the Odoo.sh dashboard) of an Odoo.sh database contains a list of files containing the logs of the database. The log files are created everyday at 5:00 AM (UTC)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:177
|
||||
msgid "The two most recent days (today and yesterday) are not compressed, while the older ones are, in order to save space. The naming of the files for today and yesterday are respectively: :file:`odoo.log` and :file:`odoo.log.1`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:181
|
||||
msgid "For the following days, they are named with their dates, and then compressed. Use the command :command:`grep` and :command:`zgrep` (for the compressed ones) to search through the files."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:185
|
||||
msgid "For more information on logs and how to access them via the Odoo.sh dashboard, see :ref:`this administration documentation <odoosh/logs>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:188
|
||||
msgid "For more information on accessing logs via the command line visit :ref:`this developer documentation <reference/cmdline/server/logging>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:191
|
||||
msgid "**Odoo Online** users won't have access to the logs. However `Odoo Support <https://www.odoo.com/help>`_ can be contacted if there is a recurring issue with the same client or domain."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:196
|
||||
msgid "Get help from Odoo support"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:198
|
||||
msgid "In order to get helped efficiently, please provide as much information as possible. Here is a list of what can be helpful when reaching out to the Odoo Support team about an issue:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:201
|
||||
msgid "Send a copy of the email headers. The `.EML` file (or **headers**) of the email is the file format containing all the technical information required for an investigation. The documentation from the email provider might explain how to access the EML file/header files. Once the headers of the email are obtained, adding it into the Odoo Support ticket is the most efficient way for the Odoo Support team to investigate."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:208
|
||||
msgid "`Gmail documentation on headers <https://support.google.com/mail/answer/29436>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:209
|
||||
msgid "`Outlook documentation on headers <https://support.microsoft.com/en-us/office/view-internet-message-headers-in-outlook-cd039382-dc6e-4264-ac74-c048563d212c#tab=Web>`_"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:212
|
||||
msgid "Explain the exact flow that is being followed to normally receive those emails in Odoo. Here are examples of questions whose answers can be useful:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:215
|
||||
msgid "Is this a notification message from a reply being received in Odoo?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:216
|
||||
msgid "Is this a message being sent from the Odoo database?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:217
|
||||
msgid "Is there an incoming email server being used, or is the email somehow being redirected?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:218
|
||||
msgid "Is there an example of an email that has been correctly forwarded?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:220
|
||||
msgid "Provide answers to the following questions:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:222
|
||||
msgid "Is it a generic issue, or is it specific to a use case? If specific to a use case, which one exactly?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:224
|
||||
msgid "Is it working as expected? In case the email is sent using Odoo, the bounce email should reach the Odoo database, and display the :ref:`red envelope <red_envelop>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/email_communication/faq.rst:228
|
||||
msgid "The bounce system parameter needs to be set in the technical settings in order for the database to correctly receive bounce messages. To access this setting, go to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`. Then select the parameter name :guilabel:`mail.bounce.alias` and set the value to `bounce` if it isn't already set."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/export_import_data.rst:3
|
||||
|
||||
Reference in New Issue
Block a user