Friday, November 09, 2018

Prepare to swith to other alternatives

Odoo 12 Community Edition removed accounting module. Without accounting module, it become useless. Most importantly, can foresee more and more core modules will be moved to enterprise edition. 

Sooner or later, we have to switch to other alternatives. 

Do some study first. Will keep track of the movement and decide.


Re: odoo vs. ERPNext

Fabien Bourgeois
 -  09/19/2017 05:22:04
Le 18/09/2017 à 14:25, Andreas Becker a écrit :
The CEO of Frappe brought an interesting input:

I have tried to summarize differences I see between the two solutions :

Quick copy-paste here for archiving :

I currently test the solution and the Frappé framework but I haven’t finished yet. So my analysis may be partial and not scientific… Please correct me if I’m wrong. To me, there a many little differences between these two open source ERP :
  1. Release model
    • ERPNext has a rolling-release model and includes migration scripts. Therefore you always benefit from latest enhancements and features but you need to ensure that your customizations stays in line with master and features can change from one day to another.
    • Odoo has a more classical release plan : each version is supported for three years and only bugfixes seems to be allowed in a stable versions. That said, no migration script is provided (OCA OpenUpgrade project tries to handle this) and each major version needs an huge migration to be planned.
  2. Architecture : as already said, ERPNext goes to include many features, verticals too (already healthcare and education ones), that may be hidden after by customization. Goods points : coherence, quality and maintenance. On Odoo side, everything is very modular and you may only install contact management or project management on your database. But this can lead to fragmentation and testing complexities.
  3. Community and manpower : Odoo SA employs dozens of people on Odoo. OCA and community is composed by hundreds of contributors. There are many (thousands) of modules existing. Frappé / ERPNext community is smaller, but growing.
  4. Features
    • ERPNext seems to offer more out-of-the-box than Odoo, especially in comparison to recent Odoo CE versions : contract / subscriptions, Gantt views, file management…
    • Odoo, with OCA repositories and other community modules, has a very large feature coverage and many of missing parts are filled that way. Out of the box, Odoo has more community oriented modules : surveys, forums, alternative to slack, mailing lists, slides (alternative to slideshare and youtube)…
  5. Framework
    • The Odoo framework needs a lot of Python and XML and a few JavaScript. The templating engine is QWeb, using XML attributes. It’s a productive business framework with includes many useful things, like good research and regroupments abilities, pivot table, charts, many views per model… Graphical customization is very limited and technical in CE version (in EE /closed source version, you have Odoo Studio…). Odoo v10 CE has no responsive backend theme nor mobile application by default (only frontend / website is responsive). The API is XML or JSON-RPC.
    • Frappé framework is more balanced between Python and JavaScript. It uses JSON massively but you don’t write it directly. Frappé is the popular Jinja templating engine on Python side. Frappé includes many graphical customizations. It can finished technical but less than Odoo CE offering. Frappé has good options for own reporting and PDF drag&drop personalization. It also offer Web Forms, realtime, universal command bar… Frappé is mobile focused with responsive backend and have open source mobile applications. The API is REST + optional RPC.
  6. Governance (last but not least)
    • Odoo is leaded by a company. Roadmap is not public and you can have surprises a few days before each new version. Odoo SA sells SaaS and services like implementation / development. It provides a partner program. Since 2015 and Odoo v9, there is an open source edition, Odoo CE and an enterprise proprietary edition, Odoo EE (that is Odoo CE + extra closed source modules). Migration code between major version is not open source, for many tears. OCA, Odoo Community Association, is a swiss non-profit foundation which coordinates open source community development, events… and manages quality software that enhances Odoo CE, add new features etc.
    • ERPNext is now driven by a non profit Indian Foundation. Roadmap is public and openly debated. All the code is open source, migration scripts included. The foundation handles events, promotion… and has its own developers. Frappé Tech still dominates ERPNext work, as the foundation is young and the number of contributors still low (but growing). Frappé Tech mainly offer SaaS hosting and is not a direct competitor for service providers.
Hope this is useful and quite objective. Feel free to amend / debate.

Thursday, November 08, 2018

Install and Configure Postfix as a Send-Only SMTP Server on Ubuntu 14.04


Postfix is an MTA (Mail Transfer Agent), an application used to send and receive email. In this tutorial, we will install and configure Postfix so that it can be used to send emails by local applications only – that is, those installed on the same server that Postfix is installed on.
Why would you want to do that?
If you're already using a third-party email provider for sending and receiving emails, you, of course, do not need to run your own mail server. However, if you manage a cloud server on which you have installed applications that need to send email notifications, running a local, send-only SMTP server is a good alternative to using a 3rd party email service provider or running a full-blown SMTP server.
An example of an application that sends email notifications is OSSEC, which will send email alerts to any configured email address (see How To Install and Configure OSSEC Security Notifications on Ubuntu 14.04). Though OSSEC or any other application of its kind can use a third-party email provider's SMTP server to send email alerts, it can also use a local (send-only) SMTP server.
That's what you'll learn how to do in this tutorial: how to install and configure Postfix as a send-only SMTP server.
Note: If your use case is to receive notifications from your server at a single address, emails being marked as spam is not a significant issue, since you can whitelist them.
If your use case is to send emails to potential site users, such as confirmation emails for message board sign-ups, you should definitely do Step 5 so your server's emails are more likely to be seen as legitimate. If you're still having problems with your server's emails being marked as spam, you will need to do further troubleshooting on your own.


Please complete the following prerequisites.
  • Ubuntu 14.04 Droplet
  • Go through the initial setup. That means you should have a standard user account with sudoprivileges
  • Have a valid domain name, like, pointing to your Droplet
  • Your server's hostname should match this domain or subdomain. You can verify the server's hostname by typing hostname at the command prompt. The output should match the name you gave the Droplet when it was being created, such as
If all the prerequisites have been met, you're now ready for the first step of this tutorial.

Step 1 — Install Postfix

In this step, you'll learn how to install Postfix. The most efficient way to install Postfix and other programs needed for testing email is to install the mailutils package by typing:
sudo apt-get install mailutils
Installing mailtuils will also cause Postfix to be installed, as well as a few other programs needed for Postfix to function. After typing that command, you will be presented with output that reads something like:
The following NEW packages will be installed:
guile-2.0-libs libgsasl7 libkyotocabinet16 libltdl7 liblzo2-2 libmailutils4 libmysqlclient18 libntlm0 libunistring0 mailutils mailutils-common mysql-common postfix ssl-cert

0 upgraded, 14 newly installed, 0 to remove and 3 not upgraded.
Need to get 5,481 kB of archives.
After this operation, 26.9 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Press ENTER to install them. Near the end of the installation process, you will be presented with a window that looks exactly like the one in the image below. The default option is Internet Site. That's the recommended option for this tutorial, so press TAB, then ENTER.
Select Internet Site from the menu, then press TAB to select <Ok>, then ENTER
After that, you'll get another window just like the one in this next image. The System mail name should be the same as the name you assigned to the Droplet when you were creating it. If it shows a subdomain like, change it to just When you're done, Press TAB, then ENTER.
Enter your domain name, then press TAB to select <Ok>, ENTER
After installation has completed successfully, proceed to Step 2.

Step 2 — Configure Postfix

In this step, you'll read how to configure Postfix to process requests to send emails only from the server on which it is running, that is, from localhost. For that to happen, Postfix needs to be configured to listen only on the loopback interface, the virtual network interface that the server uses to communicate internally. To make the change, open the main Postfix configuration file using the nano editor.
sudo nano /etc/postfix/
With the file open, scroll down until you see the entries shown in this code block.
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
Change the line that reads inet_interfaces = all to inet_interfaces = loopback-only. When you're done, that same section of the file should now read:
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = loopback-only
In place of loopback-only you may also use localhost, so that the modified section may also read:
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = localhost
When you're done editing the file, save and close it (press CTRL+X, followed by pressing Y, then ENTER). After that, restart Postfix by typing:
sudo service postfix restart

Step 3 — Test That the SMTP Server Can Send Emails

In this step, you'll read how to test whether Postfix can send emails to any external email account. You'll be using the mail command, which is part of the mailutils package that was installed in Step 1.
To send a test email, type:
echo "This is the body of the email" | mail -s "This is the subject line"
In performing your own test(s), you may use the body and subject line text as-is, or change them to your liking. However, in place of, use a valid email address, where the domain part can be, or any other email service provider that you use.
Now check the email address where you sent the test message.
You should see the message in your inbox. If not, check your spam folder.
Note: With this configuration, the address in the From field for the test emails you send will be, where sammy is your Linux username and the domain part is the server's hostname. If you change your username, the From address will also change.

Step 4 — Forward System Mail

The last thing we want to set up is forwarding, so that you'll get emails sent to root on the system at your personal, external email address.
To configure Postfix so that system-generated emails will be sent to your email address, you need to edit the /etc/aliases file.
sudo nano /etc/aliases
The full content of the file on a default installation of Ubuntu 14.04 is shown in this code block:
# See man 5 aliases for format
postmaster:    root
With that setting, system generated emails are sent to the root user. What you want to do is edit it so that those emails are rerouted to your email address. To accomplish that, edit the file so that it reads:
# See man 5 aliases for format
postmaster:    root
Replace with your personal email address. When done, save and close the file. For the change to take effect, run the following command:
sudo newaliases
You may now test that it works by sending an email to the root account using:
echo "This is the body of the email" | mail -s "This is the subject line" root
You should receive the email at your email address. If not, check your spam folder.

(Optional) Step 5 — Protect Your Domain from Spammers

In this step, you'll be given links to articles to help you protect your domain from being used for spamming. This is an optional but highly recommended step, because if configured correctly, this makes it difficult to send spam with an address that appears to originate from your domain.
Doing these additional configuration steps will also make it more likely for common mail providers to see emails from your server as legitimate, rather than marking them as spam.
Though the second article was written for Debian Wheezy, the same steps apply for Ubuntu 14.04.