2016-07-15 13:41:49 +02:00
|
|
|
=========================
|
|
|
|
|
Mail tracking for Mailgun
|
|
|
|
|
=========================
|
|
|
|
|
|
2018-11-05 22:03:00 +01:00
|
|
|
.. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|
|
|
|
!! This file is generated by oca-gen-addon-readme !!
|
|
|
|
|
!! changes will be overwritten. !!
|
|
|
|
|
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|
|
|
|
|
|
|
|
|
.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
|
|
|
|
|
:target: https://odoo-community.org/page/development-status
|
|
|
|
|
:alt: Beta
|
|
|
|
|
.. |badge2| image:: https://img.shields.io/badge/licence-AGPL--3-blue.png
|
|
|
|
|
:target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
|
|
|
|
|
:alt: License: AGPL-3
|
|
|
|
|
.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fsocial-lightgray.png?logo=github
|
2022-12-22 19:49:43 +01:00
|
|
|
:target: https://github.com/OCA/social/tree/15.0/mail_tracking_mailgun
|
2018-11-05 22:03:00 +01:00
|
|
|
:alt: OCA/social
|
|
|
|
|
.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png
|
2022-12-22 19:49:43 +01:00
|
|
|
:target: https://translation.odoo-community.org/projects/social-15-0/social-15-0-mail_tracking_mailgun
|
2018-11-05 22:03:00 +01:00
|
|
|
:alt: Translate me on Weblate
|
|
|
|
|
.. |badge5| image:: https://img.shields.io/badge/runbot-Try%20me-875A7B.png
|
2022-12-22 19:49:43 +01:00
|
|
|
:target: https://runbot.odoo-community.org/runbot/205/15.0
|
2018-11-05 22:03:00 +01:00
|
|
|
:alt: Try me on Runbot
|
|
|
|
|
|
2022-02-25 16:25:20 +01:00
|
|
|
|badge1| |badge2| |badge3| |badge4| |badge5|
|
2018-11-05 22:03:00 +01:00
|
|
|
|
2016-07-15 13:41:49 +02:00
|
|
|
This module integrates mail_tracking events with Mailgun webhooks.
|
|
|
|
|
|
|
|
|
|
Mailgun (https://www.mailgun.com/) is a service that provides an e-mail
|
|
|
|
|
sending infrastructure through an SMTP server or via API. You can also
|
|
|
|
|
query that API for seeing statistics of your sent e-mails, or provide
|
|
|
|
|
hooks that processes the status changes in real time, which is the
|
|
|
|
|
function used here.
|
|
|
|
|
|
2018-11-05 22:03:00 +01:00
|
|
|
**Table of contents**
|
|
|
|
|
|
|
|
|
|
.. contents::
|
|
|
|
|
:local:
|
|
|
|
|
|
[IMP] mail_tracking_mailgun: refactor to support modern webhooks
Before this patch, the module was designed after the [deprecated Mailgun webhooks][3]. However Mailgun had the [events API][2] which was quite different. Modern Mailgun has deprecated those webhooks and instead uses new ones that include the same payload as the events API, so you can reuse code.
However, this was incorrectly reusing the code inversely: trying to process the events API through the same code prepared for the deprecated webhooks.
Besides, both `failed` and `rejected` mailgun events were mapped to `error` state, but that was also wrong because [`mail_tracking` doesn't have an `error` state][1].
So the logic of the whole module is changed, adapting it to process the events API payload, both through controllers (prepared for the new webhooks) and manual updates that directly call the events API.
Also, `rejected` is now translated into `reject`, and `failed` is translated into `hard_bounce` or `soft_bounce` depending on the severity, as specified by [mailgun docs][2]. Also, `bounced` and `dropped` mailgun states are removed because they don't exist, and instead `failed` and `rejected` properly get their metadata.
Of course, to know the severity, now the method to obtain that info must change, it' can't be a simple dict anymore.
Added more parameters because for example modern Mailgun uses different keys for signing payload than for accessing the API. As there are so many parameters, configuration is now possible through `res.config.settings`. Go there to autoregister webhooks too.
Since the new webhooks are completely incompatible with the old supposedly-abstract webhooks controllers (that were never really that abstract), support for old webhooks is removed, and it will be removed in the future from `mail_tracking` directly. There is a migration script that attempts to unregister old webhooks and register new ones automatically.
[1]: https://github.com/OCA/social/blob/f73de421e28a43d018176f61725a3a59665f715d/mail_tracking/models/mail_tracking_event.py#L31-L42
[2]: https://documentation.mailgun.com/en/latest/api-events.html#event-types
[3]: https://documentation.mailgun.com/en/latest/api-webhooks-deprecated.html
2021-10-28 12:33:59 +02:00
|
|
|
Installation
|
|
|
|
|
============
|
2016-07-15 13:41:49 +02:00
|
|
|
|
[IMP] mail_tracking_mailgun: refactor to support modern webhooks
Before this patch, the module was designed after the [deprecated Mailgun webhooks][3]. However Mailgun had the [events API][2] which was quite different. Modern Mailgun has deprecated those webhooks and instead uses new ones that include the same payload as the events API, so you can reuse code.
However, this was incorrectly reusing the code inversely: trying to process the events API through the same code prepared for the deprecated webhooks.
Besides, both `failed` and `rejected` mailgun events were mapped to `error` state, but that was also wrong because [`mail_tracking` doesn't have an `error` state][1].
So the logic of the whole module is changed, adapting it to process the events API payload, both through controllers (prepared for the new webhooks) and manual updates that directly call the events API.
Also, `rejected` is now translated into `reject`, and `failed` is translated into `hard_bounce` or `soft_bounce` depending on the severity, as specified by [mailgun docs][2]. Also, `bounced` and `dropped` mailgun states are removed because they don't exist, and instead `failed` and `rejected` properly get their metadata.
Of course, to know the severity, now the method to obtain that info must change, it' can't be a simple dict anymore.
Added more parameters because for example modern Mailgun uses different keys for signing payload than for accessing the API. As there are so many parameters, configuration is now possible through `res.config.settings`. Go there to autoregister webhooks too.
Since the new webhooks are completely incompatible with the old supposedly-abstract webhooks controllers (that were never really that abstract), support for old webhooks is removed, and it will be removed in the future from `mail_tracking` directly. There is a migration script that attempts to unregister old webhooks and register new ones automatically.
[1]: https://github.com/OCA/social/blob/f73de421e28a43d018176f61725a3a59665f715d/mail_tracking/models/mail_tracking_event.py#L31-L42
[2]: https://documentation.mailgun.com/en/latest/api-events.html#event-types
[3]: https://documentation.mailgun.com/en/latest/api-webhooks-deprecated.html
2021-10-28 12:33:59 +02:00
|
|
|
If you're using a multi-database installation (with or without dbfilter option)
|
|
|
|
|
where /web/databse/selector returns a list of more than one database, then
|
|
|
|
|
you need to add ``mail_tracking_mailgun`` addon to wide load addons list
|
|
|
|
|
(by default, only ``web`` addon), setting ``--load`` option.
|
2016-07-15 13:41:49 +02:00
|
|
|
|
[IMP] mail_tracking_mailgun: refactor to support modern webhooks
Before this patch, the module was designed after the [deprecated Mailgun webhooks][3]. However Mailgun had the [events API][2] which was quite different. Modern Mailgun has deprecated those webhooks and instead uses new ones that include the same payload as the events API, so you can reuse code.
However, this was incorrectly reusing the code inversely: trying to process the events API through the same code prepared for the deprecated webhooks.
Besides, both `failed` and `rejected` mailgun events were mapped to `error` state, but that was also wrong because [`mail_tracking` doesn't have an `error` state][1].
So the logic of the whole module is changed, adapting it to process the events API payload, both through controllers (prepared for the new webhooks) and manual updates that directly call the events API.
Also, `rejected` is now translated into `reject`, and `failed` is translated into `hard_bounce` or `soft_bounce` depending on the severity, as specified by [mailgun docs][2]. Also, `bounced` and `dropped` mailgun states are removed because they don't exist, and instead `failed` and `rejected` properly get their metadata.
Of course, to know the severity, now the method to obtain that info must change, it' can't be a simple dict anymore.
Added more parameters because for example modern Mailgun uses different keys for signing payload than for accessing the API. As there are so many parameters, configuration is now possible through `res.config.settings`. Go there to autoregister webhooks too.
Since the new webhooks are completely incompatible with the old supposedly-abstract webhooks controllers (that were never really that abstract), support for old webhooks is removed, and it will be removed in the future from `mail_tracking` directly. There is a migration script that attempts to unregister old webhooks and register new ones automatically.
[1]: https://github.com/OCA/social/blob/f73de421e28a43d018176f61725a3a59665f715d/mail_tracking/models/mail_tracking_event.py#L31-L42
[2]: https://documentation.mailgun.com/en/latest/api-events.html#event-types
[3]: https://documentation.mailgun.com/en/latest/api-webhooks-deprecated.html
2021-10-28 12:33:59 +02:00
|
|
|
Example: ``--load=web,mail_tracking,mail_tracking_mailgun``
|
2016-07-15 13:41:49 +02:00
|
|
|
|
[IMP] mail_tracking_mailgun: refactor to support modern webhooks
Before this patch, the module was designed after the [deprecated Mailgun webhooks][3]. However Mailgun had the [events API][2] which was quite different. Modern Mailgun has deprecated those webhooks and instead uses new ones that include the same payload as the events API, so you can reuse code.
However, this was incorrectly reusing the code inversely: trying to process the events API through the same code prepared for the deprecated webhooks.
Besides, both `failed` and `rejected` mailgun events were mapped to `error` state, but that was also wrong because [`mail_tracking` doesn't have an `error` state][1].
So the logic of the whole module is changed, adapting it to process the events API payload, both through controllers (prepared for the new webhooks) and manual updates that directly call the events API.
Also, `rejected` is now translated into `reject`, and `failed` is translated into `hard_bounce` or `soft_bounce` depending on the severity, as specified by [mailgun docs][2]. Also, `bounced` and `dropped` mailgun states are removed because they don't exist, and instead `failed` and `rejected` properly get their metadata.
Of course, to know the severity, now the method to obtain that info must change, it' can't be a simple dict anymore.
Added more parameters because for example modern Mailgun uses different keys for signing payload than for accessing the API. As there are so many parameters, configuration is now possible through `res.config.settings`. Go there to autoregister webhooks too.
Since the new webhooks are completely incompatible with the old supposedly-abstract webhooks controllers (that were never really that abstract), support for old webhooks is removed, and it will be removed in the future from `mail_tracking` directly. There is a migration script that attempts to unregister old webhooks and register new ones automatically.
[1]: https://github.com/OCA/social/blob/f73de421e28a43d018176f61725a3a59665f715d/mail_tracking/models/mail_tracking_event.py#L31-L42
[2]: https://documentation.mailgun.com/en/latest/api-events.html#event-types
[3]: https://documentation.mailgun.com/en/latest/api-webhooks-deprecated.html
2021-10-28 12:33:59 +02:00
|
|
|
Configuration
|
|
|
|
|
=============
|
2016-07-15 13:41:49 +02:00
|
|
|
|
[IMP] mail_tracking_mailgun: refactor to support modern webhooks
Before this patch, the module was designed after the [deprecated Mailgun webhooks][3]. However Mailgun had the [events API][2] which was quite different. Modern Mailgun has deprecated those webhooks and instead uses new ones that include the same payload as the events API, so you can reuse code.
However, this was incorrectly reusing the code inversely: trying to process the events API through the same code prepared for the deprecated webhooks.
Besides, both `failed` and `rejected` mailgun events were mapped to `error` state, but that was also wrong because [`mail_tracking` doesn't have an `error` state][1].
So the logic of the whole module is changed, adapting it to process the events API payload, both through controllers (prepared for the new webhooks) and manual updates that directly call the events API.
Also, `rejected` is now translated into `reject`, and `failed` is translated into `hard_bounce` or `soft_bounce` depending on the severity, as specified by [mailgun docs][2]. Also, `bounced` and `dropped` mailgun states are removed because they don't exist, and instead `failed` and `rejected` properly get their metadata.
Of course, to know the severity, now the method to obtain that info must change, it' can't be a simple dict anymore.
Added more parameters because for example modern Mailgun uses different keys for signing payload than for accessing the API. As there are so many parameters, configuration is now possible through `res.config.settings`. Go there to autoregister webhooks too.
Since the new webhooks are completely incompatible with the old supposedly-abstract webhooks controllers (that were never really that abstract), support for old webhooks is removed, and it will be removed in the future from `mail_tracking` directly. There is a migration script that attempts to unregister old webhooks and register new ones automatically.
[1]: https://github.com/OCA/social/blob/f73de421e28a43d018176f61725a3a59665f715d/mail_tracking/models/mail_tracking_event.py#L31-L42
[2]: https://documentation.mailgun.com/en/latest/api-events.html#event-types
[3]: https://documentation.mailgun.com/en/latest/api-webhooks-deprecated.html
2021-10-28 12:33:59 +02:00
|
|
|
To configure this module, you need to:
|
2017-10-17 20:38:11 +02:00
|
|
|
|
[IMP] mail_tracking_mailgun: refactor to support modern webhooks
Before this patch, the module was designed after the [deprecated Mailgun webhooks][3]. However Mailgun had the [events API][2] which was quite different. Modern Mailgun has deprecated those webhooks and instead uses new ones that include the same payload as the events API, so you can reuse code.
However, this was incorrectly reusing the code inversely: trying to process the events API through the same code prepared for the deprecated webhooks.
Besides, both `failed` and `rejected` mailgun events were mapped to `error` state, but that was also wrong because [`mail_tracking` doesn't have an `error` state][1].
So the logic of the whole module is changed, adapting it to process the events API payload, both through controllers (prepared for the new webhooks) and manual updates that directly call the events API.
Also, `rejected` is now translated into `reject`, and `failed` is translated into `hard_bounce` or `soft_bounce` depending on the severity, as specified by [mailgun docs][2]. Also, `bounced` and `dropped` mailgun states are removed because they don't exist, and instead `failed` and `rejected` properly get their metadata.
Of course, to know the severity, now the method to obtain that info must change, it' can't be a simple dict anymore.
Added more parameters because for example modern Mailgun uses different keys for signing payload than for accessing the API. As there are so many parameters, configuration is now possible through `res.config.settings`. Go there to autoregister webhooks too.
Since the new webhooks are completely incompatible with the old supposedly-abstract webhooks controllers (that were never really that abstract), support for old webhooks is removed, and it will be removed in the future from `mail_tracking` directly. There is a migration script that attempts to unregister old webhooks and register new ones automatically.
[1]: https://github.com/OCA/social/blob/f73de421e28a43d018176f61725a3a59665f715d/mail_tracking/models/mail_tracking_event.py#L31-L42
[2]: https://documentation.mailgun.com/en/latest/api-events.html#event-types
[3]: https://documentation.mailgun.com/en/latest/api-webhooks-deprecated.html
2021-10-28 12:33:59 +02:00
|
|
|
#. Go to Mailgun, create an account and validate your sending domain.
|
|
|
|
|
#. Go back to Odoo.
|
|
|
|
|
#. Go to *Settings > General Settings > Discuss > Enable mail tracking with Mailgun*.
|
|
|
|
|
#. Fill all the values. The only one required is the API key.
|
|
|
|
|
#. Optionally click *Unregister Mailgun webhooks* and accept.
|
|
|
|
|
#. Click *Register Mailgun webhooks*.
|
2016-07-15 13:41:49 +02:00
|
|
|
|
2018-02-16 13:15:32 +01:00
|
|
|
You can also config partner email autocheck with this system parameter:
|
|
|
|
|
|
|
|
|
|
- `mailgun.auto_check_partner_email`: Set it to True.
|
|
|
|
|
|
2016-07-15 13:41:49 +02:00
|
|
|
Usage
|
|
|
|
|
=====
|
|
|
|
|
|
2018-05-08 18:24:36 +02:00
|
|
|
In your mail tracking status screens (explained on module *mail_tracking*), you
|
|
|
|
|
will see a more accurate information, like the 'Received' or 'Bounced' status,
|
|
|
|
|
which are not usually detected by normal SMTP servers.
|
2016-07-15 13:41:49 +02:00
|
|
|
|
2018-05-08 18:24:36 +02:00
|
|
|
It's also possible to make some checks to the partner's email addresses against
|
|
|
|
|
the Mailgun API:
|
2017-10-17 20:38:11 +02:00
|
|
|
|
|
|
|
|
- Check if the partner's email is in Mailgun's bounced list.
|
|
|
|
|
- Check the validity of the partner's mailbox.
|
|
|
|
|
- Force the partner's email into Mailgun's bounced list or delete from it.
|
|
|
|
|
|
|
|
|
|
It's also possible to manually check a message mailgun tracking when the webhook
|
|
|
|
|
couldn't be captured. For that, go to that message tracking form, press the
|
|
|
|
|
button *Check Mailgun*. It's important to note that tracking events have quite a
|
|
|
|
|
short lifespan, so after 24h they won't be recoverable.
|
|
|
|
|
|
2016-07-15 13:41:49 +02:00
|
|
|
Known issues / Roadmap
|
|
|
|
|
======================
|
|
|
|
|
|
|
|
|
|
* There's no support for more than one Mailgun mail server.
|
|
|
|
|
|
[IMP] mail_tracking_mailgun: refactor to support modern webhooks
Before this patch, the module was designed after the [deprecated Mailgun webhooks][3]. However Mailgun had the [events API][2] which was quite different. Modern Mailgun has deprecated those webhooks and instead uses new ones that include the same payload as the events API, so you can reuse code.
However, this was incorrectly reusing the code inversely: trying to process the events API through the same code prepared for the deprecated webhooks.
Besides, both `failed` and `rejected` mailgun events were mapped to `error` state, but that was also wrong because [`mail_tracking` doesn't have an `error` state][1].
So the logic of the whole module is changed, adapting it to process the events API payload, both through controllers (prepared for the new webhooks) and manual updates that directly call the events API.
Also, `rejected` is now translated into `reject`, and `failed` is translated into `hard_bounce` or `soft_bounce` depending on the severity, as specified by [mailgun docs][2]. Also, `bounced` and `dropped` mailgun states are removed because they don't exist, and instead `failed` and `rejected` properly get their metadata.
Of course, to know the severity, now the method to obtain that info must change, it' can't be a simple dict anymore.
Added more parameters because for example modern Mailgun uses different keys for signing payload than for accessing the API. As there are so many parameters, configuration is now possible through `res.config.settings`. Go there to autoregister webhooks too.
Since the new webhooks are completely incompatible with the old supposedly-abstract webhooks controllers (that were never really that abstract), support for old webhooks is removed, and it will be removed in the future from `mail_tracking` directly. There is a migration script that attempts to unregister old webhooks and register new ones automatically.
[1]: https://github.com/OCA/social/blob/f73de421e28a43d018176f61725a3a59665f715d/mail_tracking/models/mail_tracking_event.py#L31-L42
[2]: https://documentation.mailgun.com/en/latest/api-events.html#event-types
[3]: https://documentation.mailgun.com/en/latest/api-webhooks-deprecated.html
2021-10-28 12:33:59 +02:00
|
|
|
* Automate more webhook registration. It would be nice to not have to click the
|
|
|
|
|
"Unregister Mailgun webhooks" and "Register Mailgun webhooks" when setting up
|
|
|
|
|
Mailgun in Odoo. However, it doesn't come without its `conceptual complexities
|
|
|
|
|
<https://github.com/OCA/social/pull/787#discussion_r734275262>`__.
|
|
|
|
|
|
2016-07-15 13:41:49 +02:00
|
|
|
Bug Tracker
|
|
|
|
|
===========
|
|
|
|
|
|
2018-11-05 22:03:00 +01:00
|
|
|
Bugs are tracked on `GitHub Issues <https://github.com/OCA/social/issues>`_.
|
|
|
|
|
In case of trouble, please check there if your issue has already been reported.
|
|
|
|
|
If you spotted it first, help us smashing it by providing a detailed and welcomed
|
2022-12-22 19:49:43 +01:00
|
|
|
`feedback <https://github.com/OCA/social/issues/new?body=module:%20mail_tracking_mailgun%0Aversion:%2015.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.
|
2018-11-05 22:03:00 +01:00
|
|
|
|
|
|
|
|
Do not contact contributors directly about support or help with technical issues.
|
2016-07-15 13:41:49 +02:00
|
|
|
|
|
|
|
|
Credits
|
|
|
|
|
=======
|
|
|
|
|
|
2018-11-05 22:03:00 +01:00
|
|
|
Authors
|
|
|
|
|
~~~~~~~
|
|
|
|
|
|
|
|
|
|
* Tecnativa
|
|
|
|
|
|
|
|
|
|
Contributors
|
|
|
|
|
~~~~~~~~~~~~
|
|
|
|
|
|
|
|
|
|
* `Tecnativa <https://www.tecnativa.com>`_:
|
|
|
|
|
|
|
|
|
|
* Antonio Espinosa
|
|
|
|
|
* Carlos Dauden
|
|
|
|
|
* Pedro M. Baeza
|
|
|
|
|
* David Vidal
|
|
|
|
|
* Rafael Blasco
|
|
|
|
|
* Ernesto Tejeda
|
[IMP] mail_tracking_mailgun: refactor to support modern webhooks
Before this patch, the module was designed after the [deprecated Mailgun webhooks][3]. However Mailgun had the [events API][2] which was quite different. Modern Mailgun has deprecated those webhooks and instead uses new ones that include the same payload as the events API, so you can reuse code.
However, this was incorrectly reusing the code inversely: trying to process the events API through the same code prepared for the deprecated webhooks.
Besides, both `failed` and `rejected` mailgun events were mapped to `error` state, but that was also wrong because [`mail_tracking` doesn't have an `error` state][1].
So the logic of the whole module is changed, adapting it to process the events API payload, both through controllers (prepared for the new webhooks) and manual updates that directly call the events API.
Also, `rejected` is now translated into `reject`, and `failed` is translated into `hard_bounce` or `soft_bounce` depending on the severity, as specified by [mailgun docs][2]. Also, `bounced` and `dropped` mailgun states are removed because they don't exist, and instead `failed` and `rejected` properly get their metadata.
Of course, to know the severity, now the method to obtain that info must change, it' can't be a simple dict anymore.
Added more parameters because for example modern Mailgun uses different keys for signing payload than for accessing the API. As there are so many parameters, configuration is now possible through `res.config.settings`. Go there to autoregister webhooks too.
Since the new webhooks are completely incompatible with the old supposedly-abstract webhooks controllers (that were never really that abstract), support for old webhooks is removed, and it will be removed in the future from `mail_tracking` directly. There is a migration script that attempts to unregister old webhooks and register new ones automatically.
[1]: https://github.com/OCA/social/blob/f73de421e28a43d018176f61725a3a59665f715d/mail_tracking/models/mail_tracking_event.py#L31-L42
[2]: https://documentation.mailgun.com/en/latest/api-events.html#event-types
[3]: https://documentation.mailgun.com/en/latest/api-webhooks-deprecated.html
2021-10-28 12:33:59 +02:00
|
|
|
* Jairo Llopis
|
2021-07-22 10:24:42 +02:00
|
|
|
* Carlos Roca
|
2018-11-05 22:03:00 +01:00
|
|
|
|
|
|
|
|
Other credits
|
|
|
|
|
~~~~~~~~~~~~~
|
|
|
|
|
|
2016-07-15 13:41:49 +02:00
|
|
|
Images
|
|
|
|
|
------
|
|
|
|
|
|
|
|
|
|
* Mailgun logo: `SVG Icon <http://seeklogo.com/mailgun-logo-273630.html>`_.
|
|
|
|
|
|
2018-11-05 22:03:00 +01:00
|
|
|
Maintainers
|
|
|
|
|
~~~~~~~~~~~
|
2016-07-15 13:41:49 +02:00
|
|
|
|
2018-11-05 22:03:00 +01:00
|
|
|
This module is maintained by the OCA.
|
2016-07-15 13:41:49 +02:00
|
|
|
|
|
|
|
|
.. image:: https://odoo-community.org/logo.png
|
|
|
|
|
:alt: Odoo Community Association
|
|
|
|
|
:target: https://odoo-community.org
|
|
|
|
|
|
|
|
|
|
OCA, or the Odoo Community Association, is a nonprofit organization whose
|
|
|
|
|
mission is to support the collaborative development of Odoo features and
|
|
|
|
|
promote its widespread use.
|
|
|
|
|
|
2022-12-22 19:49:43 +01:00
|
|
|
This module is part of the `OCA/social <https://github.com/OCA/social/tree/15.0/mail_tracking_mailgun>`_ project on GitHub.
|
2018-11-05 22:03:00 +01:00
|
|
|
|
|
|
|
|
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
|