Article View: comp.mail.sendmail
Article #2678Re: .forward on multiple systems
From: Eric Allman
Date: Wed, 13 Jan 1993 00:40
Date: Wed, 13 Jan 1993 00:40
22 lines
1401 bytes
1401 bytes
In article <1993Jan12.214702.20374@alw.nih.gov>, weisen@alw.nih.gov (Neil Weisenfeld) writes: |> I have what is probably a common problem. I want to have a .forward |> such as the following: |> |> "|/xxx/yyy/zzz/bin/program" |> |> so that "program" will work like ``deliver'' to deliver my mail. Now, the |> problem is that my home directory is mounted by a hundred or so machines |> of different architectures. (further detail deleted) This may not be optimal for you -- but the new Berkeley version can define a ".forward path". For example: OJ$z/.forward.$j:$z/.forward would first look for .forward.hostname, and if that was not found would try .forward. You would then put the invocation of the program in .forward.daedalus.dcrt.nih.gov and "weisen@daedalus.dcrt.nih.gov" in .forward. eric
Technical Details
Message-ID:
<1ivoeb$eem@agate.berkeley.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!spool.mu.edu!agate!mastodon.CS.Berkeley.EDU!ericReferences:
<1993Jan12.214702.20374@alw.nih.gov>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!spool.mu.edu!agate!mastodon.CS.Berkeley.EDU!eric From: eric@CS.Berkeley.EDU (Eric Allman) Newsgroups: comp.mail.sendmail Subject: Re: .forward on multiple systems Date: 13 Jan 1993 00:40:43 GMT Organization: UC Berkeley Mammoth Project Lines: 22 Sender: eric@mastodon.CS.Berkeley.EDU (Eric Allman) Distribution: world Message-ID: <1ivoeb$eem@agate.berkeley.edu> References: <1993Jan12.214702.20374@alw.nih.gov> Reply-To: eric@CS.Berkeley.EDU NNTP-Posting-Host: mastodon.cs.berkeley.edu