Kinomoto-san

Hello Head Guru, MySQL 8.0.xx uses "caching_sha2_password" as the default value for the "default_authentication_plugin" variable. My hosted webstore needs the legacy default value "mysql_native_password" to work properly. Please help. Thank you.

Hello. Is the update finished? Thank you. Server Up Time: 03:24:36 up 34 days HTTP Server: Apache PHP Version: 5.4.45 (Zend: 2.4.0)

Hello Dick, Thank you very much for picking my case. I am confident that you will be able to trim the software involved and minimize the problem of non-scanned e-mails. You can even use this as a case study and maybe apply the improvements to all TCH servers for a better e-mail filtering. I wish you good luck and, of course, I will be pleased to receive updates on the case. I was almost losing my faith on TCH, but you showed me that the advanced support staff actually exists; they are just extremely hard to reach. I gave all the possible assistance that a non-expert could give (or what was possible form the client side): Possible culprits and some pages with usable tips (old but worth examine). Now I am feeling relieved knowing that this case is in good hands. Thank you.

I finally got a proper answer acknowledging that there is something wrong with the software involved in the case, but no words about solutions attempts. I just gave up and I really wish to those with similar issues better luck. I will abstain from posting details about the ticket discussion (and my own thoughts about the quality/level of TCH's customer care).

There are at least 5 topics on the official CPanel forum about this exactly same problem. I pasted the link of the most relevant one to help TCH support track down the problem on my server. I am expecting a high level support, but I am really disappointed. Is there any advanced technician at TCH capable of making the necessary verifications and tests on the server willing to help the valued costumer? I really getting seek of the generic answers that I am receiving.

For people having the same problem here are my 2 cents: http://forums.cpanel.net/f5/spamassasin-problems-some-emails-82341.html This should help. I am not 100% sure because I am waiting the response from TCH staff on my ticket (I hope they will try the procedures listed on that post).

Hello, Recently I did some tweaks to my spamassasing configuration and I periodically verified my recieved e-mails to check the SA score. I noticed the some e-mails are note being scanned by SA, apparently. A good heard should look like this: X-Spam-Status: No, score=4.1 X-Spam-Score: 41 X-Spam-Bar: ++++ X-Ham-Report: Spam detection software, running on the system "quanton.tchmachines.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see root\@localhost for details. Content preview: [...] Content analysis details: (4.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 8.0 BAYES_99 BODY: Bayes spam probability is 99 to 100% [score: 1.0000] -1.5 SPF_HELO_PASS SPF: HELO matches SPF record -1.5 SPF_PASS SPF: sender matches SPF record -1.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_REMOTE_IMAGE Message contains an external image 0.6 AWL AWL: From: address is in the auto white-list X-Spam-Flag: NO But the non-scanned e-mail have a header like this: X-Spam-Status: No, score= X-Spam-Score: X-Spam-Bar: X-Ham-Report: X-Spam-Flag: NO My first guess is that the e-mails already included the spam-related headers. Potentially added by the spammers to trick SA into not scanning it again. Second the spammers might be adding some other code to the header to trick SA. Third it can be some configuration problem with SA. I can send the full header of some e-mails for further analysis. Is anyone else having such problem? Thank you. Note: Ticket already opened (#VVQ-565-94936) but I am having a quite hard time.