🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: vmsnet.mail.pmdf
Article #712

RE: mail.delivery question

#712
From: Daniel C. Newman
Date: Wed, 23 Dec 1992 17:16
45 lines
3228 bytes
> We are setting up a 'special distribution list' (only 8 users, so far) on
> our Vax; a special account (eg: DISTRIBUTOR) has got a mail.delivery file
> as the following:
>
> !from to subj | when action  param.     ! note
> !=======================================================
> *     *   *     A    J       "FAST"     ! submit this proc. on queue FAST
> *     *   *     A    V                  ! deliver a copy of the message
> *     *   *     A    L                  ! save the batch log
> *     *   *undeliver*  T   Q            ! don't forward to the list if this
>                                         ! message is a warning of problems
>                                         ! occurred during delivery
> *     *   *     A    F ""in%""""userA@vax.domain.it"""""   ! send to userA
> *     *   *     A    F ""in%""""userB@vm.domain.de"""""    ! send to userB
> etc.
>
> Each user, from different sites in Europe, send message to the DISTRIBUTOR
> and then the message is forwarded to the rest of the list; any suggestion
> to admit only the registered users having access to this service ? (We
> would like to filter 'occasionaly' message received by DISTRIBUTOR, e.g.
> advertisement, greetings ecc.)

Your best bet would be to not use DELIVER and instead set up a mailing list in
accord with Section 3.3.2.2 of the V4.1 PMDF System Manager's Guide and then
use the special "named parameters" to control access to that list.  These
parameters are described in Section 3.3.2.2.1 of the online documentation.
(They were not documented in time to make it into the printed manuals.)  If you
cannot use Bookreader, then you can look at the documentation sources: search
for the string "named parameters" in the file
PMDF_ROOT:[DOC]GUIDE_COMPONENTS.SDML.

If you set up a mailing list this way, then you might also consider using the
mail/list server supplied with PMDF V4.1 to manage the list.  In a separate
messge I will send you information on how to use all of its access control
mechanisms to manage the list.

If you wish to stick with DELIVER, then you need to set up a command procedure
to be run by DELIVER with an E action.  This command procedure would then check
the From: address of a potential submission against the list of registered
users and then only submit the posting if a match is found.  To submit the
posting use the command

 $ PMDF SEND/HEADER/BLANK 'MESSAGE_HEADER','MESSAGE_FILE' "userA@vax.domain.it"

Dan
Technical Details
Message-ID: <01GSNGXWI5UA9BVCTX@INNOSOFT.COM>
Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!sdd.hp.com!ux1.cso.uiuc.edu!moe.ksu.ksu.edu!mccall!ipmdf-newsgate!list

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!sdd.hp.com!ux1.cso.uiuc.edu!moe.ksu.ksu.edu!mccall!ipmdf-newsgate!list
Newsgroups: vmsnet.mail.pmdf
Subject: RE: mail.delivery question
Message-ID: <01GSNGXWI5UA9BVCTX@INNOSOFT.COM>
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 23 Dec 1992 10:16:52 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 23 Dec 1992 10:16:52 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSNGYG9U0I90NMRN@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"IORI%ITNCISCA.BITNET@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Lines: 45