All Activity

I'm sure you've probably already done this, but running your domain through https://mxtoolbox.com/ can maybe provide insight as well.

It is mostly B2C, going to Outlook, Live and Hotmail ...which is certainly used by many private individuals. The services involved in this context are truly terrible. As soon as the word order appears in a message, it seems to get flagged as spam - which naturally makes things difficult for an online shop. It makes no sense, either, because there are technical ways to identify emails as legitimate rather than spam (DMARC, SPF, DKIM) - and we have implemented all of these correctly, of course, but Microsoft simply doesn't care. Whitelisting has to go through the provider; they are aware of the issue and are actively working on it, but even if the block is lifted, it can take up to three weeks. It’s not an ideal situation for us. Now we have Brevo since a few weeks and it works 🙂

If delivering to MS services, I expect this is B2B communications? If so, it's very likely the client would need to whitelist your domain before your emails can reach them. I've run into this many times before.

I've been monitoring the dashboard on the back of my shops for an announcement about the release of Thirty Bees 1.7. Playing with the core updater I see it is released. When did this happen and why nothing posted in Announcements About Thirty Bees?

I found that the id_product_attribute keyword isn't supported in the SEO URL settings Just use {id} and {rewrite} and it works

Thanks for the additional info; things are much clearer to me now. 👍 That said, we never sent attachments or anything like that, but naturally, a lot of "suspicious words" do crop up in customer communications—terms like "order," "online shop," and so on—which likely get flagged as spam. At times, it’s almost impossible to send emails to Microsoft services; sometimes they just vanish into thin air without an error message—they don't even end up in the recipient's spam folder. It’s pretty outrageous... and then you have to deal with a lot of—often not-so-friendly—inquiries asking about the status of orders and the like. We have a high volume of transactional and service-related emails to handle. We now manage 100% of that via Brevo. We don't do much marketing, and when we do, we use dedicated newsletter services that don't run through our own domain.

Sure. Pardon if you are aware of this, but I will lay out what I have to advise most companies below. I suspect that you historically were sending all email from one domain: yourdomain.de or similar. This setup can cause many issues with deliverability over time, which it sounds like you are now seeing. Fixing it is not quick but can be achieved easily. Business and transactional emails need to be separated from marketing communications by sending domain Business (Customer service responses) and transactional (Order confirmations) send from yourdomain.de, but marketing communications send from another domain or subdomain: email.yourdomain.de as example. (Check your spam folder at your personal inbox and you will see that most companies follow this practice as it protects you main domain from being flagged as spam by email companies.) Typically, you would only configure Brevo and their servers to handle marketing communications since they are usually larger volume and more likely to be flagged as spam. Your reply-to address in brevo can be a transactional address You can keep your transactional communications coming directly out of TB if you'd like using smtp. Brevo can handle these as well though if you'd like but more sending = additional cost. Ensure that you are not sending attachments in any emails by default, ever. This is almost a guaranteed spam flag against your domain. TB adds invoice attachments by default to order confirmations if you enable invoices. TB can be updated so that it still creates invoices, but does not add the attachment to the emails. The switch to using a new sending domain for marketing will take some warming to build a reputation. Start your first few sends to known recipients so that they do not flag you as spam manually on their side to help warm your domain. Additionally, in a different thread in this forum is a post with my latest version of the Brevo module that works with TB 1.6 and php 8+ and offers the ecommerce capability sync. If not using it, i advise testing on your site... it works really well to keep order data and lists synced to brevo.

Thanks for this. Testing it out currently.

Sorry, i can´t understand your idea about this? pls. explain it for me 🙂 We are experiencing major difficulties with direct emails sent from our provider to Hotmail/MS services, GMX, etc., as a large volume of them are being marked as spam. That was our main reason for choosing Brevo.

I have been using Brevo for a few years for marketing communications only. This separation from has kept our transactional communications from the stock TB setup delivering smoothly for the most part.

I set discontinued products to “Nowhere” visibility and added a manual link to a replacement. Then I manually submitted the product URLs to Google via Search Console. That kept the rankings alive without modifying the sitemap code. Anybody else try a similar workaround?

Thanks for clarifying :+)

Yes, the team said those features will be gradually added soon.

We're instant payment too. I switched to the new PayPal with fresh REST API, which apparently also features ApplePay, GooglePay and Pay Later (PayPal) functionality, although when I tried it, only the PayPal and Credit/Debit Card (complete with on-page form) options show. Would I be correct in assuming that this is simply down to these features not currently being supported in the module...or something I've messed up on at the PayPal API end? It's not the end of the world or anything, I just figured here would be the best place to ask:+)

Actually no, only one minification would happen. Current implementation just takes the very first hook int the list and use that one. So, if you just installed the module after the standard module was installed, its hook would never be called. You could "fix" that by changing the hook orders in Modules > Positions, but nobody would do that (or know about it even) So yeah, we really should have an option to select which implementation should be used.

There were a couple of small things that we still needed to iron out with some of the modules, hence the official delay. We should be doing an 'official' release soon. There will be a changelog and official email detailing some of the major changes etc.

Unfortunately, only the bots are getting smarter.. 🙂 Yes, I put this check in as otherwise we will end up minifying twice. If you think that the library could replace the native implementation that is no longer supported, I would love for thirty bees to adopt the module. 🙂

Soon there will be an official release. As you can imagine - many new features, bug fixes, security patches, etc. It is STRONGLY recommended to update to 1.7!

but it is not the cheapest one for a smaller shop, brevo has up to a lot of mails/day for free and is on of the best services.

Order confirmation emails seem simple until they start bouncing or landing in spam. For a Thirty Bees store, the best bulk email service provider usually needs simple SMTP integration and stable deliverability more than fancy extra features - honestly, SMTPmart is the best bulk email service provider I've used with a similar store setup, handling order confirmations and promo emails reliably. Worth testing sending limits and SMTP compatibility before picking the best bulk email service provider for your store.

Hi I like to hear if you find the hack, and what you did to get rid of it? I have exactly the same issue on my shop, and I also runs v1.1.0

I notice only today that Thirtybees 1.7 was released on github on July the 14th. The only thing wrote on the changelog is: Bump modules and themes Can someone explain it a little more in detail?

Very nice. This is exactly why we extracted the minifiers from core to module -- so somebody smart could provide better and faster alternative. I love seeing this. Somewhat unrelated note -- I looked into module, and was surprised by the requirement to disable/uninstall default minification module first. And indeed, core do not give us an option to choose which minification module to use. We should implement that in core, so we don't need this kind of hacks in modules.

Just to complete this here, maybe use the thirtybees 2FA module: https://store.getdatakick.com/en/modules/back-office-two-factor-authentication I'm very interested in this topic right now and would like to implement something related to it. I think "hardening" the admin login is an important matter.

Just to complete this here, maybe better use the thirtybees module: https://store.getdatakick.com/en/modules/back-office-two-factor-authentication I'm very interested in this topic right now and would like to implement something related to it. I think "hardening" the admin login is an important matter.