Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA25812; Sat, 2 Dec 95 13:45:07 EST
Received: from post-ofc02.srv.cis.pitt.edu by MIT.EDU with SMTP
	id AA25599; Sat, 2 Dec 95 13:43:39 EST
Received: from local (root@localhost)
          by post-ofc02.srv.cis.pitt.edu (8.7.1/cispo-2.0.1.1)
          ID <NAA20989@post-ofc02.srv.cis.pitt.edu> for owner-kerberos@MIT.EDU;
          Sat, 2 Dec 1995 13:44:46 -0500 (EST)
Received: via switchmail; Sat,  2 Dec 1995 13:44:45 -0500 (EST)
Received: from post-ofc02.srv.cis.pitt.edu via qmail
          ID </afs/pitt.edu/service/mailqs/q5/QF.wkk9sc28XfY=JF7k58>;
          Sat,  2 Dec 1995 13:42:48 -0500 (EST)
Date: Sat,  2 Dec 1995 13:42:47 -0500 (EST)
From: Mailer-daemon <postman+@pitt.edu> (Postmaster, University of Pittsburgh)
Subject: Returned mail: Mailbox consistently over quota
To: owner-kerberos@MIT.EDU
Message-Id: <Ukk9sbO8XfY=NF7EBX@pitt.edu>
Organization: University of Pittsburgh
Postal-Address: University of Pittsburgh, Pittsburgh, PA 15260

The following message from ``owner-kerberos@MIT.EDU'' could not be
delivered to ``+dir-insert+/afs/pitt.edu/usr0/cljack/Mailbox@pitt.edu''
because:
The destination user has consistently been over quota for at least 4
days (since 28 Nov 1995 at 13:42:20 EST), preventing mail from being
delivered.  Please consider alternate methods for contacting this
person.  The specific error message is:  Can't write in dir
/afs/pitt.edu/usr0/cljack/Mailbox: Disc quota exceeded.

The undelivered message follows:
----------------
Received: from post-ofc02.srv.cis.pitt.edu via qmail
          ID </afs/pitt.edu/service/mailqs/sq3/QF.4kipUAi8XfY=E4lp9s>;
          Tue, 28 Nov 1995 13:42:21 -0500 (EST)
Received: from post-ofc03.srv.cis.pitt.edu via qmail
          ID </afs/pitt.edu/service/mailqs/q7/QF.MkipSGO8XfYb0MW05x>;
          Tue, 28 Nov 1995 13:40:20 -0500 (EST)
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28])
          by post-ofc03.srv.cis.pitt.edu with SMTP
(8.7.1/cispo-2.0.1.1)
          ID <NAA06069@post-ofc03.srv.cis.pitt.edu> for
<cljack+@pitt.edu>;
          Tue, 28 Nov 1995 13:38:08 -0500 (EST)
Received: from pad-thai.cam.ov.com by MIT.EDU with SMTP
	id AA06729; Tue, 28 Nov 95 12:37:41 EST
Received:  by pad-thai.cam.ov.com (8.6.12/)
	id <MAA18185@pad-thai.cam.ov.com>; Tue, 28 Nov 1995 12:41:13
-0500
Received: from GATEWAY by pad-thai.cam.ov.com with netnews
	for kerberos-wrapper@cam.ov.com (kerberos@mit.edu)
To: kerberos@MIT.EDU
Date: Tue, 28 Nov 1995 11:39:32 -0500
From: "Derrick J. Brashear" <shadow+@andrew.cmu.edu>
Message-Id: <kkinh4u00WCQMN3xZJ@andrew.cmu.edu>
Organization: Systems Group 82, Carnegie Mellon, Pittsburgh, PA
Sender: usenet@cam.ov.com
References: <4kh44ymSMV1b01W1dt@transarc.com>
Subject: Re: K4 principal attributes

Excerpts from netnews.comp.protocols.kerberos: 23-Nov-95 K4 principal
attributes by Pat_Barron@transarc.com 
> I've looked all through the docs, and poked around a bit in the code,
> and I can't find any documentation references to (or code that uses)
> the "attributes" that you can set on a V4 principal.  I'm I missing
> something fundamental, or does nothing in V4 use these?  Or are they
> meant to be application-specific?

Nothing in K4 uses these. Though, i have seen (and actually plan to do) 
implementations that do.

-D




----------------