Spam and Pine

[Chris Devers]

On Tue, 2 Dec 2003, Duane Morin wrote:

> I've always been a fan of pine.  As long as I can get an ssh window to
> my home machine, I can get mail.  The major downside to Pine relative to
> the rest of the world is that it's not a POP client.

Then Pine has no major downside: it does POP just fine (for values of
"just fine" where "just fine" means living in some bizarre world where POP
is more desirable than IMAP :).

If you don't mind hand editing your ~/.pinerc, the config line will look
something like this if you want to add a POP account to your inboxes:

    incoming-folders=popserver {pop.host.com:110/user=dmorin}INBOX

with multiple POP &/or IMAP servers delimited by commas. I've got Pine set
up to access mail on four different servers as well as localhost, and the
remote servers are a mix of POP & IMAP -- no problems at all.

> Is there a good anti-spam solution that works in such a way that
> something like Pine, which periodically moves my mail form
> /var/spool/mail to $HOME/mbox (only while it is open), could use?

Err, Procmail / SpamAssassin? I've been using that setup for about a year
now, and it works fairly nicely.

But if you really want to go for a POP based approach, by all means go
ahead -- Pine will let you. If you need details, feel free to ask me, or
search Google for Pine's POP configuration options -- for the most part
it's pretty straightforward once you get used to the

    label {host[:port][/protocol][/options, e.g. username]}path

syntax that Pine uses for addressing things like POP/IMAP accounts, remote
configuration & addressbook data, etc.



-- 
Chris Devers