All blog posts

The domain has had an SPF record in place for several years. Previously its MX records were set-up to rely on email forwarding by the domain registrar. Unfortunately the registrar in use does not support SRS so all emails received are marked as failing SPF checks.

Recently the number of "bounce" email being received has been getting ridiculous. In an effort to combat this the SPF record should be changed from a soft to hard fail, DKIM signing introduced for outgoing mail and a DMARC DNS entry generated. Unfortunately, the use of the registrars email forwarder prevents a problem. The solution? Use the email server bundled with our web hosting package.

In the first place the MX record was set to point to All appeared well, but over the course of a few weeks the occasional email was going missing.

Raising this with Vidahost, it appears the MX record was setup wrongly. It should have had an entry of

    Previously I have written a blog at To try and rationalise the number of sites being maintained and hopefully help to promote within search engine listings its contents have been moved to the blog section of this site.

      It appears Stacey 3.0.0 has issues with generating urls for child pages on some occasions. When this problem is encountered, Stacey appends additional trailing slashes onto the child URLs, which when followed results in the URLs of internal site links in the destination page being incorrectly rooted.

      Rather than delve into the guts of this system, a quick and dirty work-around can be gained by editing the root .htaccess file. The following entries should resolve the problem:

      # Remove multiple slashes after domain
      RewriteCond %{THE_REQUEST} ^[A-Z]+\s//+(.*)\sHTTP/[0-9.]+$ [OR]
      RewriteCond %{THE_REQUEST} ^[A-Z]+\s(.*/)/+\sHTTP/[0-9.]+$
      RewriteRule .* %{ENV:proto}://%{HTTP_HOST}/%1 [R=301,L]
      # Remove multiple slashes anywhere in URL
      RewriteCond %{REQUEST_URI} ^(.*)//(.*)$
      RewriteRule . %1/%2 [R=301,L]