HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
Organization: Cambridge Computer Associates, Inc.
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf"
X-VMS-Cc: TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 11 Sep 92 18:01:40 GMT
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      No-such-(Phonenet)-host bounce msg
Newsgroups: bit.listserv.pmdf-l

I have a somewhat cosmetic question on the issue of bounce messages.

Attached is a bounce message generated at gs.com.  Mail arrived through
camb.com (its Internet mail exchanger).  The node was unknown.  [It was
a misspelling, with an `oh' for a `zero'.]  The bounce message subject
was
  Subject: Undeliverable mail: PhoneNet de

Beside the fact that it is truncated, is this what is really wanted?
I expect that I can substitute my own message using the $? syntax with
a wild card rule.  [I'm the postmaster at both sites.]  Is this the
recommended course?

BTW, I was also confused by the chronologically first Received:-header.

  Received: from camb.com by gs.com (PMDF #2348 ) id <01GON9E23POW95MU9E@gs.com>
   ;
   Fri, 11 Sep 1992 04:53:32 EDT
  Date: 11 Sep 1992 04:53:31 -0400 (EDT)
  From: PMDF Mail Server <postmaster@gs.com>

This message is being generated on gs.com.  And yet it's claiming the msg
was received from camb.com.  That is where the msg causing the bounce came
from.  Is this what's intended?  It did confuse me at first.









Received: from gs.com by camb.com (PMDF #2344 ) id
 <01GONBEI7AHC90Q1TW@camb.com>; Fri, 11 Sep 1992 05:51:19 EDT
Received: from camb.com by gs.com (PMDF #2348 ) id <01GON9E23POW95MU9E@gs.com>;
 Fri, 11 Sep 1992 04:53:32 EDT
Date: 11 Sep 1992 04:53:31 -0400 (EDT)
From: PMDF Mail Server <postmaster@gs.com>
Subject: Undeliverable mail: PhoneNet de
To: BISEXU-L@BROWNVM.brown.edu
Message-id: <01GON9MIXNFE95MU9E@gs.com>
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Message failed for the following reason:
no addressees
unknown host or domain: user@ARONO1
----------------------------------------
Received: from camb.com by gs.com (PMDF #2348 ) id <01GON597U2OG95N40R@gs.com>;
 Fri, 11 Sep 1992 03:07:37 EDT
Received: from BROWNVM.brown.edu by camb.com (PMDF #2344 ) id
 <01GON4S4PAJK90QBWL@camb.com>; Fri, 11 Sep 1992 02:35:43 EDT
Received: from BROWNVM.BROWN.EDU by BROWNVM.brown.edu (IBM VM SMTP V2R2) with
 BSMTP id 0523; Fri, 11 Sep 92 01:36:55 EDT
Received: from BROWNVM.BITNET by BROWNVM.BROWN.EDU (Mailer R2.08 R208004) with
 BSMTP id 5830; Fri, 11 Sep 92 01:36:55 EDT
Date: 11 Sep 1992 01:35:00 -0400 (EDT)
From: kc55 <Kelly_K_COOKSON@UMAIL.UMD.EDU>
Subject: Re: teaching
In-reply-to: <9209101754.AA19696@umailsrv0.UMD.EDU>
To: Multiple recipients of list BISEXU-L <BISEXU-L@BROWNVM.brown.edu>
Reply-to: Bisexuality Discussion List <BISEXU-L@BROWNVM.brown.edu>
Message-id: <01GON4TKIASA90QBWL@camb.com>
X-Envelope-to: berryr@ARONO1
Content-transfer-encoding: 7BIT

..text deleted...
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"@mr.lilly.com:ipmdf%ymir.claremont.edu@in""
          @mr.lilly.com:ipmdf%ymir.claremont.edu@in"
Autoforwarded: false
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Importance: normal
Priority: non-urgent
Sensitivity: Private
UA-content-id: 11695A5F2300
X-Hop-count: 2
Date:         Fri, 11 Sep 92 19:14:50 GMT
From:         "Brett E. Bowman" <BOWMAN_BRETT_E@LILLY.COM>
Subject:      Digested lists and the Notes channel
Newsgroups: bit.listserv.pmdf-l

Has anyone come up with a method of using PMDF's Notes channel to post messages
into Notes, but also getting messages from digested lists split up into
multiple posts?  We used to use BBoard to do this, but since we've moved to
PMDF's Notes channel, I haven't come up with any good way to accomplish the
same thing.

                                                Brett E. Bowman
                                                Eli Lilly & Company
                                                BOWMAN_BRETT_E@LILLY.COM
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"TERRY@spcvxa.spc.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 14 Sep 92 22:46:55 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Limiting access to outgoing mail.
Newsgroups: bit.listserv.pmdf-l

Yes, putting notices 1 on the d_noexquota channel should have the desired
effect of returning messages after one day. The effect will not carry
over to any other channels.

I have completed the changes necessary to get noexquota to work right. We
are running it on a couple of systems for testing. If all goes well the
changes will go into the -13 revision level for PMDF V4.1.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"IPMDF@YMIR.CLAREMONT.EDU", IN%"NED@INNOSOFT.COM"  "Ned Freed",
          IN%"CRW@icf.hrb.com"  "Craig R. Watkins",
          IN%"DAN@INNOSOFT.COM"  "Daniel C. Newman"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 8 Sep 92 19:21:06 GMT
From:         "Jeffrey J. Carpenter" <jjc+@PITT.EDU>
Subject:      RE: BN_MASTER and SEND/FILE
Newsgroups: bit.listserv.pmdf-l

Thanks for all your help.

The JNET Manual for version 3.4 has the following paragraph (on page 6-11):

    SEND/FILE adds "W=destuser" to any options supplied with the
    /OPTIONS="text" qualifier.  It doesn't add "W=destuser" if "W=" or
    "EXTWTR=" is manually specified in /OPTIONS, nor does it add
    "W=destuser" if there's no destination user (sending to @NODE).
    This default for external writer is useful for sites that send files
    to MVS systems running JES2 and TSO.  It eliminates the need to
    specify the "destination user" twice in a SEND/FILE command, as in
    the following:

        $ SEND/FILE/OPTIONS="W=CHRIS" filename.dat CHRIS@MVSNODE

    /OPTIONS="" is the default.


The problem is that it ONLY adds the external writer by default as the
destination user if you also specify another option, such as
"/OPTIONS=FORM=blah".   There doesn't seem to be a way to have it ONLY
add the external writer by default.

What I ended up doing was creating a separate channel for our MVS
machine and creating an option file that had:

    OPTIONS=FORMS=STANDARD

The "FORMS" option seemed to be the safest one to specify.

In my previous message, I mentioned using "OPTIONS=W=".  Reading the
blurb above would lead you to believe that this would not include the
external writer field.  Joiner (I can't remember their new name) Tech
support told me that it would include it by default with "/OPTIONS=W=",
but it ends up that the manual is correct, and it did not.

Everything seems to be working ok now.

Thanks again.



        jeff
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"INFO-PMDF@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sun, 6 Sep 92 05:37:15 GMT
From:         "Jeffrey J. Carpenter" <jjc+@PITT.EDU>
Subject:      BN_MASTER and SEND/FILE
Newsgroups: bit.listserv.pmdf-l

Hi,

I am running PMDF 4.0, JNET 3.4, Multinet 3.0, and VMS 5.4-3.

We have a connection to an MVS machine on our campus via BITNET.  The
mailer on that machine really wants the External Writer field to be set
to the destination user.  If this is not done, it parses the headers for
the "To:" line, which causes unpleasant results.

By default, the SEND/FILE command comes from Joiner with "/OPTIONS" set
to "".   I see from the source that the Options file seems to be used to
create a "/OPTIONS=blah" switch on the SEND/FILE that BN_MASTER performs.

Here are my questions:

1. Can I add a "W=" to the options file to have it set use the options
as follows:

        SEND/FILE/OPTIONS="W="

2. Joiner Tech Support tells me it is safe to include "/OPTIONS="W=" to
have the external writer field filled in on each SEND.  Is that true?
Are there any NJE mail software packages that would not like this?  If
there are, what is the best way to have this option apply to our
specific host (or a specific queue)?


Thanks,


        jeff
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: Universite Claude Bernard. Lyon (France)
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
Date:         Tue, 15 Sep 92 17:06:04 GMT
From:         Gilles Rech <gilles@CISMHP.UNIV-LYON1.FR>
Subject:      The "Sender:" header and [exe]return.exe
Newsgroups: bit.listserv.pmdf-l

My configuration: PMDF 4.1-7 & VMS 5.5-1
[exe]return.com does not send the warning message to the "Sender:"
header address when this address is not embedded between "<",">"
characters. Some discussion lists sends mails with such a header, for
instance:

when
would work. It's a bit annoying because the warning message is sent to
the original author.

Another question: in PMDF 4.0, I could exclude a channel of the
"return" mechanism by setting the exclude_list symbol in [exe]return.com.
How can I achieve such a restriction in PMDF 4.1 ?
Thank in advance for any help.
Sincerely,
                Gilles Rech.
                C.I.S.M., Universite Claude Bernard Lyon I & INSA Lyon, France.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"TERRY@spcvxa.spc.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 11 Sep 92 21:56:55 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Limiting access to outgoing mail.
Newsgroups: bit.listserv.pmdf-l

>> I shall summarize below the new support so that anyone spotting any missing
>> functionality, blunders, or whatnot can bring them to our attention now,
>> well in time for the next release.  And of course, further ideas are always
>> welcome.
>>
>>    from_channel|from_address|to_channel|to_address     $Y/$N
>
>   I'd like to be able to specify keywords to override the channel parameters
> or the PMDF defaults as well. That way, I can set holdexquota as a channel
> keyword and noexquota for a particular "problem" user. Likewise, I can set
> sendpost/nosendpost for delivery errors to this address.
>
>   What do you think?

This is an interesting idea.  Before explaining the specifics of what can
or cannot be easily done, allow me to first explain what in general needs to
be done to implement such a facility.

PMDF channel programs all load and digest their channel keyword settings once,
when they first start up.  They then begin their processing loop to handle all
queued messages requiring handling.  It is in this loop, when an individual
message is being handled that the channel then knows specifics about the to and
from addresses for a given message.  Thus, it is here in this loop that channel
keywords would have be overridden on a per address (per message) basis.
This means going through all of the PMDF channels and adding new code
everywhere a channel keyword setting is acted upon.  A lot of work, needless to
say.

Note also that there are many keywords which it doesn't make sense or just
plain isn't possible to set on a per address basis (e.g., 733, bidirectional,
batch, etc.).

Now, for the specific things you mentioned, noexquota/holdexquota/exquota,
sendpost/nosendpost/errsendpost, and similar keywords, a few changes might
suffice.  For instance, the local and slave smtp channels are the only channels
which use the noexquota/holdexquota/exquota keywords.  Similarly, much -- but
not all -- of the message bouncing is done by a single routine and thus an
80% solution might be to only teach it about per address
sendpost/nosendpost/errsendpost settings.  (The channels which generate their
own "bounce" messages do so because the information they are returning doesn't
fit the standard bounced message format.)

So, my question is what channel keywords would prove useful to set on a per
address basis (in addition to the quota and postmaster bounce copy keywords)
and how acceptable will 80% solutions be.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"DMPM%DUKEMC.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 15 Sep 92 22:25:07 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: User defined directory service?
Newsgroups: bit.listserv.pmdf-l

> We have a database matching user full names, dept , ... to their mail id.
> I would like to interface this somehow into PMDF.  What I want to be
> able to do is to have a "user defined" directory capability.  For example,
> I may want to permit a query structure that is last.first@mc.duke.edu
> where one may have only a piece of that last name (i.e. would have to allow fo
   r
> combinations of possibilities as well as multiple identical names).
>
> As far as I can tell, PMDF only allows a one-to-one matching (i.e.  jim =
> dryfo001 or dryfoos.jim = dryfo001).  I would like to do more than this.
> Perhaps I need a rewrite rule that maps * to my homebrew channel?

No, this would have nothing to do with rewrite rules.  You'd identify all
addresses destined for your channel by the domain name (just like the
directory channel does).

>  Is this possible?  I have currently been adding an alias for all users that
> are not on the local system and that must go through my homebrew channel.
> Once in my channel, I can do anything with the destination address.
>
> Appreciate any responce or suggestions.  Sorry if I have just
> overlooked something that already exists.

You might consider using the directory channel as a starting point and
modify it (the code) to do your style of name matching.  Note also that there
is a channel called, I believe, Name Router, which does name matching of the
sort I think you're looking for.  Name Router was, if I recall correctly,
originally authored by Tom Wade.  It is available from various sites via
anonymous FTP.  (I don't keep track of which sites though.)

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"bthomas@drifter.uwyo.edu"
X-VMS-Cc: INFO-PMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sun, 6 Sep 92 05:16:43 GMT
From:         "Kevin V. Carosso" <KVC@INNOSOFT.COM>
Subject:      RE: PMDF Process Symbiont problems (with MR-NOTIFY)
Newsgroups: bit.listserv.pmdf-l

The %PMDF-W-MRLSUBERR error occurs when the process symbiont
cannot figure out what PMDF channel goes with the mailbox
name for which Message Router says it has a message ready for
pickup.

In your case, MR has sent us a notification message with a mailbox
name of "SMTP".  We have to figure out which channel goes with that
mailbox, and we couldn't -- generally that is indicative of a PMDF-MR
configuration problem.

First of all, make sure that SMTP really is the name of the PMDF-MR
mailbox and that there are no other Message Router mailboxes for
PMDF-MR.  Check that PMDF.CNF or MR.CHANS (whichever contains your
"mr_local" channel definition) refers to the proper mailbox.  If
you change this and you use a compiled configuration you need to
recompile.

If you still can't figure out what the problem is, contact
"service@innosoft.com" and we'll see what else we can look at.  Do not
contact me personally as I will be out of town next week.

        /Kevin Carosso
         Innosoft
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"NED@INNOSOFT.COM"  "Ned Freed"
X-VMS-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
X-Mts: smtp
Date:         Mon, 14 Sep 92 15:48:15 +1000
From:         andrewr@ITD.ADELAIDE.EDU.AU
Subject:      RE: Problems with cc:Mail channel.
Newsgroups: bit.listserv.pmdf-l
              <01GOP8H9AB1A9FM7LA@INNOSOFT.COM>

In message <01GOP8H9AB1A9FM7LA@INNOSOFT.COM> Ned writes:

+ I gather from this that you're entering cc:Mail addresses as
+
+     "user AT postoffice"@ccmail.whatever
+
+ on the Internet/PMDF side of things. This is incorrect and unsupported. The
+ proper form to use is
+
+     user%postoffice@ccmail.whatever
+
+ where any spaces in the user part are replace with underscores and any
+ commas are replaced with plus signs. This is the supported format; it is
+ also the format that will be produced by the slave channel program.

        OK, Thanks. The problem is that the documentation I have
(PMDF-REF-4.1) has minimal information on this.

+ What are you doing to force processing of the input file? Processing
+ is not automatic -- it cannot be since PMDF has no way of sensing the
+ creation of the input file. You have to arrange to do a
+
+     $ @PMDF_ROOT:[EXE]MASTER CC_LOCAL POLL

        When I try this, I get the following error message:

$ @PMDF_ROOT:[EXE]MASTER CC_LOCAL POLL
%DCL-I-SUPERSEDE, previous value of OPTION_FILE has been superseded
%PAS-F-ARRINDVAL, array index value is out of range
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           000AEE5C  000AEE5C
CC_SLAVE        DOSUBMIT                         4944      000004F8  00002D30
CC_SLAVE        CC_SLAVE                         5027      00000017  0000347B

        Now, according to "help errors supersede", this message
indicates a success state after redefining the logical name
OPTION_FILE, and requires no user action. As such, the first thing of
note is the Pascal error message.

+ at the proper time. The periodic job can be told to do this when it runs if yo
   u
+ mark the channel with the master channel keyword.

        I'm hesitant to do this until the above problem is resolved,
which it probably is in the current release.

+ What version of PMDF are you running. There have been a number of changes
+ and enhancements since the initial release. Please contact service@innosoft.co
   m
+ and request the most recent version if you're not running at least V4.1-10.

        ident="V4.1-A"

        Not sure what the latest release from our supplier is, will
contact service as requested if they don't dave -10 or greater.

Thanks,
        Andrew.

/*
 * Andrew Rutherford                 andrewr@itd.adelaide.edu.au
 * +61 8 228 5669            Real Programmers always confuse Christmas and
 * Room 1060, Adelaide Uni      Halloween because OCT 31 == DEC 25 !
 */
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Arnold Consulting
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@ymir"
X-VMS-Cc: ARNOLD
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 12 Sep 92 06:59:22 GMT
From:         "Stephen L. Arnold" <ARNOLD@ARNOLD.COM>
Subject:      RE: BN_MASTER and SEND/FILE
Newsgroups: bit.listserv.pmdf-l

Craig Watkins said:
> |> 2. Joiner Tech Support tells me it is safe to include "/OPTIONS="W=" to
> |> have the external writer field filled in on each SEND.  Is that true?
> |> Are there any NJE mail software packages that would not like this?
> | ...
> This is about as safe as you can get.  Jnet does it by default on
> outgoing mail.  Do it.

To add a bit more to this:

I see you are running Jnet V3.4.  I'd strongly suggest upgrading to the
current release.

There is no danger of setting The external writer on every BITNET mail
file.  It is required by many MVS systems, and it makes no difference to
other systems.

PMDF should do this by default, too.  Can we get this enhancement in the
next release?

Steve
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"jjc+@pitt.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 7 Sep 92 01:30:50 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: BN_MASTER and SEND/FILE
Newsgroups: bit.listserv.pmdf-l

> We have a connection to an MVS machine on our campus via BITNET.  The
> mailer on that machine really wants the External Writer field to be set
> to the destination user.  If this is not done, it parses the headers for
> the "To:" line, which causes unpleasant results.
>
> By default, the SEND/FILE command comes from Joiner with "/OPTIONS" set
> to "".   I see from the source that the Options file seems to be used to
> create a "/OPTIONS=blah" switch on the SEND/FILE that BN_MASTER performs.
>
> Here are my questions:
>
> 1. Can I add a "W=" to the options file to have it set use the options
> as follows:
>
>       SEND/FILE/OPTIONS="W="

You need to create an option file named PMDF_ROOT:[TABLE]channel_OPTION.;
where "channel" is the name of the channel (e.g., "bit_blah").  In this
option file place the option:

        OPTIONS=W=

This will cause BN_MASTER to use the qualifier /OPTIONS="W=".

> 2. Joiner Tech Support tells me it is safe to include "/OPTIONS="W=" to
> have the external writer field filled in on each SEND.  Is that true?

I have no idea.  Perhaps Ned knows.

> Are there any NJE mail software packages that would not like this?  If
> there are, what is the best way to have this option apply to our
> specific host (or a specific queue)?

To make this specific to one host, make the rewrite rule for that particular
host use a bit_xxxxx channel (where xxxxx is whatever you want it to be barring
duplications) and then, for that channel, set up an option file with the
OPTIONS=W= entry.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@innosoft.com"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 15 Sep 92 07:56:37 GMT
From:         C.SANTANA@CGNET.COM
Subject:      default host name as foreign host
Newsgroups: bit.listserv.pmdf-l

I have been attempting to do the following:
        In VMSmail, addressing a message To: in%username
                                             (no quotes or host/domain)

Instead of this being translated to:  username@localhost.localdomain,
I would like it to always translate to a particular foreign host.domain.

I have tried setting the official-host-name of my local channel to
the foreign host, and then adding the local host name as the
local-host-alias for EVERY channel in the channel/host table.
This did not work (the FROM address of a local message was always
assigned to the foreign host/domain) and also seems a bit unelegant,
if not downright dangerous.

Has anyone done this or have any ideas about how it could be done?

-Steve Ross, CGNET

NOTE:  REPLY-TO: sross@cgnet.com  (not where this msg came from)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU