Well the move went rather smoothly I think. Other than my hibernating Tinpot Alley Blog performing some kind of database brain fart you’d never notice I’d changed servers – other than the fact that sites aren’t down for half the day and everything’s much quicker to load (please tell me it loads quicker….).
The one thing I’m currently trying to get my head round is email. Especially spam email.
It’s not just the usual crap that we all get, it’s also spoofed stuff being sent from butlersheetmetal.com and .
Now I’ve set up all the boxtrappers and spamassassins and thrown everything down various blackholes, but it seems that spamming from your domain is something else entirely. Googling the problem leads you to but one solution: .
SPF fights return-path address forgery and makes it easier to identify spoofs. Domain owners identify sending mail servers in DNS. SMTP receivers verify the envelope sender address against this information, and can distinguish authentic messages from forgeries before any message data is transmitted.
Yes, it’s all a bit too much for me on a Monday, too, and is only something you need to get your head round if you have your own server. Or that’s what I think I can gather. I don’t think you have to waste your time with this kinda thing otherwise.
I’ve also added the plugin to stop undesirables harversting email addresses from this blog.
It’s probably all a bit after the horse has bolted but I really don’t like the idea of people being spammed from butlersheetmetal.com and tinpotalley.com.
I apologise for not having implemented something before it happened.
If there’s anybody with a bit more nous about this, please feel free to share in the comments.
Yeah, I read about that yesterday. Apparently ICANN have said they aren't actually capable of stopping their .org domain as it belongs to Tucows or something.
I find trying to get my head round the whole DNS mail thing and whatnot truly monstrous.
Still, got to get there.
- spam
- offensive
- disagree
- off topic
Like