* smtp mail delivery failure
@ 1994-10-10 14:17 postmaster
0 siblings, 0 replies; 3+ messages in thread
From: postmaster @ 1994-10-10 14:17 UTC (permalink / raw)
Attempt to deliver your mail to minster.york.ac.uk!forsyth, minster.york.ac.uk!mhw-plan9, minster.york.ac.uk!pete-plan9 reported the following:
---------- diagnosis ----------
rmail: pete-plan9 -- unknown user or mailbox
---------- unsent mail ----------
>From cse.psu.edu!plan9-fans Mon Oct 10 04:26:59 0400 1994 remote from inet
Received: by psuvax1.cse.psu.edu id <292341>; Mon, 10 Oct 1994 09:00:28 -0400
Received: from minster.york.ac.uk ([144.32.128.41]) by psuvax1.cse.psu.edu with SMTP id <292332>; Mon, 10 Oct 1994 08:59:52 -0400
From: forsyth@minster.york.ac.uk
Date: Mon, 10 Oct 1994 04:26:59 -0400
To: plan9-fans@cse.psu.edu
Message-ID: <swordfish.781793972@minster.york.ac.uk>
subject: b.com
Sender: owner-plan9-fans@cse.psu.edu
Precedence: bulk
Reply-To: plan9-fans@cse.psu.edu
which hard disc have you got on your 386/486 machine?
(ie, make, size, type)
you can try ftp'ing b.com from /pub/plan9/b.com on ftp.cs.york.ac.uk
to see if that is better (or worse!). there was a problem with the handling
of certain older drives, but i can't remember whether i fixed it in b.com
or devhard.c in the pc kernel.
^ permalink raw reply [flat|nested] 3+ messages in thread
* smtp mail delivery failure
@ 1994-10-10 18:01 Jeff
0 siblings, 0 replies; 3+ messages in thread
From: Jeff @ 1994-10-10 18:01 UTC (permalink / raw)
^ permalink raw reply [flat|nested] 3+ messages in thread
* smtp mail delivery failure
@ 1994-10-10 14:46 postmaster
0 siblings, 0 replies; 3+ messages in thread
From: postmaster @ 1994-10-10 14:46 UTC (permalink / raw)
Attempt to deliver your mail to minster.york.ac.uk!forsyth, minster.york.ac.uk!mhw-plan9, minster.york.ac.uk!pete-plan9 reported the following:
---------- diagnosis ----------
rmail: pete-plan9 -- unknown user or mailbox
---------- unsent mail ----------
>From cse.psu.edu!plan9-fans Mon Oct 10 10:17:00 0400 1994 remote from inet
Received: by psuvax1.cse.psu.edu id <292397>; Mon, 10 Oct 1994 09:24:43 -0400
Received: from minster.york.ac.uk ([144.32.128.41]) by psuvax1.cse.psu.edu with SMTP id <292332>; Mon, 10 Oct 1994 09:24:01 -0400
From: postmaster@minster.york.ac.uk
Date: Mon, 10 Oct 1994 10:17:00 -0400
To: plan9-fans@cse.psu.edu
Message-ID: <swordfish.781795430@minster.york.ac.uk>
Subject: smtp mail delivery failure
Sender: owner-plan9-fans@cse.psu.edu
Precedence: bulk
Reply-To: plan9-fans@cse.psu.edu
Attempt to deliver your mail to minster.york.ac.uk!forsyth, minster.york.ac.uk!mhw-plan9, minster.york.ac.uk!pete-plan9 reported the following:
---------- diagnosis ----------
rmail: pete-plan9 -- unknown user or mailbox
---------- unsent mail ----------
>From cse.psu.edu!plan9-fans Mon Oct 10 04:26:59 0400 1994 remote from inet
Received: by psuvax1.cse.psu.edu id <292341>; Mon, 10 Oct 1994 09:00:28 -0400
Received: from minster.york.ac.uk ([144.32.128.41]) by psuvax1.cse.psu.edu with SMTP id <292332>; Mon, 10 Oct 1994 08:59:52 -0400
From: forsyth@minster.york.ac.uk
Date: Mon, 10 Oct 1994 04:26:59 -0400
To: plan9-fans@cse.psu.edu
Message-ID: <swordfish.781793972@minster.york.ac.uk>
subject: b.com
Sender: owner-plan9-fans@cse.psu.edu
Precedence: bulk
Reply-To: plan9-fans@cse.psu.edu
which hard disc have you got on your 386/486 machine?
(ie, make, size, type)
you can try ftp'ing b.com from /pub/plan9/b.com on ftp.cs.york.ac.uk
to see if that is better (or worse!). there was a problem with the handling
of certain older drives, but i can't remember whether i fixed it in b.com
or devhard.c in the pc kernel.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~1994-10-10 18:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1994-10-10 14:17 smtp mail delivery failure postmaster
1994-10-10 14:46 postmaster
1994-10-10 18:01 Jeff
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).