drStratuS

Well, if any of you are like me and don’t want the “enclosure” feature *at all*, here’s an amateur solution.

All you have to do is open your wp-includes/functions.php file and take a look at line no. 766. There’s a preg_match_all function which is responsible for “discovering” the audio or video file(s) linked in your post. You have to “break” that function somehow, for instance, add an additional “p” after “http” so it’ll read “httpp”.

Now WP won’t find any of your media files linked in your post anymore, nor will it include them in your blog’s feed, plus the delete button for the “enclosure” custom field in the administration panel will automagically start working.

Hope it helps, at least until someone comes up with a more profound solution. ??

I’m sorry for bringing up an old topic. I’m new here and not sure whether this is desirable or not.
First of all, great software! I practically fell in love with WordPress since it suits my needs perfectly. ??
Anyway, this problem, mentioned by xrlq, still exists in v1.2 and my solution is kind of similar to that of unclePino’s.
Open wp-includes/functions.php.
Replace the original lines 999-1001:
$message_headers = "MIME-Version: 1.0\r\n"
. "$from\r\n"
. "Content-Type: text/plain; charset=\"" . get_settings('blog_charset') . "\"\r\n";
with:
$message_headers = "MIME-Version: 1.0\n"
. "$from\n"
. "Content-Type: text/plain; charset=\"" . get_settings('blog_charset') . "\"\n";
As you can see, I deleted the “\r” in all three lines. After that, the “From:” field is displayed correctly and the defined charset is actually used.
You can make a similar adjustment in the lines 1039-1041, if you use comment approval.