🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: vmsnet.mail.pmdf
Article #733

Use of reverse database and affect on requesting Bitnet files.

#733
From: James Dryfoos- Postmaster
Date: Sun, 03 Jan 1993 19:02
37 lines
2868 bytes
We have been reverse mapping all mail through our PMDF node for sometime now.
One side affect I noticed was that mail going out our Bitnet link to listservs
would result in the listserv sending a file (sometimes mail) back to the
sending ID (as we are directly on the Bitnet).  When the file arrives, JNET
sees that this user does not exist on the local system and sends the file to
Postmaster (as defined in the JNET startup).  I have written a simple DCL
program that grabs all files in the postmaster area, looks to whom each was
really sent, and forwards them on as an e-mail message.

Is anyone else doing anything like this?
Are there any plans for PMDF to support this?
I have not played with JNET's API stuff, but am sure something that is less of
a hack can be done.  Anyone do this?

I have not even contemplating supporting anything but text files (have not
needed to so far).  This might be an interesting thing for PMDF to do.  It
coulld take the incoming files and put them into Mime parts?

As an example, user X on system Y would normally have a return address
of x%y@dukemc, but we rewrite it do standard_id@dukemc and send it out.
A listserv sends back directly to standard_id@dukemc.  For mail this works out
fine as a corresponding alias of standard_id@dukemc gets rewritten to x%y.
However, incoming Bitnet files never get touched by PMDF.  As there is no VMS
account standard_id on our system. the file is delivered to postmaster.


Thanks in advance,

--Jim

  ==========================================================================
     James D. Dryfoos                   |  E-Mail:
     Medical Center Information Systems |    dryfo001@mc.duke.edu
     Duke University Medical Center     |    dryfo001@dukemc.bitnet
     Box 3900 DUMC                      |  (919) 286-6391 - Office
     Durham, NC 27710 USA, Earth        |  (919) 286-6369 - Fax
  ==========================================================================
Technical Details
Message-ID: <01GT31PBKL4I00CWKR@mc.duke.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!unixhub!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!crdgw1!rpi!usc!wupost!crcnis1.unl.edu!moe.ksu.ksu.edu!mccall!ipmdf-newsgate!list

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!unixhub!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!crdgw1!rpi!usc!wupost!crcnis1.unl.edu!moe.ksu.ksu.edu!mccall!ipmdf-newsgate!list
From: dmpm%dukemc.bitnet@ymir.claremont.edu (James Dryfoos- Postmaster)
Newsgroups: vmsnet.mail.pmdf
Subject: Use of reverse database and affect on requesting Bitnet files.
Message-ID: <01GT31PBKL4I00CWKR@mc.duke.edu>
Date: 3 Jan 93 19:02:34 GMT
Organization: Duke University Medical Center, Durham NC, USA
Lines: 37
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 03 Jan 1993 14:02:34 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GT2VPFRSXU90OFAI@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT