Good morning all,

I can see from David's progress reports that DKIM support in Mercury is progressing well, and that it is in Beta testing at the moment.

Is there a roadmap for a working release?

Although I have full SPF alignment for my domain, (and therefore a DMARC pass), I am keen to get DKIM compliant as well.

I would be willing to help with Beta testing if this helps @David

John

Yes, it's been a while, hasn't it... The problem is that the DKIM release got rather swept away by the need to redevelop MercuryB to host the pmail.com website after Amazon shafted me, and when I look at the huge extra capability those changes add (I've just finished adding a workable level of automated ACME (LetsEncrypt) support too), it seems that it's worth a little longer so that it can be included in the release.

I'm very near to having MercuryB complete now - I just need to fix some problems I inadvertently introduced with existing MercuryB services - but once that's done I'll be going through a short beta cycle then doing a release. If I can't get MercuryB complete to my satisfaction by the end of April, I'll ship the new release with the DKIM support, but with the old version of MercuryB.

Sorry for the delays... As I frequently say to myself, though (I talk to myself a lot), while it may take longer than I expect, I almost always do actually get things done... eventually.

Cheers!

-- David --

Thanks for the update @David ,

Another few weeks wait isn't going to make a busting difference so I wont pester you further!

Thanks again

John.

Hello,
Do you have any news ?.
Many thanks for your information

Hi @PHR ,

I don't have any further info, but hopefully @David may be able to give us an update on a prospective release

John.

I'm currently trying to track down a reasonably large memory leak in the MercuryB module;
I also have to complete porting the web-based Mercury licensing system to the new
MercuryB interface (that process is nearly finished). Even though a lot of users don't use
the MercuryB module (something I hope will change with the new static site support), I
really can't release a version of Mercury when there's a fairly important outstanding issue
in any of the modules.

Once I've tracked the memory leak, there will be a short beta period (basically just a week,
to make sure I haven't overlooked anything obvious) - it doesn't need to be longer than that
because the new Mercury has been running flawlessly on Demeter, my new web presence
system, for nearly two months now, including the DKIM support and the static site
serving in MercuryB. After that, I'll be getting it out the door as quickly as I possibly can.

In case you're interested, the ACME support I mentioned in my post earlier this year is
now also working, and Mercury on Demeter is automatically obtaining and renewing
certificates from LetsEncrypt (not just for the MercuryB module, but for all the SSL-capable
modules on the system).

I've been rather hampered in work recently by a fairly severe bout of RSI in my right arm,
but that's gradually coming right. It's meant I've only been able to work an hour or two
at a time before the pain gets too intense, and that's slowed me down a lot.

Sorry for all the delays - nothing ever seems to be easy any more, and I should really
learn not to make release estimates, because I never seem to be able to get them right
(except this time, of course <grin>.)

Cheers!

-- David --

PS: I'll put up a progress report this weekend - I realize I've been a bit slack in that
department recently.

@David
Many thanks for your information.
Take care of your health ...