@@ -271,3 +271,32 @@ By default, inbound messages are fetched every 5 minutes for on-premise database
271271 This value can be changed in :ref: `developer mode <developer-mode >`. Go to
272272 :menuselection: `Settings --> Technical --> Automation --> Scheduled Actions ` and look for
273273 :guilabel: `Mail: Fetchmail Service `.
274+
275+ System parameters that prevent feedback loops
276+ ---------------------------------------------
277+
278+ There are two system parameters that help prevent email loops from occurring in Odoo. These
279+ parameters were introduced in Odoo 16 to prevent aliases from creating too many records and to
280+ prevent feedback loops on the catchall reply-to email address. They are present in database but not
281+ in the *System Parameters *. To override the following defaults they need to be added in.
282+
283+ The two system parameters are as follows:
284+
285+ - `mail.incoming.limit.period ` (60 minutes by default)
286+ - `mail.incoming.limit.alias ` (5 by default)
287+
288+ Add these fields in Odoo by first enabling :ref: `developer mode <developer-mode >`, and then
289+ navigating to :menuselection: `Settings --> Technical Menu --> Parameters --> System Parameters `.
290+ Change the value of these parameters, as needed.
291+
292+ When an email is received in the Odoo database on the catchall email address or on any alias, Odoo
293+ looks at the mail received for the given period of time defined in the system parameter
294+ `mail.incoming.limit.period `. If the received email was sent to an alias then Odoo will reference
295+ the `mail.incoming.limit.alias ` system parameter and determine the value as the number of records
296+ this alias is allowed to create in the given period of time (value of `mail.incoming.limit.period `).
297+
298+ In addition, when email is received to the catchall email address, Odoo will reference the emails
299+ received to the database during the set period of time (as stated by the value in the system
300+ parameter: `mail.incoming.limit.period `). Odoo will then determine whether any of the emails
301+ received match that of the email(s) being received during the specified time-frame, and will prevent
302+ a feedback loop from occurring if a duplicate email is detected.
0 commit comments