[comp.mail.mh] UUCP not supported

gorpong@ping.chi.il.us (Gordon C. Galligher) (06/01/91)

When I try to send mail with an address like foo!bar!u, post gives me the
following error:

	To: ping.chi.il.us!gorpong
	Fcc: +obox
	X-Mailer: MH 6.7.1 #22[UCI] (ping) of Sat Feb 2 01:51:10 CST 1991
	Subject: This is a test
	--------
	Watch it blow up.

	What now? send

	ping.chi.il.us!gorpong: not supported; UUCP address
	post: 1 addressee undeliverable
	send: message not delivered to anyone

Post -help shows this:

	version: MH 6.7.1 #22[UCI] (ping) of Sat Feb 2 01:51:10 CST 1991
	options: [SYS5] [SYS5DIR] [DBM] [TYPESIG=void] [DUMB] [OVERHEAD] [ATZ]
	         [RPATHS] [MHE] [MHRC] [DBM] [MORE='"/usr/bin/more"']
	         [SBACKUP='"#"'] [MSGPROT='"0600"'] [FOLDPROT='"0700"']
	         [MMDFMTS] [MMDFII] [SPRINTFTYPE=int]

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!

		-- Gordon.
-- 
Gordon C. Galligher	9127 Potter Rd. #2E	Des Plaines, IL    60016-4881
gorpong@ping.chi.il.us    gorpong%ping@uu.psi.com   ...!uu.psi.com!ping!gorpong
   	We had V6, V7, System III, System V, and now Plan 9.
	 Next AT&T will say:  "Gee, I could have had a V8."

ziegast@UUNET.UU.NET (Eric Ziegast) (06/03/91)

"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