Shawn Milochik <ShawnLinurati.net> wrote in message news:<pan.2003.08.19.22.42.33.43107.16205Linurati .net>...Okay, so far the only thing you need to do is read the doentation> Here's the project:
> I want to download my mail, and optionally do zero or more
> of the following:
> 1. Forward certain messages to another e-mail address.
> 2. Send a particular auto-response, depending upon sender.
> 3. E-mail a list of all e-mail senders/subjects to another e-mail address.
> Then, I want to filter all messages through a Bayesian filter, probably
> Spamassassin, then place the good messages back into my original
> e-mail account, except in another box, such as "unread" instead of
> back into the inbox, and spam into another box, such as "spam"
for spammassassin. There's a few ways to do it. I personally use
MH-mail, procmail, postfix, and fetchmail. Fetchmail picks up the
mail, forwards it to the SMTP server on the box, checks for viruses
(yes, you CAN check mail for viruses on Linux - not that it would harm
anything - but my wife enjoys Windows, so I have to keep her safe and
get her mail - then she grabs the mail off my system ... where was I
.... oh, ya), then it goes through procmail, which has a "recipe" to
filter it using spamassassin (to pick up "stray" spam - read on). So
far, the only thing Perl is spamassassin.
Well, this again is not Perl, but you can set fetchmail NOT to mark>
> I do not want to use any of the user mail functionality of my
> Linux server -- I just want to use my pop3/smtp e-mail account, and
> I want everything to be put back into my pop3/smtp e-mail account
> after it's been filtered, so that I can check it with webmail.
messages as being read when you get them. Not exactly what you
wanted, but to send mail BACK to your webmail account seems redundent
- but that's my opinion and the fact that I'm spoilled by my ISP
(which does use spamassassin). However, if you want to 'roll your
own' solution, there are several Perl modules to aid you in this task.
Just a side note: if you are responsible about testing, you're going
to need to set up a mail server anyway. I can speak from experience
that it's a bad idea to use a script (or fetchmail for that matter)
and not test it in a controled environment first. You end up lossing
mail if you don't test first ;)
IMHO, use the tools on your system. They are proven, maintained, and>
> So the question is, should I use a hobbled together combination of
> fetchmail, procmail, and sendmail (hereafter referred to as "FPS"),
> or a Perl script?
work. That's not a reflection of any Perl scripts you may find/write
- but why re-invent the wheel? Unless that what's you want to do. I
mean, why write say, a web server in Perl, unless you think you can do
better than Apache -or- want the experience. HOWEVER, I'd ditch
sendmail and start using postfix ... but here again, not Perl and just
If you decide to 'roll your own', you're going to have a monumental
task ahead of you.