WordPress

A note on comment notifications

This entry was posted in Administrative and tagged Internet WordPress on by

When a comment gets posted to my blog, the server sends me an email to let me know. In most cases it lands in my spam folder, and with good reason. WordPress is doing something dumb.

The email is using the “From” address which the commenter provided. With modern SPF, DMARC, and DKIM protocols, which are almost mandatory today, the owner of an email account indicates which servers are authorized to use its address. The receiving IMAP or POP server will check if it came from an authorized IP address. If it didn’t, the server may mark it as spam or block it completely. Failure to do authentication properly is one of the biggest reasons legitimate mail gets flagged.

People posting comments on my blog aren’t going to authorize my WordPress server to send email for them. When my personal email server gets a message with a “From” address that belongs to the commenter but a received-mail path that comes from the website server, it looks exactly like impersonation. Technically, it is.

I don’t know why WordPress does it this way. It could use a “From” address on garymcgath.com for comment notifications, and the mail would almost certainly get through.

This means I usually don’t see comment notifications, so it may take longer for me to reply. Sorry.

The WordPress ActivityPub plugin

This entry was posted in Administrative and tagged Fediverse mastodon WordPress on by

The ActivityPub protocol, best known as a key element of Mastodon, is catching on for multiple uses. There’s an ActivityPub plugin for WordPress, which makes a site’s feed available through ActivityPub. When you add it to your site, people with Mastodon accounts can use them to read your blog. (Some Mastodon sites put limitations on reading long posts.)

The current version is in beta and has limitations. The WordPress site has to be in your root directory. Because of the way I set this site up a long time ago, that locks me out. But recently Automattic, the company behind WordPress.com, has taken over development of the plugin. The result should be faster development and fewer limitations. Matthias Pfefferle, the plugin’s developer, will continue to work on it (and hopefully get better paid for it).
(more…)