Lines of code | 70 |
Technical Name |
mailgun |
License | See License tab |
Website | https://itpp.dev |
Also available in version | v 10.0 v 9.0 |
Lines of code | 70 |
Technical Name |
mailgun |
License | See License tab |
Website | https://itpp.dev |
Also available in version | v 10.0 v 9.0 |
Mailgun
Easy to setup the outgoing and incoming mail flow
- Powerful Sending Infrastructure
- Intelligent Inbound Routing & Storage
- Tracking and Analytics
- Email Validation
Mailgun Configuration
Manage Domains
Note that the state of your domain should be Active to be able to use it from Odoo side. To verify it follow the instruction How do I verify my domain

Click on added domain name and see all the information needed to configure your Incoming and Outgoing mail feature.

If you use sandbox domain, add Authorized Recipient first (sandbox domains are restricted to authorized recipients)


Routes
Navigate to Routes menu and create a new route

Set the following fields and values:

Now everything is ready to move to Odoo configuration.
Odoo Configuration
Outgoing Mail Feature
At first, activate the developer mode. Then go to Settings → Technical → Email → Outgoing Mail Servers menu and populate the following fields:
Once the fields are populated, click Test Connection button to check the connection to smtp server. If everything is ok, you can see popup message Connection Test Succeeded! Everything seems properly set up! and you are able to send messages now.

Incoming Mail Feature
Note that to setup incoming mailing, it is not required to setup Incoming Mail Server.
Open Settings → General Settings menu:
Save the changes.

Setup mailgun API credentials in Settings → Parameters → System Parameters menu. Create new parameter:

Now you can configure mail aliases for users. Go to Settings → Users menu and open user form (e.g. for Administrator). Then switch to Preferences tab and select an existing alias or create new one in the Alias field.

Open the user's related partner and set Email - the email is used for replying on user messages

Everything is done! It's time to send/receive email messages now!
Need our service?
Contact us by email or fill out request form
- apps@it-projects.info
- https://www.it-projects.info/page/website.contactus
- https://m.me/itprojectsllc
- skype@it-projects.info
11.0 community
11.0 enterprise
Mailgun
Installation
- Install this module in a usual way
Configuration
Mailgun-side
- register or log in http://mailgun.com
- Open menu [[ Domains ]] and click on your domain, e.g. sandbox123*****.mailgun.org domain. Here you can see all the information needed to configure odoo outgoing mail feature
- Please note that state of your domain should be Active before you can use it. If it is Unverified, verify it first using Mailgun FAQ - How do I verify my domain
- if you are using your sandbox domain, add Authorized Recipient first (Sandbox domains are restricted to authorized recipients only)
- create new Route
- Open menu [[ Routes ]]
- Click [Create Route] button
- Expression Type - Custom
- Raw Expression - match_recipient('.*@<your mail domain>')
- Actions - Store and notify, http://<your odoo domain>/mailgun/notify
Odoo-side
- Activate Developer Mode
- Configure Outgoung mail server
- Open menu [[ Settings ]] >> Technical >> Email >> Outgoing Mail Servers
- Edit localhost record or create new one with the following:
- Description - Mailgun
- SMTP Server - take from Mailgun SMTP Hostname (usually, it is smtp.mailgun.org)
- Connection Security - SSL/TLS
- Username - take from Mailgun Default SMTP Login
- Password - take from Mailgun Default Password
- Click [Test Connection] button to check the connection and then [Save]
- Configure Incoming mail feature
- Configure catchall domain
- Open menu Settings / General Settings, check External Email Servers and edit Alias Domain - set it from Mailgun Domain Name
- Click [Save] button
- Set Mailgun API credentials
- Open menu [[ Settings ]] >> Parameters >> System Parameters
- Create new parameter
- key: mailgun.apikey
- Value: API Key from mailgun (key-...)
- Click [Save] button
- Configure mail aliases and emails for users
- Open menu [[ Settings ]] >> Users >> Users
- Select the Administrator user (for example, you should configure all your users the same way but using different aliases) and click [Edit]
- On Preference tab edit Alias field - create new mail alias, e.g. admin@<you mail domain> with the following settings
- Alias Name - admin
- Aliased Model - Users
- Record Thread ID - 1
- Default Values - {}
- Alias Contact - Everyone
- Security Owner - Administrator
- Parent Model - Not set
- Parent Record Thread ID - 0
- Open user's Related Partner and edit Email field - usually it should be the same as mail alias name (admin@<you mailgun domain for Administrator) - this would be an address for replying user's messages
- Configure catchall domain
Usage
Outgoing
- Open menu [[ Settings ]]>> Email >> Emails to create a message
- Click [Send Now] button
- RESULT: receive the message in your mail client (e.g. on gmail.com)
Incoming
- Create new message from your mail client to e.g. admin@<you mailgun domain>
- Open menu [[ Discuss ]] in Odoo
- RESULT: See your message there
GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below. 0. Additional Definitions. As used herein, "this License" refers to version 3 of the GNU Lesser General Public License, and the "GNU GPL" refers to version 3 of the GNU General Public License. "The Library" refers to a covered work governed by this License, other than an Application or a Combined Work as defined below. An "Application" is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library. A "Combined Work" is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the "Linked Version". The "Minimal Corresponding Source" for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version. The "Corresponding Application Code" for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work. 1. Exception to Section 3 of the GNU GPL. You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL. 2. Conveying Modified Versions. If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version: a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy. 3. Object Code Incorporating Material from Library Header Files. The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following: a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the object code with a copy of the GNU GPL and this license document. 4. Combined Works. You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following: a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the Combined Work with a copy of the GNU GPL and this license document. c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document. d) Do one of the following: 0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source. 1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version. e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.) 5. Combined Libraries. You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License. b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 6. Revised Versions of the GNU Lesser General Public License. The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation. If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.
Please log in to comment on this module