Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Re: How and in what typical environments is Community Odoo begin used
    Hi Kitti

    We met in HK event long time back, not sure if you remember :)

    Yes I remember :-)

    To us, we are not opposing EE, we also try to propose it when possible. But so far, only small companies that can adapt to EE can use it. For big organizations, or more complicated requirements, it is required to use CE + OCA addons.

    Very interesting that you say  EE is only for smaller companies? We find that the EE finance module is a must-have for most organisations unless we interface to XERO etc (small organisations). Some companies actually just feel "safer" going with EE because of the perceived Odoo corporate backing which is especially important when coming up against Netsuite, Navision, SAP B1 etc. CE finance additions are great but the EE versions are an easier sell (my experience anyway). Of course, mis_builder is always in my sales kitbag.

    For custom vertical work not requiring full accounting, I agree that CE is a great choice and we have used it for that purpose.

    But beside that, it is just enjoyable to work with OCA people.

    Absolutely agree.
     
    Would be nice if functional expert like yourself is around too!

    I'd love to contribute more but time gets the better of me generally - family, house-painting, lawns, oh and working also. (the community is so knowledgeable I fell slightly intimidated sort-of)

    Thank you for your comments.

    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd





    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"


    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.




    On Thu, 23 Apr 2020 at 23:27, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
    Hi Jonathan, hope you do well,

    We met in HK event long time back, not sure if you remember :)

    To us, we are not opposing EE, we also try to propose it when possible. But so far, only small companies that can adapt to EE can use it. For big organizations, or more complicated requirements, it is required to use CE + OCA addons.

    But beside that, it is just enjoyable to work with OCA people. Would be nice if functional expert like yourself is around too!

    Note: Not sure exactly what is your question, but I believe you are welcome to discuss here.

    Kind regards,
    Kitti U.

    On Thu, Apr 23, 2020 at 4:12 AM Jonathan Wilson <jonathan.wilson@willdooit.com> wrote:
    Thank you for your feedback everybody - interesting. This is probably not the forum to continue the discussion I guess?

    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd





    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"


    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.




    On Wed, 22 Apr 2020 at 17:17, Rémi CAZENAVE - Le Filament <remi@le-filament.com> wrote:

    Hi Jonathan, all,

    Funny enough I had a discussion a few months back with an Odoo integrator working with Odoo enterprise only, and he was arguing this is where the revenue was (and did not understand why we would not become an Odoo partner).

    At Le Filament we have the opposite approach, working exclusively with Open Source softwares, so only with Odoo Community version, and we still have decent revenue :)

    Our strategy is somehow different though, since we are not selling Odoo software but rather an adapted solution for our customers (based on Odoo but most of our customers are not coming to us looking for Odoo).

    We spend time at the beginning of projects involving all future users, to determine how they expect the tool that will accompany them to work, then we install Odoo and make the necessary integration / configuration / development to fit their needs.

     

    So far we have installed Odoo Community for 30+ customers (from 2 to 200 users) and seldomly we have to send them to an Odoo Enterprise integrator (it happened though when they were already convinced that Odoo Enterprise was what they needed).

    Regarding Accounting functionalities, most of our customers do not use it extensively in Odoo but work with an Accounting partner or internal service (with their own specialized accounting tool) which are fed with exports from Odoo journals (mainly Sales, Purchase, Expense and POS), so I could not answer whether full accounting can be properly done in Community version, although I do not see any show stoppers.

    Best Regards,


    Le Filament Rémi CAZENAVE
    ------
    SCOP LE FILAMENT
    06 87 23 26 04
    remi@le-filament.com

    Le 2020-04-21 23:32, Jonathan Wilson a écrit :

    Hi All
     
    I love watching all the email go back and forth in this forum and only pretend to know what you are all talking about but coming from a solid commercial programming background myself (no python :-) I understand in general terms but don't feel qualified to comment except maybe from a functional perspective at times.
     
    At WilldooIT we are fairly firmly placed in the Odoo enterprise world as the commercial reality is that is where the revenue is. However, I do realise that the community version is very functional in its own right especially in the basic ERP functionalities and front-end capabilities. In this forum, I get the impression that there are some serious implementations of the Odoo community version and was wondering if you could give me some examples or typical use-cases? And if the lask of the enterprise accounting features is the main reason customers move to Odoo enterprise, and if the OCA financial reporting modules sufficient for larger companies.
     
    I must admit to feeling a bit guilty writing this as I once promised Maxime Chambreuil to approach Australian universities and Tech schools to get Odoo introduced as a learning tool for both the IT and Finance streams. I think it is a great idea and I have made a couple of attempts but time seemed to get the better of me - apologies Maxime, I will keep trying.
     
    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd

     
     
     
    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"

    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.
     
     
     

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Jonathan Wilson - 12:36 - 24 Apr 2020
  • Re: Yet another followup module ?
    Hi Alexis,

    Nice module, and great explanatory video.

    It's true the current credit_control module is complex yet useful for high volume applications as you noted.

    IMO, there is room for having both in OCA, provided the README of the repo explains why both modules exist.
    So I think it would be a welcome addition to OCA/credit-control.

    Best regards,

    --
    Stéphane Bidoul | @SBidoul
    Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

    On Wed, Apr 22, 2020 at 12:22 PM Alexis de Lattre <alexis.delattre@akretion.com> wrote:
    Dear OCA friends,

    I published yesterday a new module called Overdue Invoice Reminder (technical name : account_invoice_overdue_reminder) :


    It is an alternative to the OCA module account_credit_control available on https://github.com/OCA/credit-control (was in OCA/account-financial-tools for v10 and under)

    If you want to have a demo of my new module, please look at my screencast :

    Why did I decide to develop "yet another module" for followup ? Because I deployed the account_credit_control module for several companies (in v10), and the experience was not very positive, and they all stopped using it shortly after the deployment. My feeling about this OCA module is that it is like an army tank designed to send millions of followup letters ; the usability is not so good and it's not possible to customize the email/letters. Also, this module is very big (1900 line of python code) and difficult to modify because it is quite complex. That's why I decided to start the development of a new module from scratch. My main goals were:
    - give full control on the overdue email/letters to the user,
    - usability and easy the understand,
    - simplicity (700 lines of Python code, easy to read and understand),
    - reminders by email by default, with the possibility to also send letters and make phone calls.

    Please look at the README of the module for more info about the module (and its limitations) :

    I haven't submitted this module to OCA because of the rule "1 module per feature". But, if you think that this module should be in OCA, I'm ready to submit it. Anyway, your feedback on this module is welcomed. But don't forget that I want to KEEP THIS MODULE SIMPLE, so I may refuse features that add too much complexity.

    P.S. : I plan to backport this module to v10 after the first feedbacks.

    --
    Alexis de Lattre
    Akretion France - 27 rue Henri Rolland - 69100 Villeurbanne - France
    Mail : alexis.delattre@akretion.com
    Mobile : +33 6 99 08 92 45

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Stéphane Bidoul - 05:31 - 23 Apr 2020
  • Re: stock-logistics-barcode OCA module application

    Check server logs and/or the browser dev tools for errors, without that it is hard to say what's the issue.

    The config is not cached but you should restart the server so that it is applied.

    Regards,

    Kiril

    On 23.4.20 17:12, Harold luzardo wrote:
    Thanks Kiril,

    I replicate what you said, but once I click on app button I ending in a page with no menus on the top of the screen just my logo and that's it :( looks like the page is not loading completely if I go back and remove the added path everything works fine again, By any chance is there like a cache or so that keeps the previous config saved?

    Thanks for all your help.



    On Thu, Apr 23, 2020 at 10:07 AM Kiril Vangelovski <kiril@lambda-is.com> wrote:
    Hi Harold,

The modules should be in the root path of the directory that you've 
added in addons_path.

If they are not you should add the additional path specifically even 
though it is a child. Example:

addons_path = 
/opt/odoo/odoo/addons,/mnt/extra-addons,/mnt/extra-addons/stock-logistics-barcode

Regards,

Kiril

On 23.4.20 15:52, Harold luzardo wrote:


> Hello there,


>


> I try to install the OCA module stock-logistics-barcode[1] for version 


> 11, I have git clone the repository and place it into extra-addons 


> folder, I went back to my Odoo and using the debug action I refresh my 


> application list, but I'm not able to see listed this module. 


> Searching and asking a bit I have tried restarting the server and 


> checking the __manufest__.py installable: True status[2]. I have other 


> modules that are placed in that same path folder (extra-addons) and 


> they are working fine, showing and updating correctly, but for some 


> reason, I'm not able to have this one working, definitely, I'm doing 


> or missing something but as a good NEWBIE that I'm I don't what it is.


>


> Thanks for your help


>


> Regards,


>


> [1]https://github.com/OCA/stock-logistics-barcode/tree/11.0


>


> [2]


> ./stock_scanner/__manifest__.py:  'installable': True,


> ./stock_barcodes/__manifest__.py:    "installable": True,


> ./stock_barcodes_supplierinfo/__manifest__.py:  "installable": True,


> ./product_supplierinfo_barcode/__manifest__.py:  "installable": True,


> ./base_gs1_barcode/__manifest__.py:    'installable': True,


> ./stock_barcodes_gs1/__manifest__.py:    'installable': True,


> ./product_multi_ean/__manifest__.py:    'installable': True,


> ./stock_barcodes_gs1_expiry/__manifest__.py:    'installable': True,


>


> -- 


> -- 


> Harold g Luzardo b


> @Kickfliph


> GNU/Linux User #535193


> pub   2048R/0BCF3A23 2014-06-08


> Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23


>


> _______________________________________________


> Mailing-List: https://odoo-community.org/groups/contributors-15


> Post to: mailto:contributors@odoo-community.org


> Unsubscribe: https://odoo-community.org/groups?unsubscribe


>


-- 
Lambda IS DOOEL - free/open-source information systems implementation & development

Kiril Vangelovski - consultant/developer

web: https://www.lambda-is.com
tel: +38971753823

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    --
    Harold g Luzardo b
    @Kickfliph
    GNU/Linux User #535193
    pub   2048R/0BCF3A23 2014-06-08
    Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
Lambda IS DOOEL - free/open-source information systems implementation & development

Kiril Vangelovski - consultant/developer 

web: https://www.lambda-is.com
tel: +38971753823
    by Kiril Vangelovski - 05:26 - 23 Apr 2020
  • Re: stock-logistics-barcode OCA module application
    Thanks Kiril,

    I replicate what you said, but once I click on app button I ending in a page with no menus on the top of the screen just my logo and that's it :( looks like the page is not loading completely if I go back and remove the added path everything works fine again, By any chance is there like a cache or so that keeps the previous config saved?

    Thanks for all your help.



    On Thu, Apr 23, 2020 at 10:07 AM Kiril Vangelovski <kiril@lambda-is.com> wrote:
    Hi Harold,

The modules should be in the root path of the directory that you've 
added in addons_path.

If they are not you should add the additional path specifically even 
though it is a child. Example:

addons_path = 
/opt/odoo/odoo/addons,/mnt/extra-addons,/mnt/extra-addons/stock-logistics-barcode

Regards,

Kiril

On 23.4.20 15:52, Harold luzardo wrote:


> Hello there,


>


> I try to install the OCA module stock-logistics-barcode[1] for version 


> 11, I have git clone the repository and place it into extra-addons 


> folder, I went back to my Odoo and using the debug action I refresh my 


> application list, but I'm not able to see listed this module. 


> Searching and asking a bit I have tried restarting the server and 


> checking the __manufest__.py installable: True status[2]. I have other 


> modules that are placed in that same path folder (extra-addons) and 


> they are working fine, showing and updating correctly, but for some 


> reason, I'm not able to have this one working, definitely, I'm doing 


> or missing something but as a good NEWBIE that I'm I don't what it is.


>


> Thanks for your help


>


> Regards,


>


> [1]https://github.com/OCA/stock-logistics-barcode/tree/11.0


>


> [2]


> ./stock_scanner/__manifest__.py:  'installable': True,


> ./stock_barcodes/__manifest__.py:    "installable": True,


> ./stock_barcodes_supplierinfo/__manifest__.py:  "installable": True,


> ./product_supplierinfo_barcode/__manifest__.py:  "installable": True,


> ./base_gs1_barcode/__manifest__.py:    'installable': True,


> ./stock_barcodes_gs1/__manifest__.py:    'installable': True,


> ./product_multi_ean/__manifest__.py:    'installable': True,


> ./stock_barcodes_gs1_expiry/__manifest__.py:    'installable': True,


>


> -- 


> -- 


> Harold g Luzardo b


> @Kickfliph


> GNU/Linux User #535193


> pub   2048R/0BCF3A23 2014-06-08


> Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23


>


> _______________________________________________


> Mailing-List: https://odoo-community.org/groups/contributors-15


> Post to: mailto:contributors@odoo-community.org


> Unsubscribe: https://odoo-community.org/groups?unsubscribe


>


-- 
Lambda IS DOOEL - free/open-source information systems implementation & development

Kiril Vangelovski - consultant/developer

web: https://www.lambda-is.com
tel: +38971753823

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    --
    Harold g Luzardo b
    @Kickfliph
    GNU/Linux User #535193
    pub   2048R/0BCF3A23 2014-06-08
    Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23
    by Harold Burton - 05:11 - 23 Apr 2020
  • Re: stock-logistics-barcode OCA module application 
    Hi Harold,

The modules should be in the root path of the directory that you've 
added in addons_path.

If they are not you should add the additional path specifically even 
though it is a child. Example:

addons_path = 
/opt/odoo/odoo/addons,/mnt/extra-addons,/mnt/extra-addons/stock-logistics-barcode

Regards,

Kiril

On 23.4.20 15:52, Harold luzardo wrote:

> Hello there,

>

> I try to install the OCA module stock-logistics-barcode[1] for version 

> 11, I have git clone the repository and place it into extra-addons 

> folder, I went back to my Odoo and using the debug action I refresh my 

> application list, but I'm not able to see listed this module. 

> Searching and asking a bit I have tried restarting the server and 

> checking the __manufest__.py installable: True status[2]. I have other 

> modules that are placed in that same path folder (extra-addons) and 

> they are working fine, showing and updating correctly, but for some 

> reason, I'm not able to have this one working, definitely, I'm doing 

> or missing something but as a good NEWBIE that I'm I don't what it is.

>

> Thanks for your help

>

> Regards,

>

> [1]https://github.com/OCA/stock-logistics-barcode/tree/11.0

>

> [2]

> ./stock_scanner/__manifest__.py:  'installable': True,

> ./stock_barcodes/__manifest__.py:    "installable": True,

> ./stock_barcodes_supplierinfo/__manifest__.py:  "installable": True,

> ./product_supplierinfo_barcode/__manifest__.py:  "installable": True,

> ./base_gs1_barcode/__manifest__.py:    'installable': True,

> ./stock_barcodes_gs1/__manifest__.py:    'installable': True,

> ./product_multi_ean/__manifest__.py:    'installable': True,

> ./stock_barcodes_gs1_expiry/__manifest__.py:    'installable': True,

>

> -- 

> -- 

> Harold g Luzardo b

> @Kickfliph

> GNU/Linux User #535193

> pub   2048R/0BCF3A23 2014-06-08

> Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23

>

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe

>

-- 
Lambda IS DOOEL - free/open-source information systems implementation & development

Kiril Vangelovski - consultant/developer

web: https://www.lambda-is.com
tel: +38971753823
    by Kiril Vangelovski - 04:05 - 23 Apr 2020
  • stock-logistics-barcode OCA module application
    Hello there,

    I try to install the OCA module stock-logistics-barcode[1] for version 11, I have git clone the repository and place it into extra-addons folder, I went back to my Odoo and using the debug action I refresh my application list, but I'm not able to see listed this module. Searching and asking a bit I have tried restarting the server and checking the __manufest__.py installable: True status[2]. I have other modules that are placed in that same path folder (extra-addons) and they are working fine, showing and updating correctly, but for some reason, I'm not able to have this one working, definitely, I'm doing or missing something but as a good NEWBIE that I'm I don't what it is.

    Thanks for your help

    Regards,


    [2] 
    ./stock_scanner/__manifest__.py:    'installable': True,
    ./stock_barcodes/__manifest__.py:    "installable": True,
    ./stock_barcodes_supplierinfo/__manifest__.py:    "installable": True,
    ./product_supplierinfo_barcode/__manifest__.py:    "installable": True,
    ./base_gs1_barcode/__manifest__.py:    'installable': True,
    ./stock_barcodes_gs1/__manifest__.py:    'installable': True,
    ./product_multi_ean/__manifest__.py:    'installable': True,
    ./stock_barcodes_gs1_expiry/__manifest__.py:    'installable': True,

    --
    --
    Harold g Luzardo b
    @Kickfliph
    GNU/Linux User #535193
    pub   2048R/0BCF3A23 2014-06-08
    Key fingerprint = 842E 986F 2A7B A507 4F0B  4A0F A73D 5885 0BCF 3A23
    by Harold Burton - 03:51 - 23 Apr 2020
  • Re: How and in what typical environments is Community Odoo begin used
    Hi Jonathan, hope you do well,

    We met in HK event long time back, not sure if you remember :)

    To us, we are not opposing EE, we also try to propose it when possible. But so far, only small companies that can adapt to EE can use it. For big organizations, or more complicated requirements, it is required to use CE + OCA addons.

    But beside that, it is just enjoyable to work with OCA people. Would be nice if functional expert like yourself is around too!

    Note: Not sure exactly what is your question, but I believe you are welcome to discuss here.

    Kind regards,
    Kitti U.

    On Thu, Apr 23, 2020 at 4:12 AM Jonathan Wilson <jonathan.wilson@willdooit.com> wrote:
    Thank you for your feedback everybody - interesting. This is probably not the forum to continue the discussion I guess?

    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd





    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"


    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.




    On Wed, 22 Apr 2020 at 17:17, Rémi CAZENAVE - Le Filament <remi@le-filament.com> wrote:

    Hi Jonathan, all,

    Funny enough I had a discussion a few months back with an Odoo integrator working with Odoo enterprise only, and he was arguing this is where the revenue was (and did not understand why we would not become an Odoo partner).

    At Le Filament we have the opposite approach, working exclusively with Open Source softwares, so only with Odoo Community version, and we still have decent revenue :)

    Our strategy is somehow different though, since we are not selling Odoo software but rather an adapted solution for our customers (based on Odoo but most of our customers are not coming to us looking for Odoo).

    We spend time at the beginning of projects involving all future users, to determine how they expect the tool that will accompany them to work, then we install Odoo and make the necessary integration / configuration / development to fit their needs.

     

    So far we have installed Odoo Community for 30+ customers (from 2 to 200 users) and seldomly we have to send them to an Odoo Enterprise integrator (it happened though when they were already convinced that Odoo Enterprise was what they needed).

    Regarding Accounting functionalities, most of our customers do not use it extensively in Odoo but work with an Accounting partner or internal service (with their own specialized accounting tool) which are fed with exports from Odoo journals (mainly Sales, Purchase, Expense and POS), so I could not answer whether full accounting can be properly done in Community version, although I do not see any show stoppers.

    Best Regards,


    Le Filament Rémi CAZENAVE
    ------
    SCOP LE FILAMENT
    06 87 23 26 04
    remi@le-filament.com

    Le 2020-04-21 23:32, Jonathan Wilson a écrit :

    Hi All
     
    I love watching all the email go back and forth in this forum and only pretend to know what you are all talking about but coming from a solid commercial programming background myself (no python :-) I understand in general terms but don't feel qualified to comment except maybe from a functional perspective at times.
     
    At WilldooIT we are fairly firmly placed in the Odoo enterprise world as the commercial reality is that is where the revenue is. However, I do realise that the community version is very functional in its own right especially in the basic ERP functionalities and front-end capabilities. In this forum, I get the impression that there are some serious implementations of the Odoo community version and was wondering if you could give me some examples or typical use-cases? And if the lask of the enterprise accounting features is the main reason customers move to Odoo enterprise, and if the OCA financial reporting modules sufficient for larger companies.
     
    I must admit to feeling a bit guilty writing this as I once promised Maxime Chambreuil to approach Australian universities and Tech schools to get Odoo introduced as a learning tool for both the IT and Finance streams. I think it is a great idea and I have made a couple of attempts but time seemed to get the better of me - apologies Maxime, I will keep trying.
     
    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd

     
     
     
    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"

    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.
     
     
     

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Kitti Upariphutthiphong - 03:26 - 23 Apr 2020
  • Re: Yet another followup module ?
    Me too; I shared the difficult of using OCA module.

    Il 22/04/20 12:37, luc.demeyer@noviat.com ha scritto:

    I share the experience of Alexis on the complexity of the credit_control module hence I think there is a place for an easier to use alternative.

     

    From: Alexis de Lattre <alexis.delattre@akretion.com>
    Sent: Wednesday, 22 April 2020 12:22
    To: Contributors <contributors@odoo-community.org>
    Subject: Yet another followup module ?

     

    Dear OCA friends,

     

    I published yesterday a new module called Overdue Invoice Reminder (technical name : account_invoice_overdue_reminder) :

     

     

    It is an alternative to the OCA module account_credit_control available on https://github.com/OCA/credit-control (was in OCA/account-financial-tools for v10 and under)

     

    If you want to have a demo of my new module, please look at my screencast :

     

    Why did I decide to develop "yet another module" for followup ? Because I deployed the account_credit_control module for several companies (in v10), and the experience was not very positive, and they all stopped using it shortly after the deployment. My feeling about this OCA module is that it is like an army tank designed to send millions of followup letters ; the usability is not so good and it's not possible to customize the email/letters. Also, this module is very big (1900 line of python code) and difficult to modify because it is quite complex. That's why I decided to start the development of a new module from scratch. My main goals were:

    - give full control on the overdue email/letters to the user,

    - usability and easy the understand,

    - simplicity (700 lines of Python code, easy to read and understand),

    - reminders by email by default, with the possibility to also send letters and make phone calls.

     

    Please look at the README of the module for more info about the module (and its limitations) :

     

    I haven't submitted this module to OCA because of the rule "1 module per feature". But, if you think that this module should be in OCA, I'm ready to submit it. Anyway, your feedback on this module is welcomed. But don't forget that I want to KEEP THIS MODULE SIMPLE, so I may refuse features that add too much complexity.

     

    P.S. : I plan to backport this module to v10 after the first feedbacks.


    --

    Alexis de Lattre
    Akretion France - 27 rue Henri Rolland - 69100 Villeurbanne - France
    Mail : alexis.delattre@akretion.com

    Mobile : +33 6 99 08 92 45

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Antonio M. Vigliotti - 02:21 - 23 Apr 2020
  • Re: smtp server service
    Hi Lorenzo,

    I'll look into installing mail_outbound_static on odoo-community.org.

    -sbi

    On Thu, Apr 23, 2020 at 9:02 AM Lorenzo Battistini <elbaddy@gmail.com> wrote:
    Also, odoo-community.org should use mail_outbound_static.
    Below an example of email to "contributors@odoo-community.org" marked as SPAM because of failing DMARC.

    Can someone install it? Then you just need to set the fixed "from" address in the ir.mail_server, like "mailing@odoo-community.org"

    Thanks!


    image.png


    On Thu, 23 Apr 2020 at 08:47, Lorenzo Battistini <elbaddy@gmail.com> wrote:
    Hi Jordi,

    Odoo is not DMARC compliant. You can check the issues reported by Oleg for some history:

    In order to avoid messages sent by odoo to be marked as SPAM because of DMARC, you can use mail_outbound_static

    By the way, we use Mailgun too.

    Regards


    On Mon, 20 Apr 2020 at 20:37, Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello Community!

    Thanks again for the feedback.
    We put in place SPF, DKIM and DMARC policies.
    We need not to work them out so the emails sent from odoo are greenlit.

    I am falling deep into the DMARC reports :)

    Jordi

    Le jeu. 9 avr. 2020 à 02:02, Oleg Kuryan <oleg@ventor.tech> a écrit :
    Hello, Jordi,

    1. First of all you need to tell us how you setted up your Odoo to work via Gmail? And also what is version of Odoo you are using ?

    2. Also are you using standard Odoo capabilities of sending emails or you customized smth? Reason, standard Odoo works like this.
    - Imagine I have sent email to your email sales@yourdomain.com from my email address oleg@mydomain.com
    - A new opportunity is created that will send emails to all followers of sales team sales@yourdomain.com is mail alias to.
    Important! Odoo Standard will send email to followers FROM oleg@mydomain.com

    So actually it will be sending email from domain it is actually not controlling.

    Few things about it:
    - Generally speaking we do not know(nobody knows) if google likes when you do that way. My personal opinion is by doing that too often , you Gmail domain will loose ratings.
    - second thing - if on my email domain  oleg@mydomain.com DMARC is properly configured, than google will not send it. Because that is SPAM! Obviously it is spam when you try to pretend sending from not your domain 

    Just read this for more details. This is ongoing discussions in many other Odoo issues on GitHub (just quick Google) 

    Usually Olivier Dony is participant of this discussions as he is expert in this. You can find a lot of issues like this from Odoo side.

    So another important recommendation. Do not mix different type of emails in one provider.

    There are 3 types of mails you usually send:
    1) Personal - use Google apps for sending personal emails. Because that way you make sure this mails are isolated from other type of mails and your mailbox will not be marked as spammy because you sent content from Odoo through relay and some systems report it as non reliable and spammy(for different reasons). So sending your emails from Odoo through Gmail you have a risk that even your personal emails will become untrusted and will get into spam.

    2) Transactional mails - this is mails from Odoo, other automatic messages (like registration confirmation ). Use for this separate specialised transactional mail provider . Like mailgun. Simply for reason in point 1. "Do not place eggs in one basket"

    3) Mass mailing - never do it through Odoo that sends it through Gmail. Despite of the fact Odoo has mass mailing feature  you will compromise your domain very easily with mass mailing if use Gmail.  If you still want to use Odoo mass mailing, configure separate outgoing mail server for this (for example through mailgun or other transactional provider) 
    Or better, Use specialised massailing providers like Mailchimp for this. Because after reputation of your domain is lost it is very hard to restore it. So you will be getting into Spam even from your personal mails.

    Few things:
    1) If you do not have full time sys admin, do not setup your own mail server. It is very hard to maintain mail infrastructure as new mail server need to get good reputation before other mail providers will trust it. And that is long process. And with sending mails from Odoo through your vanilla installed postfix you will not get good reputation easily. Most likely you will get anti-reputation :)
    2) check your domain is not blacklisted 
    Reason , most mail providers when receiving mail automatically check for blacklists. And if it is blacklisted, it can be marked as spam.
    3) make sure DKIM is setted up properly on your domain 
    4) Make sure that SPF is defined for all your mailproviders you are going to use (Gmail, Mailgun, MailChimp and etc.). Every such mail provider has dedicated page how to configure this.
    5) DMARC yes, configure it also for stronger validation. Note that Odoo work bad with DMARC configured emails. There were few attempts like below from Community to fix behavior of Odoo , but it was always non accepted https://github.com/odoo/odoo/pull/20911

    Hope that all helps !





    On Thu, Apr 9, 2020, 1:06 AM Gustavo Valverde <gustavo@iterativo.do> wrote:
    A few keypoints:
    • Try having DKIM,SPF and DMARC
    • Make your signature on Odoo a text instead of an image (just in case your Odoo signature is different)
    • Use GMAIL relay server smtp-relay.gmail.com; just in case you're hitting your quota (not related to SPAM tough)
    • Amazon Simple Email Service is great for mass mailing https://aws.amazon.com/ses/
    Regards, 

    On Wed, Apr 8, 2020 at 5:27 PM Frederik Kramer <frederik.kramer@initos.com> wrote:
    Hi Jordi, 

the relative amount of mails going through Odoo is probably less
relevant than the absolut amount. Generally spoken i'd always suggest
to invest time in setting up an own mail Server instead of relaying
through GMail and if you really need to sent masses of uniform E-mail
probably going through an load balanced and properly scaling service
like mailchimp or mailgun would be devisable yes. I don't honestly know
but E-Mails going through Odoo will be easily identifiable by almost
every AI and that is probably the reason (in relation with the content
of the mails) being identified as SPAM

Best Frederik

Am Mittwoch, den 08.04.2020, 21:17 +0000 schrieb Jordi Riera:






> Hello list,






> 






> We use our Odoo extensively to send our emails. I just did the stats






> and 75% of our sent emails are from our Odoo.






> We are currently using gmail as our smtp service. We start to see






> some of our emails tagged as spam. We are wondering why.






> Have you ever faced the same problem?






> 






> Another question on the same topic, what do you use as SMTP service ?






> Would you advise to go to a simple local server or to go to a






> dedicated service provider like mailgun or something like that?






> 






> Again, thank you for all your answers. You are the best :)






> Take care.






> 






> Jordi






> 






-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    Gustavo Valverde

    Chief Technology Officer

    M (829) 686 8270 D  (829) 956 5191 ext. 202

    E  gustavo@iterativo.do


    ITERATIVO SRL

    Roble Corporate Center, Piso 7

    Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana


    T (829) 956 5191| E info@iterativo.do | www.iterativo.do


    Member firm of ITERATIVO LLC & Progressa Corporate Group


    Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial. 

    This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters. 

     

    https://iterativo.do/web/image/39802/hoja-verde.png

    No imprimas este correo si no es necesario. Cuidemos del ambiente!

    Do not print this mail if it's not necessary. Let's take care of the environment!

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribefma

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --


    --

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Stéphane Bidoul - 09:15 - 23 Apr 2020
  • Re: How and in what typical environments is Community Odoo begin used
    On Wed, 22 Apr 2020 at 09:26, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
    Odoo CE + OCA can perfectly serve for whole accounting and with powerful localizations like Spanish one (OCA/l10n-spain), it's even better than enterprise.

    This is true also for Italy


    --
    by Lorenzo Battistini. - 09:05 - 23 Apr 2020
  • Re: smtp server service
    Also, odoo-community.org should use mail_outbound_static.
    Below an example of email to "contributors@odoo-community.org" marked as SPAM because of failing DMARC.

    Can someone install it? Then you just need to set the fixed "from" address in the ir.mail_server, like "mailing@odoo-community.org"

    Thanks!


    image.png


    On Thu, 23 Apr 2020 at 08:47, Lorenzo Battistini <elbaddy@gmail.com> wrote:
    Hi Jordi,

    Odoo is not DMARC compliant. You can check the issues reported by Oleg for some history:

    In order to avoid messages sent by odoo to be marked as SPAM because of DMARC, you can use mail_outbound_static

    By the way, we use Mailgun too.

    Regards


    On Mon, 20 Apr 2020 at 20:37, Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello Community!

    Thanks again for the feedback.
    We put in place SPF, DKIM and DMARC policies.
    We need not to work them out so the emails sent from odoo are greenlit.

    I am falling deep into the DMARC reports :)

    Jordi

    Le jeu. 9 avr. 2020 à 02:02, Oleg Kuryan <oleg@ventor.tech> a écrit :
    Hello, Jordi,

    1. First of all you need to tell us how you setted up your Odoo to work via Gmail? And also what is version of Odoo you are using ?

    2. Also are you using standard Odoo capabilities of sending emails or you customized smth? Reason, standard Odoo works like this.
    - Imagine I have sent email to your email sales@yourdomain.com from my email address oleg@mydomain.com
    - A new opportunity is created that will send emails to all followers of sales team sales@yourdomain.com is mail alias to.
    Important! Odoo Standard will send email to followers FROM oleg@mydomain.com

    So actually it will be sending email from domain it is actually not controlling.

    Few things about it:
    - Generally speaking we do not know(nobody knows) if google likes when you do that way. My personal opinion is by doing that too often , you Gmail domain will loose ratings.
    - second thing - if on my email domain  oleg@mydomain.com DMARC is properly configured, than google will not send it. Because that is SPAM! Obviously it is spam when you try to pretend sending from not your domain 

    Just read this for more details. This is ongoing discussions in many other Odoo issues on GitHub (just quick Google) 

    Usually Olivier Dony is participant of this discussions as he is expert in this. You can find a lot of issues like this from Odoo side.

    So another important recommendation. Do not mix different type of emails in one provider.

    There are 3 types of mails you usually send:
    1) Personal - use Google apps for sending personal emails. Because that way you make sure this mails are isolated from other type of mails and your mailbox will not be marked as spammy because you sent content from Odoo through relay and some systems report it as non reliable and spammy(for different reasons). So sending your emails from Odoo through Gmail you have a risk that even your personal emails will become untrusted and will get into spam.

    2) Transactional mails - this is mails from Odoo, other automatic messages (like registration confirmation ). Use for this separate specialised transactional mail provider . Like mailgun. Simply for reason in point 1. "Do not place eggs in one basket"

    3) Mass mailing - never do it through Odoo that sends it through Gmail. Despite of the fact Odoo has mass mailing feature  you will compromise your domain very easily with mass mailing if use Gmail.  If you still want to use Odoo mass mailing, configure separate outgoing mail server for this (for example through mailgun or other transactional provider) 
    Or better, Use specialised massailing providers like Mailchimp for this. Because after reputation of your domain is lost it is very hard to restore it. So you will be getting into Spam even from your personal mails.

    Few things:
    1) If you do not have full time sys admin, do not setup your own mail server. It is very hard to maintain mail infrastructure as new mail server need to get good reputation before other mail providers will trust it. And that is long process. And with sending mails from Odoo through your vanilla installed postfix you will not get good reputation easily. Most likely you will get anti-reputation :)
    2) check your domain is not blacklisted 
    Reason , most mail providers when receiving mail automatically check for blacklists. And if it is blacklisted, it can be marked as spam.
    3) make sure DKIM is setted up properly on your domain 
    4) Make sure that SPF is defined for all your mailproviders you are going to use (Gmail, Mailgun, MailChimp and etc.). Every such mail provider has dedicated page how to configure this.
    5) DMARC yes, configure it also for stronger validation. Note that Odoo work bad with DMARC configured emails. There were few attempts like below from Community to fix behavior of Odoo , but it was always non accepted https://github.com/odoo/odoo/pull/20911

    Hope that all helps !





    On Thu, Apr 9, 2020, 1:06 AM Gustavo Valverde <gustavo@iterativo.do> wrote:
    A few keypoints:
    • Try having DKIM,SPF and DMARC
    • Make your signature on Odoo a text instead of an image (just in case your Odoo signature is different)
    • Use GMAIL relay server smtp-relay.gmail.com; just in case you're hitting your quota (not related to SPAM tough)
    • Amazon Simple Email Service is great for mass mailing https://aws.amazon.com/ses/
    Regards, 

    On Wed, Apr 8, 2020 at 5:27 PM Frederik Kramer <frederik.kramer@initos.com> wrote:
    Hi Jordi, 

the relative amount of mails going through Odoo is probably less
relevant than the absolut amount. Generally spoken i'd always suggest
to invest time in setting up an own mail Server instead of relaying
through GMail and if you really need to sent masses of uniform E-mail
probably going through an load balanced and properly scaling service
like mailchimp or mailgun would be devisable yes. I don't honestly know
but E-Mails going through Odoo will be easily identifiable by almost
every AI and that is probably the reason (in relation with the content
of the mails) being identified as SPAM

Best Frederik

Am Mittwoch, den 08.04.2020, 21:17 +0000 schrieb Jordi Riera:





> Hello list,





> 





> We use our Odoo extensively to send our emails. I just did the stats





> and 75% of our sent emails are from our Odoo.





> We are currently using gmail as our smtp service. We start to see





> some of our emails tagged as spam. We are wondering why.





> Have you ever faced the same problem?





> 





> Another question on the same topic, what do you use as SMTP service ?





> Would you advise to go to a simple local server or to go to a





> dedicated service provider like mailgun or something like that?





> 





> Again, thank you for all your answers. You are the best :)





> Take care.





> 





> Jordi





> 





-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    Gustavo Valverde

    Chief Technology Officer

    M (829) 686 8270 D  (829) 956 5191 ext. 202

    E  gustavo@iterativo.do


    ITERATIVO SRL

    Roble Corporate Center, Piso 7

    Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana


    T (829) 956 5191| E info@iterativo.do | www.iterativo.do


    Member firm of ITERATIVO LLC & Progressa Corporate Group


    Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial. 

    This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters. 

     

    https://iterativo.do/web/image/39802/hoja-verde.png

    No imprimas este correo si no es necesario. Cuidemos del ambiente!

    Do not print this mail if it's not necessary. Let's take care of the environment!

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribefma

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --


    --
    by Lorenzo Battistini. - 09:00 - 23 Apr 2020

    1 attachments 1 attachments

    image.png
  • Re: smtp server service
    Hi Jordi,

    Odoo is not DMARC compliant. You can check the issues reported by Oleg for some history:

    In order to avoid messages sent by odoo to be marked as SPAM because of DMARC, you can use mail_outbound_static

    By the way, we use Mailgun too.

    Regards


    On Mon, 20 Apr 2020 at 20:37, Jordi Riera <jordi.riera@numigi.com> wrote:
    Hello Community!

    Thanks again for the feedback.
    We put in place SPF, DKIM and DMARC policies.
    We need not to work them out so the emails sent from odoo are greenlit.

    I am falling deep into the DMARC reports :)

    Jordi

    Le jeu. 9 avr. 2020 à 02:02, Oleg Kuryan <oleg@ventor.tech> a écrit :
    Hello, Jordi,

    1. First of all you need to tell us how you setted up your Odoo to work via Gmail? And also what is version of Odoo you are using ?

    2. Also are you using standard Odoo capabilities of sending emails or you customized smth? Reason, standard Odoo works like this.
    - Imagine I have sent email to your email sales@yourdomain.com from my email address oleg@mydomain.com
    - A new opportunity is created that will send emails to all followers of sales team sales@yourdomain.com is mail alias to.
    Important! Odoo Standard will send email to followers FROM oleg@mydomain.com

    So actually it will be sending email from domain it is actually not controlling.

    Few things about it:
    - Generally speaking we do not know(nobody knows) if google likes when you do that way. My personal opinion is by doing that too often , you Gmail domain will loose ratings.
    - second thing - if on my email domain  oleg@mydomain.com DMARC is properly configured, than google will not send it. Because that is SPAM! Obviously it is spam when you try to pretend sending from not your domain 

    Just read this for more details. This is ongoing discussions in many other Odoo issues on GitHub (just quick Google) 

    Usually Olivier Dony is participant of this discussions as he is expert in this. You can find a lot of issues like this from Odoo side.

    So another important recommendation. Do not mix different type of emails in one provider.

    There are 3 types of mails you usually send:
    1) Personal - use Google apps for sending personal emails. Because that way you make sure this mails are isolated from other type of mails and your mailbox will not be marked as spammy because you sent content from Odoo through relay and some systems report it as non reliable and spammy(for different reasons). So sending your emails from Odoo through Gmail you have a risk that even your personal emails will become untrusted and will get into spam.

    2) Transactional mails - this is mails from Odoo, other automatic messages (like registration confirmation ). Use for this separate specialised transactional mail provider . Like mailgun. Simply for reason in point 1. "Do not place eggs in one basket"

    3) Mass mailing - never do it through Odoo that sends it through Gmail. Despite of the fact Odoo has mass mailing feature  you will compromise your domain very easily with mass mailing if use Gmail.  If you still want to use Odoo mass mailing, configure separate outgoing mail server for this (for example through mailgun or other transactional provider) 
    Or better, Use specialised massailing providers like Mailchimp for this. Because after reputation of your domain is lost it is very hard to restore it. So you will be getting into Spam even from your personal mails.

    Few things:
    1) If you do not have full time sys admin, do not setup your own mail server. It is very hard to maintain mail infrastructure as new mail server need to get good reputation before other mail providers will trust it. And that is long process. And with sending mails from Odoo through your vanilla installed postfix you will not get good reputation easily. Most likely you will get anti-reputation :)
    2) check your domain is not blacklisted 
    Reason , most mail providers when receiving mail automatically check for blacklists. And if it is blacklisted, it can be marked as spam.
    3) make sure DKIM is setted up properly on your domain 
    4) Make sure that SPF is defined for all your mailproviders you are going to use (Gmail, Mailgun, MailChimp and etc.). Every such mail provider has dedicated page how to configure this.
    5) DMARC yes, configure it also for stronger validation. Note that Odoo work bad with DMARC configured emails. There were few attempts like below from Community to fix behavior of Odoo , but it was always non accepted https://github.com/odoo/odoo/pull/20911

    Hope that all helps !





    On Thu, Apr 9, 2020, 1:06 AM Gustavo Valverde <gustavo@iterativo.do> wrote:
    A few keypoints:
    • Try having DKIM,SPF and DMARC
    • Make your signature on Odoo a text instead of an image (just in case your Odoo signature is different)
    • Use GMAIL relay server smtp-relay.gmail.com; just in case you're hitting your quota (not related to SPAM tough)
    • Amazon Simple Email Service is great for mass mailing https://aws.amazon.com/ses/
    Regards, 

    On Wed, Apr 8, 2020 at 5:27 PM Frederik Kramer <frederik.kramer@initos.com> wrote:
    Hi Jordi, 

the relative amount of mails going through Odoo is probably less
relevant than the absolut amount. Generally spoken i'd always suggest
to invest time in setting up an own mail Server instead of relaying
through GMail and if you really need to sent masses of uniform E-mail
probably going through an load balanced and properly scaling service
like mailchimp or mailgun would be devisable yes. I don't honestly know
but E-Mails going through Odoo will be easily identifiable by almost
every AI and that is probably the reason (in relation with the content
of the mails) being identified as SPAM

Best Frederik

Am Mittwoch, den 08.04.2020, 21:17 +0000 schrieb Jordi Riera:





> Hello list,





> 





> We use our Odoo extensively to send our emails. I just did the stats





> and 75% of our sent emails are from our Odoo.





> We are currently using gmail as our smtp service. We start to see





> some of our emails tagged as spam. We are wondering why.





> Have you ever faced the same problem?





> 





> Another question on the same topic, what do you use as SMTP service ?





> Would you advise to go to a simple local server or to go to a





> dedicated service provider like mailgun or something like that?





> 





> Again, thank you for all your answers. You are the best :)





> Take care.





> 





> Jordi





> 





-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    Gustavo Valverde

    Chief Technology Officer

    M (829) 686 8270 D  (829) 956 5191 ext. 202

    E  gustavo@iterativo.do


    ITERATIVO SRL

    Roble Corporate Center, Piso 7

    Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana


    T (829) 956 5191| E info@iterativo.do | www.iterativo.do


    Member firm of ITERATIVO LLC & Progressa Corporate Group


    Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial. 

    This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters. 

     

    https://iterativo.do/web/image/39802/hoja-verde.png

    No imprimas este correo si no es necesario. Cuidemos del ambiente!

    Do not print this mail if it's not necessary. Let's take care of the environment!

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribefma

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Jordi Riera - VP Technique
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    by Lorenzo Battistini. - 08:51 - 23 Apr 2020
  • Re: How and in what typical environments is Community Odoo begin used
    Thank you for your feedback everybody - interesting. This is probably not the forum to continue the discussion I guess?

    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd





    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"


    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.




    On Wed, 22 Apr 2020 at 17:17, Rémi CAZENAVE - Le Filament <remi@le-filament.com> wrote:

    Hi Jonathan, all,

    Funny enough I had a discussion a few months back with an Odoo integrator working with Odoo enterprise only, and he was arguing this is where the revenue was (and did not understand why we would not become an Odoo partner).

    At Le Filament we have the opposite approach, working exclusively with Open Source softwares, so only with Odoo Community version, and we still have decent revenue :)

    Our strategy is somehow different though, since we are not selling Odoo software but rather an adapted solution for our customers (based on Odoo but most of our customers are not coming to us looking for Odoo).

    We spend time at the beginning of projects involving all future users, to determine how they expect the tool that will accompany them to work, then we install Odoo and make the necessary integration / configuration / development to fit their needs.

     

    So far we have installed Odoo Community for 30+ customers (from 2 to 200 users) and seldomly we have to send them to an Odoo Enterprise integrator (it happened though when they were already convinced that Odoo Enterprise was what they needed).

    Regarding Accounting functionalities, most of our customers do not use it extensively in Odoo but work with an Accounting partner or internal service (with their own specialized accounting tool) which are fed with exports from Odoo journals (mainly Sales, Purchase, Expense and POS), so I could not answer whether full accounting can be properly done in Community version, although I do not see any show stoppers.

    Best Regards,


    Le Filament Rémi CAZENAVE
    ------
    SCOP LE FILAMENT
    06 87 23 26 04
    remi@le-filament.com

    Le 2020-04-21 23:32, Jonathan Wilson a écrit :

    Hi All
     
    I love watching all the email go back and forth in this forum and only pretend to know what you are all talking about but coming from a solid commercial programming background myself (no python :-) I understand in general terms but don't feel qualified to comment except maybe from a functional perspective at times.
     
    At WilldooIT we are fairly firmly placed in the Odoo enterprise world as the commercial reality is that is where the revenue is. However, I do realise that the community version is very functional in its own right especially in the basic ERP functionalities and front-end capabilities. In this forum, I get the impression that there are some serious implementations of the Odoo community version and was wondering if you could give me some examples or typical use-cases? And if the lask of the enterprise accounting features is the main reason customers move to Odoo enterprise, and if the OCA financial reporting modules sufficient for larger companies.
     
    I must admit to feeling a bit guilty writing this as I once promised Maxime Chambreuil to approach Australian universities and Tech schools to get Odoo introduced as a learning tool for both the IT and Finance streams. I think it is a great idea and I have made a couple of attempts but time seemed to get the better of me - apologies Maxime, I will keep trying.
     
    Kind regards

    Jonathan Wilson

    Chief Sales and Innovation Executive

    WilldooIT Pty Ltd

     
     
     
    First Australian Odoo GOLD partner
    2017, 2015 & 2013 Odoo Best Partner Asia/Pacific
    Creators of  Odoo-Pentaho integration project

    "Making growth through technology easy"

    E: jonathan.wilson@willdooit.com

    P: +61 3 9135 1900

    M: +61  4 000 17 444

    Linkedin

    10/435 Williamstown Road

    Port Melbourne VIC 3207

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by Willdoo IT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.
     
     
     

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Jonathan Wilson - 11:11 - 22 Apr 2020
  • Crowdfunding? Again 
    Dear community,

There was a question about crowdfunding specific fixes or migrations year or so ago. At that time it did not find any support, if I recall correctly, yet I’d like to resurface it and start a discussion about OCA setting up any suitable platform of fund-an-issue using GitHub.

Kind regards,
Alexey
    by Alexey Pelykh <alexey.pelykh@gmail.com> - 02:15 - 22 Apr 2020
  • Re: Yet another followup module ?
    Hi all,

    Thanks a lot for this module and this video really self explained

    +1 to put into OCA with excludes key in manifest

    Bonne journée


    David BEAL - akretion.com
    Chef de projet
    Odoo Développement / Intégration


    Le mer. 22 avr. 2020 à 13:17, Graeme Gellatly <gdgellatly@gmail.com> a écrit :
    Evolution vs revolution. Only 1 can be done easily inside OCA for a non original contributor. Indeed I imagine that is the genesis of the 1 module rule, to support evolution and discourage revolution. 

    So when you disagree with a long established and regularly migrated module, I wholeheartedly agree with Alexis approach.

    Do it, then worry about the rest later.

    I support the rule, but I'm aware it is a tradeoff between 2 approaches.

    On Wed, 22 Apr 2020, 10:42 pm Roussel, Denis, <denis.roussel@acsone.eu> wrote:
    Great!

    But one question comes into my mind.

    Why not having proposed a refactor of existing module to split functionalities in different modules in order to allow user choosing the ones he wants to use ?

    On Wed, Apr 22, 2020 at 12:22 PM Alexis de Lattre <alexis.delattre@akretion.com> wrote:
    Dear OCA friends,

    I published yesterday a new module called Overdue Invoice Reminder (technical name : account_invoice_overdue_reminder) :


    It is an alternative to the OCA module account_credit_control available on https://github.com/OCA/credit-control (was in OCA/account-financial-tools for v10 and under)

    If you want to have a demo of my new module, please look at my screencast :

    Why did I decide to develop "yet another module" for followup ? Because I deployed the account_credit_control module for several companies (in v10), and the experience was not very positive, and they all stopped using it shortly after the deployment. My feeling about this OCA module is that it is like an army tank designed to send millions of followup letters ; the usability is not so good and it's not possible to customize the email/letters. Also, this module is very big (1900 line of python code) and difficult to modify because it is quite complex. That's why I decided to start the development of a new module from scratch. My main goals were:
    - give full control on the overdue email/letters to the user,
    - usability and easy the understand,
    - simplicity (700 lines of Python code, easy to read and understand),
    - reminders by email by default, with the possibility to also send letters and make phone calls.

    Please look at the README of the module for more info about the module (and its limitations) :

    I haven't submitted this module to OCA because of the rule "1 module per feature". But, if you think that this module should be in OCA, I'm ready to submit it. Anyway, your feedback on this module is welcomed. But don't forget that I want to KEEP THIS MODULE SIMPLE, so I may refuse features that add too much complexity.

    P.S. : I plan to backport this module to v10 after the first feedbacks.

    --
    Alexis de Lattre
    Akretion France - 27 rue Henri Rolland - 69100 Villeurbanne - France
    Mail : alexis.delattre@akretion.com
    Mobile : +33 6 99 08 92 45

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 34 64

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by David BEAL - 01:36 - 22 Apr 2020
  • Re: Yet another followup module ?
    Evolution vs revolution. Only 1 can be done easily inside OCA for a non original contributor. Indeed I imagine that is the genesis of the 1 module rule, to support evolution and discourage revolution. 

    So when you disagree with a long established and regularly migrated module, I wholeheartedly agree with Alexis approach.

    Do it, then worry about the rest later.

    I support the rule, but I'm aware it is a tradeoff between 2 approaches.

    On Wed, 22 Apr 2020, 10:42 pm Roussel, Denis, <denis.roussel@acsone.eu> wrote:
    Great!

    But one question comes into my mind.

    Why not having proposed a refactor of existing module to split functionalities in different modules in order to allow user choosing the ones he wants to use ?

    On Wed, Apr 22, 2020 at 12:22 PM Alexis de Lattre <alexis.delattre@akretion.com> wrote:
    Dear OCA friends,

    I published yesterday a new module called Overdue Invoice Reminder (technical name : account_invoice_overdue_reminder) :


    It is an alternative to the OCA module account_credit_control available on https://github.com/OCA/credit-control (was in OCA/account-financial-tools for v10 and under)

    If you want to have a demo of my new module, please look at my screencast :

    Why did I decide to develop "yet another module" for followup ? Because I deployed the account_credit_control module for several companies (in v10), and the experience was not very positive, and they all stopped using it shortly after the deployment. My feeling about this OCA module is that it is like an army tank designed to send millions of followup letters ; the usability is not so good and it's not possible to customize the email/letters. Also, this module is very big (1900 line of python code) and difficult to modify because it is quite complex. That's why I decided to start the development of a new module from scratch. My main goals were:
    - give full control on the overdue email/letters to the user,
    - usability and easy the understand,
    - simplicity (700 lines of Python code, easy to read and understand),
    - reminders by email by default, with the possibility to also send letters and make phone calls.

    Please look at the README of the module for more info about the module (and its limitations) :

    I haven't submitted this module to OCA because of the rule "1 module per feature". But, if you think that this module should be in OCA, I'm ready to submit it. Anyway, your feedback on this module is welcomed. But don't forget that I want to KEEP THIS MODULE SIMPLE, so I may refuse features that add too much complexity.

    P.S. : I plan to backport this module to v10 after the first feedbacks.

    --
    Alexis de Lattre
    Akretion France - 27 rue Henri Rolland - 69100 Villeurbanne - France
    Mail : alexis.delattre@akretion.com
    Mobile : +33 6 99 08 92 45

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 34 64

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Graeme Gellatly - 01:15 - 22 Apr 2020
  • Re: Yet another followup module ?
    Great!

    But one question comes into my mind.

    Why not having proposed a refactor of existing module to split functionalities in different modules in order to allow user choosing the ones he wants to use ?

    On Wed, Apr 22, 2020 at 12:22 PM Alexis de Lattre <alexis.delattre@akretion.com> wrote:
    Dear OCA friends,

    I published yesterday a new module called Overdue Invoice Reminder (technical name : account_invoice_overdue_reminder) :


    It is an alternative to the OCA module account_credit_control available on https://github.com/OCA/credit-control (was in OCA/account-financial-tools for v10 and under)

    If you want to have a demo of my new module, please look at my screencast :

    Why did I decide to develop "yet another module" for followup ? Because I deployed the account_credit_control module for several companies (in v10), and the experience was not very positive, and they all stopped using it shortly after the deployment. My feeling about this OCA module is that it is like an army tank designed to send millions of followup letters ; the usability is not so good and it's not possible to customize the email/letters. Also, this module is very big (1900 line of python code) and difficult to modify because it is quite complex. That's why I decided to start the development of a new module from scratch. My main goals were:
    - give full control on the overdue email/letters to the user,
    - usability and easy the understand,
    - simplicity (700 lines of Python code, easy to read and understand),
    - reminders by email by default, with the possibility to also send letters and make phone calls.

    Please look at the README of the module for more info about the module (and its limitations) :

    I haven't submitted this module to OCA because of the rule "1 module per feature". But, if you think that this module should be in OCA, I'm ready to submit it. Anyway, your feedback on this module is welcomed. But don't forget that I want to KEEP THIS MODULE SIMPLE, so I may refuse features that add too much complexity.

    P.S. : I plan to backport this module to v10 after the first feedbacks.

    --
    Alexis de Lattre
    Akretion France - 27 rue Henri Rolland - 69100 Villeurbanne - France
    Mail : alexis.delattre@akretion.com
    Mobile : +33 6 99 08 92 45

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 34 64

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
    by Denis Roussel - 12:41 - 22 Apr 2020
  • RE: Yet another followup module ?

    I share the experience of Alexis on the complexity of the credit_control module hence I think there is a place for an easier to use alternative.

     

    From: Alexis de Lattre <alexis.delattre@akretion.com>
    Sent: Wednesday, 22 April 2020 12:22
    To: Contributors <contributors@odoo-community.org>
    Subject: Yet another followup module ?

     

    Dear OCA friends,

     

    I published yesterday a new module called Overdue Invoice Reminder (technical name : account_invoice_overdue_reminder) :

     

     

    It is an alternative to the OCA module account_credit_control available on https://github.com/OCA/credit-control (was in OCA/account-financial-tools for v10 and under)

     

    If you want to have a demo of my new module, please look at my screencast :

     

    Why did I decide to develop "yet another module" for followup ? Because I deployed the account_credit_control module for several companies (in v10), and the experience was not very positive, and they all stopped using it shortly after the deployment. My feeling about this OCA module is that it is like an army tank designed to send millions of followup letters ; the usability is not so good and it's not possible to customize the email/letters. Also, this module is very big (1900 line of python code) and difficult to modify because it is quite complex. That's why I decided to start the development of a new module from scratch. My main goals were:

    - give full control on the overdue email/letters to the user,

    - usability and easy the understand,

    - simplicity (700 lines of Python code, easy to read and understand),

    - reminders by email by default, with the possibility to also send letters and make phone calls.

     

    Please look at the README of the module for more info about the module (and its limitations) :

     

    I haven't submitted this module to OCA because of the rule "1 module per feature". But, if you think that this module should be in OCA, I'm ready to submit it. Anyway, your feedback on this module is welcomed. But don't forget that I want to KEEP THIS MODULE SIMPLE, so I may refuse features that add too much complexity.

     

    P.S. : I plan to backport this module to v10 after the first feedbacks.


    --

    Alexis de Lattre
    Akretion France - 27 rue Henri Rolland - 69100 Villeurbanne - France
    Mail : alexis.delattre@akretion.com

    Mobile : +33 6 99 08 92 45

    by Luc De Meyer. - 12:36 - 22 Apr 2020
  • Yet another followup module ?
    Dear OCA friends,

    I published yesterday a new module called Overdue Invoice Reminder (technical name : account_invoice_overdue_reminder) :


    It is an alternative to the OCA module account_credit_control available on https://github.com/OCA/credit-control (was in OCA/account-financial-tools for v10 and under)

    If you want to have a demo of my new module, please look at my screencast :

    Why did I decide to develop "yet another module" for followup ? Because I deployed the account_credit_control module for several companies (in v10), and the experience was not very positive, and they all stopped using it shortly after the deployment. My feeling about this OCA module is that it is like an army tank designed to send millions of followup letters ; the usability is not so good and it's not possible to customize the email/letters. Also, this module is very big (1900 line of python code) and difficult to modify because it is quite complex. That's why I decided to start the development of a new module from scratch. My main goals were:
    - give full control on the overdue email/letters to the user,
    - usability and easy the understand,
    - simplicity (700 lines of Python code, easy to read and understand),
    - reminders by email by default, with the possibility to also send letters and make phone calls.

    Please look at the README of the module for more info about the module (and its limitations) :

    I haven't submitted this module to OCA because of the rule "1 module per feature". But, if you think that this module should be in OCA, I'm ready to submit it. Anyway, your feedback on this module is welcomed. But don't forget that I want to KEEP THIS MODULE SIMPLE, so I may refuse features that add too much complexity.

    P.S. : I plan to backport this module to v10 after the first feedbacks.

    --
    Alexis de Lattre
    Akretion France - 27 rue Henri Rolland - 69100 Villeurbanne - France
    Mail : alexis.delattre@akretion.com
    Mobile : +33 6 99 08 92 45
    by Alexis de Lattre - 12:20 - 22 Apr 2020
  • Re: How and in what typical environments is Community Odoo begin used
    Odoo CE + OCA can perfectly serve for whole accounting and with powerful localizations like Spanish one (OCA/l10n-spain), it's even better than enterprise.

    Regards.
    by Pedro M. Baeza - 09:25 - 22 Apr 2020