When creating documents in HTML that make use of <div> blocks to position elements on the page links can appear to stop working if they are in the area bound by the block. Browsers appear to render HTML code in different orders, so a block that appears after a link will suppress the link in the rendered page. It is obvious once you understand the problem, but took some time to sort out when I could see the text clearly, especially since in one case the link worked in IE but not Firefox
An example:

<div style="position: relative;">
    <p style="position: relative;">
        <a href="">
            This link likely won't work.
        </a>
    </p>
    <div style="position: absolute;
                top: 0px;
                width: 100%;
                border:solid 1px;">
        <p style="text-align: right">
            DIV block text on the right.
        </p>
    </div>
</div>

Fortunately the fix in some cases is as simple as reordering the link and <div> blocks so that the block gets rendered first:

<div style="position: relative;">
    <div style="position: absolute;
                top: 0px;
                width: 100%;
                border:solid 1px;">
        <p style="text-align: right">
            DIV block text on the right.
        </p>
    </div>
    <p style="position: relative;">
        <a href="">
            This link should work.
        </a>
    </p>
</div>

Clear as day once you know what’s happening - the text has rendered properly and appears to be a link, but it cannot be clicked in some browsers. The <div> that has been layered over top of the text can be seen through, but the hotspot for the link is in the layer under the block.

I installed the SARE rule updates channel into a nightly sa-update routine yesterday, and noticed today that the rules didn’t appear to be getting used. I had misread the docs initially it turns out - you must use the updates.spamassassin.org channel if you plan to use any other channels since SA expects to find all rules in one location.

When I tried adding the default channel tonight I was getting the following error tonight while setting up sa-update:

error: GPG validation failed!
The update downloaded successfully, but it was not signed with a trusted GPG
key. Instead, it was signed with the following keys:

24F434CE

Perhaps you need to import the channel's GPG key? For example:

wget http://spamassassin.apache.org/updates/GPG.KEY
gpg --import GPG.KEY

After poking around for a bit I found the last line of the message is misleading - you actually want to run sa-update --import GPG.KEY after downloading it.

The guys on Cranky Geeks were discussing the merits of cellular phones having all sorts of extra features on them. North Americans are less inclined to see their phones as all-purpose devices as Europeans do. One comment made was that Europeans refer to their phones as their “mobile”, instead of “phone”. The cranks overlooked the fact that here in NA we refer to them as our “cell” - a word that usually describes a really small living organism not normally thought of as being multitasking. Perhaps it’s the name that’s holding us back?