importing outlook pst files in evolution in Fedora 13 ( Goddard)

If you were using outlook and moved to some other mail client then you know the pain of moving the mails from outlook mail from outlook to any other client.

If you are using evolution on Fedora, then you are in luck. Just install the plug-in and select the file to import as simple as that.

sudo yum install evolution-pst

Well, can it get simpler than that and a post shorter than this 🙂


email with templates (with variables) from the command line with sendmail or any other MTA.

I was trying to get templates to work on evolution and found that although templates are there in evolution mail client, its not that efficient to use. What I thus wanted was to have something that could allow me to send mails to (and cc and bcc) to specified people with predefined template, only some values changed, like changelog and so on. So I wrote a set of files and below files to achieve the same. Hope it helps you too 🙂

First we will have a file called \”fields\” containing all the variable that we intend to use:

cc=\”Amit Agarwal\”

Ok, so here we are defning the to field, cc field and the other fields along with the name of the file to attach. Next we need the template to use. Create a file called \”template.changelog\” as defined in the above file:


Please find the changelog for $tag for $product-$customer. Issue addressed : $issue .



Next we have a shell script called \”\” to actually send the mail. Here is the script:

source ./fields
rm -rf .temp .temp1
touch .temp
sed \”s/\\$product/$product/g\” $template > .temp1
sed \”s/\\$customer/$customer/g\” .temp1 > .temp

sed \”s/\\$issue/$issue/g\” .temp1 > .temp1
sed \”s/\\$tag/$tag/g\” .temp1 > .temp

rm -f .temp1
sendEmail -xu user  -xp pass  -s server  -f agarwal -t \”$to\” -cc \”$cc\” -u \”[$product-$customer]:$subject for $issue\” -o message-file=.temp -a $attachment
echo \”Mail sent with \\nSubject $subject \\nto $to \\nand copied to $cc and \\nattached $attachment\”

In the shell script I am using sendEmail, but you can use any MTA that you want. 🙂

Well, I think you get the idea, so you can modify the script to include the necessary checks and modify according to your needs.


Get a lot of spam — use spamassasin.

If you get a lot of spam into your local inbox and do not want your service provider to filter them for you, like me :), then you can use spamassasin.

The benefit with this approach is that all the spam will be delivered to your local inbox and you do not need to do anything on the server. You can blacklist, whitelist, report message as spam all on your client and it would not change anything on the server. So you control your mail, isn\’t that great. What to do, start with minimal things:

sudo yum install spamassassin evolution-spamassassin

Now configure spamassasin to start on system bootup. And then configure your evolution to use spamassasin.

You can do this in the evolution preferences -> Mail Preferences -> Junk