home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!rutgers!jvnc.net!darwin.sura.net!mips!swrinde!elroy.jpl.nasa.gov!decwrl!decwrl!infopiz!mccall!ipmdf-newsgate!list
- From: ned@sigurd.innosoft.com (Ned Freed)
- Newsgroups: vmsnet.mail.pmdf
- Subject: RE: question
- Message-ID: <01GNQFVHU2AO9BVFXH@SIGURD.INNOSOFT.COM>
- Date: 18 Aug 92 23:59:07 GMT
- Organization: The Internet
- Lines: 21
- Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
- Resent-Date: 18 Aug 1992 16:59:07 -0700 (PDT)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-ID: <01GNRIT10BB695NOFN@YMIR.CLAREMONT.EDU>
- X-Vms-To: IN%"wdw3@cunixb.cc.columbia.edu"
- X-Vms-Cc: IPMDF
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-Transfer-Encoding: 7BIT
-
- Sure -- anyone on the Internet can send to .BITNET addresses. It is very
- easy; you just use something like:
-
- user%host.bitnet@cunyvm.cuny.edu
-
- The gateway host cunyvm.cuny.edu is just one of several possibilities.
-
- The PMDF configuration procedure automatically generated a .BITNET rule
- for hosts that aren't on BITNET directly, so you can actually type in
-
- user@host.bitnet
-
-
- on a properly configured PMDF system that's only on the Internet and the
- address will be handled properly. The rewrite rule is something like:
-
- .bitnet $U@$H.BITNET@cunyvm.cuny.edu@MTCP-DAEMON
-
- This will vary depending on the TCP/IP implementation you use.
-
- Ned
-