Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: Yet another followup module ?
Re: How and in what typical environments is Community Odoo begin used
Re: smtp server service
byAlso, 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!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_staticBy the way, we use Mailgun too.RegardsOn 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 :)JordiLe 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.comSo 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 domainJust 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 blacklistedGood start is here https://mxtoolbox.com/blacklists.aspxReason , 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 domain4) 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/20911Hope 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.
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
--
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Lorenzo Battistini
https://github.com/eLBati
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
