home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!rutgers!jvnc.net!darwin.sura.net!mips!sdd.hp.com!swrinde!elroy.jpl.nasa.gov!ames!Drago.TGV.COM!MADISON
- From: madison@Drago.TGV.COM (Matt Madison)
- Newsgroups: vmsnet.networks.tcp-ip.multinet
- Subject: Re: no copy of returned mail to postmaster
- Message-ID: <1992Aug19.205354.17112@news.arc.nasa.gov>
- Date: 19 Aug 92 20:53:54 GMT
- References: <2D80054519AUG92161652@TGV.COM>
- Sender: usenet@news.arc.nasa.gov
- Reply-To: madison@tgv.com
- Organization: TGV, Incorporated
- Lines: 22
-
- In article <2D80054519AUG92161652@TGV.COM>, "Kasey Briggs, 792-2134" <BRIGGSK@Citadel.edu> writes:
- >We had a similar problem here caused by a Multinet default that you should
- >check. Multinet 3.0 set up a logical for postmaster (I can't remember exactly
- >what the logical was called; you can show logicals for *post and catch it if
- >it's there) which forwarded mail to System. We only use System for installs,
- >so nobody was getting the errors
-
- The logical name is POSTMASTER. That's what was causing your other problem:
-
- >Since this happened, we've taken the precaution of forwarding System's mail to
- >postmaster. My big complaint about Multinet's defaulting to System is that
- >it was messing up my BITNET error mail too.
-
- In MultiNet V3.2, the logical name MultiNet uses to identify the SMTP postmaster
- will change to MULTINET_SMTP_POSTMASTER, which should prevent the kind of
- interference you were having with Jnet. The logical will still default to
- SYSTEM if you don't tell it otherwise.
-
- -Matt
- --
- Matthew Madison | madison@tgv.com | +1 408 427 4366
- TGV, Inc. | 603 Mission Street | Santa Cruz, CA 95060 USA
-