{"id":40,"date":"2007-05-29T09:30:41","date_gmt":"2007-05-29T14:30:41","guid":{"rendered":"http:\/\/www.opticality.com\/blog\/?p=40"},"modified":"2007-05-29T09:30:41","modified_gmt":"2007-05-29T14:30:41","slug":"dkim-now-installed","status":"publish","type":"post","link":"https:\/\/opticality.com\/blog\/2007\/05\/29\/dkim-now-installed\/","title":{"rendered":"DKIM now installed"},"content":{"rendered":"

DKIM<\/a> (DomainKeys Identified Mail) is now running on my server. I don’t think there are enough sites using it yet for it to have been worth my effort (it was more effort than I expected it to be), but now it’s done, so we’ll see.<\/p>\n

Of course, if everyone else also said “It’s not worth the effort, and I’ll wait to see if it gets adopted”, then it will never reach critical mass.<\/p>\n

For now, the only really<\/em> useful thing is that I can now credibly (and easily<\/em>) toss all email that purports<\/em> to be from any of my originating domains to us. My spam filters did a reasonably good job tossing those, but now I should be 100% sure that an email claiming to be from a domain that I control, actually is from there.<\/p>\n

I had hoped that another benefit would be verifying that any email from yahoo.com was legitimate (since that’s such a popular spamming return path). Unfortunately, while Yahoo! definitely supports DKIM (and the original DomainKeys), many legitimate<\/em> yahoo.com users don’t send<\/em> their emails through the Yahoo! smtp servers, so their emails don’t get signed. Oh well.<\/p>\n

In any event, I’m now an enabler of the future of anti-spam measures, rather than a laggard. \ud83d\ude09<\/p>\n

Next step on this train is likely to be greylisting. There is a lot to like about it, but a lot to be wary of from a business perspective. I didn’t give a link because I’ll do that if<\/em> I install it and get it running.<\/p>\n","protected":false},"excerpt":{"rendered":"

DKIM (DomainKeys Identified Mail) is now running on my server. I don’t think there are enough sites using it yet for it to have been worth my effort (it was more effort than I expected it to be), but now it’s done, so we’ll see. Of course, if everyone else also said “It’s not worth […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":4,"activitypub_interaction_policy_quote":"anyone","activitypub_status":"","footnotes":""},"categories":[4,2],"tags":[],"class_list":["post-40","post","type-post","status-publish","format-standard","hentry","category-4","category-2"],"_links":{"self":[{"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/posts\/40","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/comments?post=40"}],"version-history":[{"count":0,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/posts\/40\/revisions"}],"wp:attachment":[{"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/media?parent=40"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/categories?post=40"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/tags?post=40"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}