home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!gatech!paladin.american.edu!auvm!CC.UVCC.EDU!COLEVE
- Return-path: uucp@mccall.UUCP
- Errors-to: epmdf@YMIR.BITNET
- Organization: Utah Valley Community College
- X-Envelope-to: PMDF-L@IRLEARN.BITNET
- X-VMS-To: IN%"ipmdf-newsgate@mccall.UUCP"
- Content-type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-transfer-encoding: 7BIT
- Message-ID: <01GNOQT2KAHU95NFDH@YMIR.CLAREMONT.EDU>
- Date: Mon, 17 Aug 92 21:14:40 GMT
- Sender: PMDF Distribution List <PMDF-L@IRLEARN>
- Comments: Warning -- original Sender: tag was news@PARK.UVCC.EDU
- From: coleve@CC.UVCC.EDU
- Subject: RE: Problem with printer channel?
- X-To: ipmdf-newsgate@mccall.UUCP
- Newsgroups: bit.listserv.pmdf-l
- Lines: 22
-
- In article <01GNNMC2FAKY8WXYL0@ucsvc.ucs.unimelb.edu.au>,
- c.chaundy@its.unimelb.edu.au writes:
- > Prior to PMDF V4.1, we had a simplistic printer channel setup which just
- > read the list of files to be processed in MASTER.COM and took the 'to'
- > address and used the /note switch to print the message out on SYS$PRINT.
- >
- > With V4.1, I want to upgrade to use the standard PMDF printer channel and
- > wondered how it reacted if the mailbox part of the 'to' address was not a
- > AVPL to avoid having to re-educate users and make bulk changes to a huge
- > number of directory channel files - I got the answer - *badly*.
- [...]
- > Apart from the fact that I will have to move to AVPL pairs (it would have
- > been nice to default mailboxes that are not AVPL pairs to just 'Attention:'),
- > I assume this other behaviour is most definitely a bug in the printer channel.
- >
-
- I'm trying a rewrite rule like:
- HARDCOPY.UVCC.EDU /AT=$U@HARDCOPY.UVCC.EDU
-
- seems to do the job...
- --
- -- Vern Cole -- Systems Manager -- Utah Valley Community College --
-