Just so you all understand the reply/confirmation problem...
 
Say there is a host node on both BITNET and the Internet.  Say it is called
GPUVM on BITNET and VM.GPU.EDU on the Internet.  Say I subscribe from my
node (UCSFVM on BITNET and UCSFVM.UCSF.EDU on the Internet) by BITNET.
 
What the listserv sees for my node is UCSFVM (on BITNET).   It then sends
me the confirmation message.  Some brilliant piece of software notices
that we are both on the Internet, and sends me the confirmation message
that way.  Worst of all, it changes the From: of the conf msg to be
VM.GPU.EDU.  Now when I reply to that, my mailer generates a Internet
style address for me and the confirmation appears to come from
UCSFVM.UCSF.EDU, which is not a match to the node I subed from and so is
rejected as a confirm.   This is why using mail twice will work.  Both
of my outgoing From: addresses will be the same.   It would be nice if
Eric would enhance the "no good confirmation" message to say the node
from which the confirm was received and the node from which the original
sub was received when the userids agree.  That would make the problem
a lot clearer.   But the real bug is in the code which decides to "optimize"
the confirmation message by sending it to an address and from an address
other than the ones in the original sub.   Dave
 
Dave Gomberg, role model for those who don't ask much in their fantasy lives.
GOMBERG@UCSFVM  Internet node UCSFVM.UCSF.EDU             fax-> (415)731-7797