dynambee

I've experienced this problem in the past as well. I think it is because the test system uses different code to what is used on the "contact" form and for sending orders. If the main system works then that's what is important. Also, don't use encrypted connections to SMTP. Use either SSL or TLS. Always.

Good email service is something that I think a lot of businesses struggle with. I know I have, and I've tried many solutions over the years. For a long time I used Google Apps Standard Edition -- the free version that is no longer available for new signups. It's pretty good, but since I can't add it to new domains I'm pretty limited in how I can use it. I have a couple of domains on Google Apps paid but at $6 per account it can add up in a hurry (plus I don't really like forking money over to Google, they have plenty already.) One thing that the paid version does provide is push email, and the free version does not have this. I also have my own mailserver set up, I use mailcow on a VULTR VM. It works quite well actually, and has push support. It also has calendaring and contacts. I've been running it for a couple of years now and it has proven to be stable with good update support. However I know if something goes wrong with it I will be up sh#t creek. I don't have the time to dedicate to fixing a broken mail server and mail is critical to a functioning business. There is also the problem of making sure my domains and IP don't end up on blacklists and this takes time too. Even so, some of the big mail providers will tag my outbound messages as spam. All of this has resulted in a search for a better, more affordable mail solution. The most promising one I have found thus far is OpenSRS Hosted Email. It's cheap (50~60¢/month per account), seems to be robust, and the overall features are good for the money. The only drawback I see is no push support. I suppose I could live without that in the name of fixing all the other issues *but* I wonder if anyone here has any better options they could suggest? Ideas?

That is absolutely fantastic news. Thank you!

I've been playing with the ES module on TB 1.0.8. My host (Cloudways) offers ES 5.4 and 6.5. I tried to get it working with 6.5 but even following the suggestions I found on this forum I was unable to get ES to index with 6.5. I think there have been too many changes between 6.0 (which the module is in theory compatible with) and 6.5/6.8/newer for it to work. Even with only the 8 or 10 sample products in the store the indexing didn't work. However when I rolled back to ES 5.4 the indexing worked perfectly & was nearly instant. Now I have a different problem, the front end parts of the ES module do not seem to function with TB 1.0.8 with Bleeding Edge upgrades. Later today I will do some more testing on this and see if I can narrow down exactly why.

If the current IP gets re-blacklisted then a new IP will get blacklisted as well. The key thing is to fix the problems that caused the blacklisting the first time -- using PHP Mailer and not having the mail DNS SPF & DKIM records set up correctly. Once those issues are fixed it doesn't really matter if you get a new IP or go through the effort of getting the current IP unlisted. The only real difference is the amount of time & effort involved and as you have experienced getting unlisted is a PITA.

You could save yourself a lot of time by getting a new IP for your webserver. Before doing this edit your DNS to change the domain record TTL settings from their current 14400 (4 hours) to 300 (5 minutes). I would advise doing this 24 hours before you swap the IP but you could wait as little as 4 hours. Then swap the IP, and after a few hours increase the DNS TTL to 3600 (1 hour). Make sure all your DNS settings for email (SPF and DKIM in particular) are correct. This should solve your problem without having to deal with all the blacklist issues you face now.

@eikichiz, did you actually get this working and then do a full reindex to see if it indexed properly? I followed your directions but the store seems to be unable to index any data. Any other tips or ideas? Edit: Also, what version of TB were you using?

Is your mailchimp account active & functioning correctly? Any recent bills from them that your CC company rejected for some reason? No recently changed passwords or other credentials?

That would explain it. Like an idiot I forgot to look in the TB Marketplace for the module, only looked for it in the TB site back office. Thanks.

I wanted to do some testing with the Elasticsearch module but I cannot seem to get the module to install. I downloaded the module from github as a zip file. Renamed the zip file to "elasticsearch.zip" and renamed the module folder inside the zip file to "elasticsearch". Then I uploaded the module in the back office. The file seems to have been unzipped into the correct elasticsearch folder but once this completes everything crashes (error below). I figured maybe I need to install it from the command line so I did that as well (manual unzipping, making sure permissions are set correctly) and then went back into the back office. When I try to open the Modules and Services it crashes. In both cases I get the following error message: [PrestaShop] Fatal error in module file :/public_html/modules/elasticsearch/elasticsearch.php: require_once(): Failed opening required '/public_html/modules/elasticsearch/vendor/autoload.php' (include_path='/public_html/vendor/pear/archive_tar:/public_html/vendor/pear/console_getopt: /public_html/vendor/pear/pear-core-minimal/src:/public_html/vendor/pear/pear_exception:.:/usr/share/php') I removed the directory path before /public_html as it was the same for every folder and just made the error harder to read. I've also inserted a few line breaks to make the error easier to read. I'm on a Cloudways VULTR server with 2 cores, 4GB memory, PHP 7.1, Elasticsearch 5.4 (tried 6.5 too, same error), and MySQL 5.7. Redis is installed too, which should be unrelated. I have tried disabling non-TB modules and disabling overrides, same problem happens. I have all caching on the server disabled. All forms of CCC are disabled. I'm sure that I am just missing something simple here but for the life of me I can't figure out what it is. Help?

Try running the test script on your server again to see if it can connect to the MS SMTP server or if it still gives the same error. If the test script works then you have a TB config problem. If the test script doesn't work then you are still blacklisted.

It's been 6 months, why is your website still running TB?

If you really want to stay with ES 6.8 then doing something like what is described in this thread might make it work.

This is very interesting and relieving to hear. My memory from the earlier days of TB is that the plan was to maintain PS 1.6.x compatibility for the 1.0.x release of TB but that compatibility would start to break with the 1.1.x releases. I am very happy to hear that either my memory is wrong or that TB's planned path forward has shifted.

At this point it has been definitively shown that MS is blocking SMTP requests from @t4Chippy's webserver. We don't know why the IP is being blocked but the test script runs perfectly from a server on a different IP using @t4Chippy's email account credentials. So, in final summary, the swiftmailer implementation included with TB supports STARTTLS and connects just fine to MS Office 365 SMTP server. The issue here was specific to the webserver in question. The solution will either be to get MS to take the IP off the blacklist (difficult IMO) or to change webserver IPs. Also, DNS settings regarding email authentication need to be fully set up to hopefully avoid this problem happening again on a new IP.

9/100. 😞

The Thirtybees module is not compatible with Elasticsearch 5. It is compatible with Elasticsearch 5.4. These are very different things. It should also work with 6.0 but I don't know of anyone who has tried it with a version as new as 6.8 and there is no way to know if it will run. It is best to get it working with a version that is known to work before trying anything else. I understand it gets very frustrating when a whole ton of time is spent trying to get something to work. Sometimes it is best to step away for a bit and then try again with rested mind & eyes. It is very much worth it to get the module working but as I mentioned in my original reply, it will probably take some effort.

A bunch of messages back you mentioned that you installed ES 5. Hopefully by that you meant 5.4? That is the earliest version supported by the plugin. In any case, based on the CURL results you posted above, port 9200 still has ES 6.8 running on it. Not sure where ES 5.4 is but it won't be on 9200. I'm actually not even sure that it is supported to run two ES servers on one system but having never tried it I can't say for sure. Either way, I would remove both the installed ES servers and start fresh with ES 5.4 and see how that goes.

Here is some more info on that blacklist. You might want to try checking your IP's sender score. There's a good chance they won't have much info on you, but they might. Good that your domain doesn't seem to be blacklisted, that would really suck. Changing webserver IPs is much easier than changing domains.

Based on further discussion by PM and further testing by myself it would seem somewhat likely that @t4Chippy's webserver IP has been blacklisted by MS or by a 3rd party blacklist provider used by MS. This could be as a result of the regular connections by PHP Mailer or it might be because the DNS records for the domain did not show the webserver IP as being a valid IP to send mail from. Without the DNS records showing the webserver IP as an approved mail server for the domain it makes that IP appear to be sending spam. The exact reasons are speculation, but what does seem to be true is that the swiftmailer version included with TB is able to connect to smtp.office365.com using TLS. At this point @t4Chippy should check if his IP has been blacklisted and use something like this to see if his entire domain is on a blacklist. If the IP is blacklisted then getting a new IP for the webserver would be a good idea. If the domain itself is blacklisted, that is a much bigger problem. Getting a domain removed from public blacklists is just about impossible. The usual suggestion is to abandon the domain and start over with a new one. If neither the IP nor the domain appear on public blacklists then (assuming it is a blacklist issue) it is probably just the MS SMTP server blacklisting the IP. In this case a new IP for the webserver would be the solution, combined with proper DNS records of course.

Something I would personally find extremely useful would be the ability to display multiple products on one page. This could be used for selling spare parts for a machine, for example. All the parts for one machine listed on one page with a price & "Add to Cart" button beside each one. It would also be very useful to be able to associate products to other products. Continuing the example from above, it would be very good to be able to associate all the spare parts for a given machine to the machine's own listing. From a different angle it would be great to be able to associate common or compatible accessories with a product. Customers are more likely to buy things together that way, or at least be aware of the options they might have. Spare batteries, cases, straps, etc, etc. Another thing that I have noticed is that when a product has variations (different sizes, different colors, etc) there is no way to set different physical weights or dimensions for the variations. Only the parent product has dimensions and weight set. Sometimes variations can be quite different in size & weight and not being able to set them individually makes the variation system a lot less useful. Just some random thoughts.

Try connecting from the command line with CURL: curl -GET http://127.0.0.1:9200 or curl -XGET http://127.0.0.1:9200 or curl -IGET http://127.0.0.1:9200 You can also try something like this to make sure your ES server is running: sudo /etc/init.d/elasticsearch status There should also be a logs directory just below your main elasticsearch directory, or it could be /var/log/elasticsearch. You can also check the system logs, sometimes they will have helpful info.

Did he correctly modify the script for your server? Did he set up the email addresses and password correctly? The script itself is fine, I wrote it and then tested it before posting it. Might be better if your friend comes to this thread. It’s hard to talk through a 3rd party.

Try a slightly older version of ES. The module was written to work with 5.4 and 6.0. It may work with newer versions or it may not.

The Elastic Search module will probably take some effort to get working properly but once you do get it working the search on your site will become incredibly fast. At least as fast and probably faster than any site you have visited. I’m working on a site now that will have ~100k items and eventually probably 200k items and will definitely be implementing the ES module on it. Unfortunately I’m not yet ready to start work on that part of the site.