First of all, Happy New Year to you all! Here's hoping 2025 is a better year for the world as a whole than 2024 was. For me, December has mainly revolved around some emergency development I have had to take on to save my main web site, www.pmail.com. For many years, I have used Amazon's S3 service to host my web site, and for the most part, it has been a cost-effective and reliable way of doing that. Towards the end of November, though, when I went to the Amazon S3 console to upload my last progress message to the site, I discovered that for reasons I still do not understand, S3 had removed my ability to write data to the site, even though I was logged in as the site owner. Unfortunately, one area where Amazon S3 is NOT a good service is in the support they provide. In essence, at the product tier I was using, there was absolutely no support of any kind available apart from confusing and barely-readable FAQs, and a generative AI system that was so bad I don't know why they even bothered adding it. In order to get assistance from a real person, I would have had to move up to a tier that I can no longer afford. In the end, the only practical solution I could see was to resume hosting the site out of my own domain, but I do not currently have spare hardware suitable for running up a copy of Apache (the only web server I really know very much about). Out of desperation, I decided that I would host www.pmail.com on my main Mercury server, using the MercuryB HTTP/HTTPS protocol module that is part of that program. This kind of hosting, however, requires a rework of some of the core elements of MercuryB, which is mainly designed as a task-driven HTTP server using coded service modules; don't worry too much about what any of that means - suffice it to say that hosting a simple static web site was not something MercuryB could do at that time with any real fluency, although the changes required to make it happen were not very large. As I got into the rework, I realized that in fact, what I was doing was adding something that many small business sites might find quite useful - an easy way to host their own simple web sites, at which point it became clear that I needed to make the new functionality accessible as well as functional: it had to be possible to set up one or more static sites in an easy way, and to ensure that they had proper levels of security as well. So, what started as an emergency need to deal with a problem imposed on me by an anonymous, uninterested corporation, turned into a feature addition that I believe many sites will find handy. Put another way, a relatively small job (adding hosting support for my own web site) morphed into a larger job altogether (adding hosting support for anyone's web site). The rework, which I regard as a necessary interruption to other work I was doing, is proceeding quite well, and I hope to be able to regain control of the www.pmail.com web site in the next couple of weeks, at which point I can resume working on other issues. A particular interruption has been the release into testing of Mercury with DKIM support, although that code is working well, and has been in production here now for over a month. I realized quite late in the piece that just because I'm working on one Mercury module (MercuryB) that does not mean I can't also have the rest of the system out in testing, so I will be releasing Mercury with DKIM to the test team in the next couple of days. That's about all for this instalment - watch for another progress update, hopefully with more interesting information for WinPMail users, at the end of January. All my best to you all, -- David --