2010. 11. 29
Email::MIME::* modules aren’t very close friends
The Email::*
modules are all pretty neat, with a pleasant API. But combining them isn’t always as effortless as you’d
expect.
For my email2blog script, I use Email::Filter as the bridge between the MTA and
blosxom:
# grab email from STDIN
my $mail = Email::Filter->new;
The $mail object has nifty methods that make it very simple to accept or reject a
message.
Once I accept a message, I take out the attachments with Email::MIME::Attachment::Stripper.
The first step is to construct a stripper based on the incoming email:
# make stripper
my $strip = Email::MIME::Attachment::Stripper->new(
Email::MIME->new( $mail->simple->as_string ),
force_filename => 1
);
I’m not impressed with the hoops I have to jump through there. It should be easy for
EMA::Stripper to build its own Email::MIME object when handed an
Email::Simple object. But in fact, even Email::MIME itself doesn’t offer that
option.
Next up is taking apart the MIME email:
# strip attachments
my $msg = $strip->message;
my @attachments = $strip->attachments;
That’s pretty straightforward. $msg is an Email::MIME object, without the
attachments. To get at the plaintext body is still not very comfortable:
# extract plaintext body
my $text = first { $_->content_type =~ m{text/plain} } $msg->parts;
Maybe that’s because there may not be a text/plain part with meaningful content, but I
wouldn’t expect $msg->body to be empty after the strip operation. It is though, so that fancy
grep is necessary.
The @attachments array on the other hand is very easy to work with. It has just the things
you need, and nothing else.
All in all, the script ended up being about 60 well-spaced lines long, with most of that being taken up by sanitizing the input. The fact that I didn’t actually have to think how MIME encoding works under the hood was a big plus, and for that I’m very happy with the PEP Project.
No comments yet [ / text / blosxom / email ] permalink
First impressions
I installed Blosxom today. Getting it up and running was a piece of cake. Finding useful plugins took a little longer, but I’m happy with the current set:
- categories, meta, directorybrowse, flavourdir
- MarkDown
- SmartyPants
I stole the layout from my Perl pages.
No comments yet [ / text / blosxom ] permalink
Tidyhtml 0.01
Initial version
I’ve just written a tiny blosxom plugin that cleans up your html. It uses the 1.07_01 dev version of
HTML::Tidy, which in
turn uses libtidy.
Since this is the first ever version, I’m just going to paste it here. I’ll build a proper release later on.
# Blosxom Plugin: tidyhtml
# Author(s): Rhesa Rozendaal
# Version: 0.01
# URL: http://oss.rhesa.com/blog/text/blosxom/plugins/tidyhtml
package tidyhtml;
use strict;
# --- Configurable variables -----
my $tidy_config = {
tidy_mark => 'no',
wrap => '120',
indent => 'auto',
output_xhtml => 'yes',
char_encoding => 'utf8',
doctype => 'strict',
add_xml_decl => 'yes',
alt_text => 'photo',
};
# --------------------------------
use HTML::Tidy;
sub last {
# only operate on html content types.
return unless $blosxom::header->{-type} =~ /html/;
$blosxom::output = HTML::Tidy->new( $tidy_config )
->clean( $blosxom::output );
return;
}
sub start { 1 }
1;
No comments yet [ / text / blosxom / plugins / tidyhtml ] permalink
JavaScript-driven syntax highlighting
Based on a PerlMonks idea, I’ve added syntax highlighting on code blocks. The javascript is here, and the css here.
See this post for an example (you need javascript enabled for this).
No comments yet [ / text / blosxom ] permalink
This time, with attachments
Let’s hear a “YAY!” :-)
No comments yet [ / text / blosxom / email ] permalink
Testing my email2blog script (take 2)
Ok, so mailing works, and the file gets stored in the proper location. Now, lets see if the permissions work out.
No comments yet [ / text / blosxom / email ] permalink
New version of “tidyhtml”
Slightly cleaned up, and made sure we’re outputting proper utf-8.
Grab tidyhtml 0.03 here and enjoy :-)
No comments yet [ / text / blosxom / plugins / tidyhtml ] permalink
The “feedback” plugin
Took some tweaking to get it to work. It only works on single-story pages, which aren’t accessible with the vanilla blosxom flavours.
I had to tweak my story.html a bit to give me links to a single story:
<p>
<a name="$fn"
href="$blosxom::url$blosxom::path/$fn.$blosxom::flavour"
>
<h2 class="pagetitle">$title</h2>
</a>
<br />
$body
</p>
By putting the href attribute on the anchor, you get to the actual story.
I also added a bit of fluff to make a nice footer:
<p class="storylinks">
<span id="commentlink">
<a href="$blosxom::url$blosxom::path/$fn.$blosxom::flavour">
comments: $feedback::comments_count
</a>
</span>
<span id="permalink">
time: $hr:$min <i>[$directorybrowse::browseable_path ]
<a href="$url/$yr/$mo_num/$da#$fn">permalink</a></i>
</span>
</p>
Adding this css makes it look decent:
p.storylinks #commentlink {
text-align: left;
width:100px;
float: left;
}
p.storylinks #permalink {
text-align: right;
position: relative;
display: block;
margin-left:100px;
}
Once that was in place, the feedback plugin
works like a charm. I like the moderation, and it looks reasonably secure.
No comments yet [ / text / blosxom ] permalink
Testing my email2blog script
I’ve just written a small Email::Filter script that will allow me to post
using email.
We’ll see; if this shows up, it works :-)
No comments yet [ / text / blosxom / email ] permalink
Handy Blosxom links
No comments yet [ / text / blosxom ] permalink