Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!IUP!MJSTRAW From: MJSTRAW@IUP (Mark Strawcutter) Newsgroups: bit.listserv.pmdf-l Subject: exquota Message-ID: <900206.12405095.001905@IUP.CP6> Date: 6 Feb 90 17:47:00 GMT Sender: PMDF Distribution List Reply-To: PMDF Distribution List Lines: 20 Approved: NETNEWS@PSUVM Gateway Errors-to: postmast@YMIR.BITNET X-Orig-To: ipmdf@ymir X-Envelope-to: PMDF-L@IRLEARN.BITNET X-VMS-To: ipmdf@YMIR.CLAREMONT.EDU Comments: Warning -- RSCS tag indicates an origin of POSTMAST@YMIR X-To: ipmdf@YMIR John Payne writes: . . . >I haven't looked at the problem seriously, but I did notice that the >problem doesn't seem to be PMDF specific. Under VMS 5.2, a process >with EXQUOTA (or even just SETPRV) can deliver mail to an over-stuffed >account via vanilla VMS Mail, where an unprivileged user gets a quota error. . . . We're relatively new to all this. We're running JNET 3.4 and just got our PMDF tapes. We've noticed that JNET re-installs MAIL with EXQUOTA. This means that disk quotas are pretty useless. Anyone (priv or no) can send mail to a user who has exceeded his quota. Joiner claims MAIL's gotta have EXQUOTA. sigh. Does PMDF need it, too? Mark Strawcutter