Handling SPAM

Well it’s not a new debate, thats for sure, and I have very strong views on this topic (especially blacklists and ISP’s restricting trade), as well as an approach to a new Protocol termed ‘Authenicated Mail’ or ‘amail’. I’ll need to put my notes on my blog one day.

The purpose for note, is the ongoing increasing spam and inappropiateness of mail that is coming to a general web accessible email address for a client.
I’ve proposed they move to a Challenge Response System for at least general listed email addresses on web sites. This will at least cut down the amount received at the mailbox, however it doesn’t eliminate the mail, the traffic, time, money and space used in mail.

What other approaches can you try. Well, not having a mailto link on your site is a good start. The use of an image to display an email address and not text is also a sound entry approach. I’d also recommend that for general web inquiries, you rotate your names, for example: website@domain.com , inquiries@domain.com , contactus@domain.com etc. As the address is only used on the website, changing the email, and turning the old name into an invalid mailbox will help.

I’ve also found another novel approach, this is the second time I’ve seen this. The website asks you to please add predefined characters into the subject line. Here’s and example.

http://r0.unctad.org/ecommerce/ecommerce_en/contact_en.htm

Tagged with: General

Why using production workloads over simulated workloads is critical

AI-Assisted SQL Tuning Last week in his keynote speech at Percona Live Bay Area 2026 , Andy Pavlo presented Databases: The Final Boss of Agents and provided some useful insights into query optimization of simulated workloads leveraging AI.

Improving your MySQL Security Posture Presentation

At the MySQL BR Conference 2025 I had the opportunity to speak about Improving Your MySQL Security Posture. You can find a copy of my slides on my Presentations , and a Portugese (Brazil) translation.

MySQL and Heatwave Summit Presentation

Last week I had the opportunity to speak at the MySQL and Heatwave Summit in San Francisco. I discussed the impact of the new MySQL 8.0 default caching_sha2_password authentication, replacing the mysql_native_password authentication that was the default for approximately 20 of the 30 years that MySQL has existed.