On (10/06/03 03:24), Pigeon wrote: > On Tue, Jun 10, 2003 at 12:49:45AM +0100, Clive Menzies wrote: > > On (09/06/03 17:36), Pigeon wrote: > > > On Mon, Jun 09, 2003 at 02:38:42PM +0100, Clive Menzies wrote: > > > > And I'm still struggling with my set up .... not > > > > managed to implement procmail yet and the cron job to "getmail" is being > > > > mailed to me every 5 five minutes... but that's another story;) > > > > > > Re procmail: I haven't found any need for this; personally I find that > > > setting up Exim filtering rules in my ~/.forward, which may call > > > shellscripts, suffices for my needs (delivering to different > > > mailboxes, stripping off standard footers). Exim's language is a bit > > > more legible than procmail's... (Useful command option: exim -bm. > > > Handy for feeding a footer-stripped message back into the mail system > > > for final delivery) > > Do you also use this for filtering spam? I was thinking > > procmail/spamassassin ... > > Ah, right. I haven't installed any spam-filtering tools yet because > only recently has it begun to be a problem, and then more because of > the offensive content than the volume; I am currently in process of > accumulating a corpus of spam to feed to a Bayesian filter to start it > off. I've sort of ruled out spamassassin because of its reputation for > being a resource hog (due to personal conceptions of elegance rather > than shortage of resources). So the following paragraph is not based > on actual experience :-) > > Since Linux anti-spam tools tend to operate as spam-taggers, and leave > other programs to do the filtering based on the tags, I don't see any > particular reason you couldn't have a set of filtering rules that say: > if tagged as spam, save in the "spam" box; if as ham, carry on with > normal ham filtering; if untagged, pass to spam-tagger, which adds > tags, then feeds the tagged message back in with exim -bm. > I've done the easy bit below - this will have to wait until I've sorted NIS, NFS and Samba - but thanks - it's given me some idea of which direction to go in. I couldn't get procmail to work at all but somebody suggested it was because the cron job e-mails were hijacking the recipes - I didn't know enough to tell. But I'll come back to all this soon....I hope;)
> > > Re cron job: modify it so that the command output which is currently > > > being mailed to you is redirected to /dev/null. > > > > Sorry to be dense ;) Can you be a bit more explicit? > > Easiest with an example, I think... Sometimes my main box can't use > the network after booting unless the networking services on the > gateway, which is headless, are restarted as well. So I have a cron > job on the gateway to periodically ping the main box and restart the > networking if it can't get through. The command I run (with crontab > gubbins snipped; pigeon is the name of the main box) is: > > ping -c 4 pigeon > /dev/null || /etc/init.d/networking restart > /dev/null > Wow! Pigeon you've changed my life ;) I've been thinking: "I must get round to sorting these wretched cron job e-mails" - I looked in muttrc, getmailrc, man crontab etc. It wasn't a huge priority but a persistent irritation. * * * * * /usr/bin/getmail > /dev/null so simple, so elegant and it works! Thanks a bunch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
