My contribution to this discussion is going to be this: Don't delete the mail. Keep it around somewhere, and browse it occasionally for false positives.
C On Wed, 2002-04-03 at 07:44, Sundial Services International, Inc. wrote: > Gentlebeings... you are all on high-speed links and you're thinking "set up > your own POP server..." As though that were no problem. > > And no, it's not that I don't know just how to do just that. But my > particular circumstances preclude that approach. In effect I need to (doing > the entire job non-root from an ordinary user account) periodically query > the mail on a server ... run it through filtering but also cross-comparison > ... and delete the mail I don't want to log on [think TELEPHONE DIALUP, > think POOR LINES] and laboriously retrieve. > > And I really -do- need to do it _that _way. > > > > > At 07:26 AM 4/3/02 -0800, Rob McMillin wrote: > >Sundial Services International, Inc. wrote: > > > >>Here's my problem. We use an external ISP to handle our mail, and of course > >>we are getting pummeled with spam so fast that the mailbox can fill up > >>within hours. We use a different ISP to handle the web-site and can set up > >>programs on that. > >> > >>What I want to do, unless it has already been done, is to construct a Perl > >>script that can then be run periodically as a cron-job. What this script > >>would do is to interrogate each of the mailboxes we use, determine what's > >>spam among them, and delete those messages so that only they come down the > >>line when we download mail. > >> > >Ha! Fancy you should mention it. I have a friend who is in a very > >similar situation. He has a publically visible mail address that he > >*cannot* get rid of -- it's his business mail, and has been visible on > >his site since he opened shop over five years ago. It's hosted at the > >mailserver of the company that bought his business. He gets 100+ spams > >to this address daily. What you want is to set up a separate server with > >its own POP3 server, and use fetchmail with the following ~/.fetchmailrc > > > >poll <pop3_servername> protocol pop3 username <username> password <pwd> > >mda "/usr/bin/procmail -d %T" > > > >for each affected account, assuming you use POP3 to pick up your mail. > >Then, follow the usual installation/delivery instructions for > >SpamAssassin, and change all your mail clients to point to the new mail > >server for delivery. It's not quite what you're asking for, because it > >sounds like you're using IMAP for delivery, but I think it's the best > >you can do under the circumstances. > > > >-- > > http://www.pricegrabber.com > > "We are smarter individually." -- Larry Niven > > > > > > > > > > > > > > Sundial Services International Inc. > ============================================================= > - Scottsdale AZ (480) 946-8259; fax (480) 874-2068 > - Innovative solutions for complex database issues! > - http://www.sundialservices.com/ > - PGP public key at http://www.sundialservices.key/pgp.key > > > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk > > _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
