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 --
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 --