Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!UUNET.UU.NET!ziegast
From: ziegast@UUNET.UU.NET (Eric Ziegast)
Newsgroups: comp.mail.mh
Subject: Re: UUCP not supported (MH6.7.1)
Message-ID: <9106022220.AA13967@rodan.UU.NET>
Date: 2 Jun 91 22:20:56 GMT
References: <1991Jun01.112245.6514@ping.chi.il.us>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 21

"Gordon C. Galligher" writes:
> 	To: ping.chi.il.us!gorpong
> 
> What am I missing?  Before I got it working with MMDFII the UUCP part of it
> worked.  Now that I have it with MMDFII, it no longer works.  Something is
> wierd, and my last cry for help apparently fell upon deaf ears.  I would
> appreciate any tidbits of information anyone could throw my way.  Thank you!

Perhaps MH is balking because there are no "@"'s in the address.

Look at the BANG under "options" in the READ-ME.  It tells MH to prefer
UUCP addresses (bang paths) over (@).  It might help. :)  It might not. :(

To help you debug, try using:

	send -nopush -watch -verbose

at the whatnow prompt to see how it handles your message.

--
Eric W. Ziegast - jr uunet postmaster - ziegast@uunet.uu.net