Xref: utzoo comp.mail.headers:457 comp.mail.misc:1551 comp.mail.sendmail:412 comp.mail.uucp:2652
Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ncis.llnl.gov!ncis!helios.ee.lbl.gov!ace.ee.lbl.gov!leres
From: leres@ace.ee.lbl.gov (Craig Leres)
Newsgroups: comp.mail.headers,comp.mail.misc,comp.mail.sendmail,comp.mail.uucp
Subject: Re: Still trying to get smart routing working.
Message-ID: <1715@helios.ee.lbl.gov>
Date: 19 Jan 89 06:52:09 GMT
References: <412@execu.UUCP> <7094@xanth.cs.odu.edu> <412@avsd.UUCP>
Sender: usenet@helios.ee.lbl.gov
Reply-To: leres@helios.ee.lbl.gov (Craig Leres)
Followup-To: comp.mail.headers
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 19

Richard Childers writes:
> When I find .forward files in the LAN - usually as a result of receiving 
> mail that looped round and round, before ending up in my mailbox as a problem
> report from MAILER-DAEMON - I cat /dev/null into them and chown them to root
> and chmod the sucker to 444 and that's that.

This sounds gratuitously fascist to me. Luckly, it's not hard to remove
such a file:

    helios 7 % ls -l .forward
    -r--r--r--  1 root            0 Jan 18 22:40 .forward
    helios 8 % rm .forward
    rm: override protection 444 for .forward? y
    helios 9 % ls -l .forward
    .forward not found

The advanced reader might want to use "rm -f .forward"

		Craig