On machine A, the user creates a ~/.forward file such as this:
\user, user@B
Then, on machine B, the user creates this ~/.forward file:
\user, user@A
The intention is that the backslashed name (\user) will cause local delivery and the
second address in each will forward a copy of the message to the other machine.
Unfortunately, this causes mail to go back and forth between the two machines
(delivering and forwarding at each) until the mail is finally bounced with the error
message ???too many hops.???
On the machine that the administrator controls, a fix to this looping is to temporarily
edit the aliases database and insert an alias for the offending user, such as this:
user: \user
This causes mail for user to be delivered locally and that user??™s ~/.forward file to be
ignored. After the user has corrected the offending ~/.forward files, this alias can be
removed.
13.8.3 Appending to Files
The ~/.forward file can contain the names of files onto which mail is to be appended.
Such filenames must begin with a slash character that cannot be quoted. For example,
if a user wishes to keep a backup copy of incoming mail:
\user
/home/user/mail/in.backup
the first line (\user) tells sendmail to deliver directly to the user??™s mail spool file using
the local delivery agent. The second line tells sendmail to append a copy of the mail
message to the file specified (in.
Pages:
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902