Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to all of its recipients. The
following address(es) failed:
anton@localhost:
generated |cat >>$home/Mail/test/foo:
"cat" command not found for address_pipe transport
------ This is a copy of the message, including all the headers. ------
Return-path: <debian-devel@lists.debian.org>
Received: from localhost (mail.alfaskop.net) [127.0.0.1] (anton)
by camilla.emmerfors.net with esmtp (Exim 2.05 #1 (Debian))
id 10oBZJ-0001z3-00; Sun, 30 May 1999 21:48:25 +0200
Received: from murphy.debian.org (murphy.debian.org [209.41.108.199])
by mail.alfaskop.net (8.9.1a/8.9.1) with SMTP id UAA32374
for <anton@alfaskop.net>; Sun, 30 May 1999 20:03:49 +0200
Received: (qmail 25109 invoked by uid 38); 30 May 1999 18:02:50 -0000
Resent-Date: 30 May 1999 18:02:49 -0000
Resent-Cc: recipient list not shown: ;
X-Envelope-Sender: jbotha@dundee.lia.net
Date: Sun, 30 May 1999 19:59:03 +0200
From: Sarel Botha <sjb@dundee.lia.net>
To: Debian Developerslist <debian-devel@lists.debian.org>
Subject: Re: ip-{up,down} scripts
Message-ID: <[🔎] 19990530195902.A7074@jab.home>
Mail-Followup-To: Debian Developerslist <debian-devel@lists.debian.org>
References: <[🔎] 19990529202953.A3028@omega.dhis.org> <[🔎] 877lpr5pah.fsf@haitech.martin.home> <[🔎] 19990529221357.A1681@master.debian.org> <[🔎] 87wvxqu6vq.fsf@haitech.martin.home> <[🔎] 87r9nyd1qy.fsf@hasler.dhh>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <[🔎] 87r9nyd1qy.fsf@hasler.dhh>; from John Hasler on Sun, May 30, 1999 at 10:19:01AM -0500
Resent-Message-ID: <"PE7x9B.A.HIG.J1XU3"@murphy>
Resent-From: debian-devel@lists.debian.org
X-Mailing-List: <debian-devel@lists.debian.org> archive/latest/36910
X-Loop: debian-devel@lists.debian.org
Precedence: list
Resent-Sender: debian-devel-request@lists.debian.org
On Sun, May 30, 1999 at 10:19:01AM -0500, John Hasler wrote:
> Martin Bialasinski writes:
> > As I said, with the ipparam option, there is no problem distinguishing
> > the connections.
>
> I've been thinking of suggesting that pon use ipparam to pass the provider
> name to pppd. Pppconfig 2.0 will need that for the new dns stuff.
>
And then maybe a dir for each provider in /etc/ppp/ip-up.d ? I think that would solve everyone's problems. Just use the ipparam parameter which is handed to ip-up which then does a run-parts /etc/ppp/ip-up.d/$PROVIDER
--
-----------------------------------------------------------------------------
Sarel Botha | Computer & | +27 341 81341
(sjb@dundee.lia.net) | Accounting | BOX 2065, Dundee
| Services | 3000, South Africa
-----------------------------------------------------------------------------
"The End is near." -- http://www.geocities.com/Athens/Olympus/7771/666.htm
-----------------------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: