"Note: all blogs are owned by the original account (email) that created them - you best and easiest is to get the log-in info from the original developer and have them transfer the blog to another account"
So that's the catch22-I respect that blog belongs to original account, which is great for personal blog, but when the blog really "belongs" to the organization and community, and the original account won't cooperate or pretends he's not getting the emails, everyone suffers because blog can't be updated or changed. Interesting dilemma as raises question of who does the blog really belong to, and if the blog is for a legitimate organization, does the original account's rights trump those of the organization, and should that person have the right to hold the blog hostage after he/she has resigned post and moved on? Doesn't seem right. Seems like organization should have some backdoor into the site and should technically own the blog, not the web admin.
Is one option to literally copy the content to another blog, with a better domain name, and leave the old blog inactive? If so is there a paid option for this or a utility? What are other options? Seems like organization should have a right to the blog. Thanks, fred