Problem
A Hewlett Packard network printer has been configured as an AFPS shared printer. If a print request is made from an AFPS Microsoft Windows 95 client to this printer share, the print request does actually print, but the "root" user at the local UNIX system is notified by mail(C) that the same print request has been canceled by the printer administrator user account "lp". The message received is similar to:
To: lp@testsco.x.y.com
Subject: Failed mail
Date: Wed, 14 May 97 11:26:58 BST
Message-ID: <9705141126.aa01747@testsco.x.y.com>
Status: RTrouble sending mail on testsco.x.y.com:============ Transcript follows ============(USER) Unknown user name in "ADMINISTRATOR" Submit error: No valid addresses
============== Message follows =============
From: lp@testsco.x.y.com (Printer administrator)
X-Mailer: SCO OpenServer Mail Release 5.0
To: ADMINISTRATOR
Subject: Status of lp request.
Date: Wed, 14 May 97 11:26:57 BSTSubject: Status of lp request print1-293Your request print1-293 destined for print1 was canceled by the administrator.
A similar mail message is received whenever a print request is made to this particular printer. On a very busy system, these mail messages may consume a large amount of disk space.
The LP scheduler, lpsched(ADMN), initially attempted to notify the submittor of the print request, the AFPS user "ADMINISTRATOR" in this case, that it had been canceled. This failed as it is not an existing UNIX user. It was then rerouted to the "root" user of the system.
This problem has been observed in cases where large print requests, greater than 280 KB, are sent to print in rapid succession from a Microsoft Windows 95 client, and also in cases of only a single small print request being sent. The pattern does not appear to be consistent.
Solution
This problem has been reported to SCO Engineering.
The mail may be deleted manually or a ".maildelivery" file may be placed in the UNIX user's home directory, if that user has been mapped to an AFPS account, which could delete any lp originating mail. For example:
# header content action result filename/command
# Header: From, To, cc, Subject, Sender, *
# Content: pattern
# Action: file, pipe, destroy
# Result: A (ok=delivered), R (not delivered), ?
(if not accepted already)
#* - pipe R rcvtrip $(sender)
#
...
...
From lp@testsco.x.y.com destroy A -