Date: Fri, 4 Oct 96 15:06:10 PDT From: Snuffles@kew.com Subject: UUPC-Info-Request Digest 1996 #21 To: uupc-info-digest@kew.com Message-ID: Reply-To: UUPC-Info-Request@kew.com UUPC-Info-Request Digest Fri, 4 Oct 96 Volume 1996: Issue 21 Today's Topics: Administrivia Anybody manage to use Yarn with UUPC? MS Exchange client for UUPC/extended new configuration of mail at kew.com (2 msgs) problem calling REXX gateway with "|" in HOSTPATH (3 msgs) Problem with the first From line in mailboxes Putting email into news (3 msgs) SMTP and uupc (2 msgs) Snews and UUPC SYS Files again To subscribe to UUPC-Info-Digest, send the command in the body of a message to listserv@kew.com: subscribe uupc-info-Digest To signoff from UUPC-Info-Digest, use "signoff" instead of "subscribe". You can also send an "index" to the listserv to get an index of back issues and other files available for retrieval. Note: Questions on UUPC/extended itself which are not of general interest should be sent to help@kew.com, not to the mailing list. Nor questions should be posted on Usenet, we don't read it. (Much.) ---------------------------------------------------------------------- Date: Thu, 03 Oct 1996 08:56:58 -0400 From: Software@kew.com Subject: Administrivia To: UUPC/Extended mailing list UUPC_info has been changed from an open moderated list to a closed unmoderated list which anyone can join. This means several minor things: 1) Posts will be turned around faster 2) If you're not on the list, your mail bounces -- you'll be invited to join. (Digest readers are NOT technically on the list.) 3) Subscription requests will be filtered automatically if sent directly to the list, but the occasional unsubscribe request may slip through. Junk mail sent blindly to the list will also be rejected. The list remains under my direct control, and I reserve the right to moderate the list at any time. (Clearly, I don't current see the need.) Please do not post source code or solicitations to the list. -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 "And some they will and some they won't And with some it's just as well . . ." - Supertramp ------------------------------ Date: Tue, 01 Oct 1996 15:36:14 -0800 From: nfahmi@abdulla.pc.my Subject: Anybody manage to use Yarn with UUPC? To: UUPC/Extended mailing list Hi all, Just wondering whether anybody have succeded in using Yarn with UUPC? TIA. -- Nik Ahmad Fahmi e-mail: nfahmi@abdulla.pc.my 74744.1202@compuserve.com ... 640K ought to be enough for anybody. - Bill Gates, 1981 ------------------------------ Date: Tue, 1 Oct 1996 18:06:42 +0200 From: e8125949@student.tuwien.ac.at Subject: MS Exchange client for UUPC/extended To: UUPC/Extended mailing list I have just tried a shareware called "mail4u" that might be of interest for everybody who wants to use the Windows 95 Exchange client to exchange mail via uucp. I have found it at http://mail4u.home.ml.org Norbert e8125949@stud2.tuwien.ac.at ------------------------------ Date: Sat, 28 Sep 1996 20:03:49 -0400 From: Software@kew.com Subject: new configuration of mail at kew.com To: UUPC/Extended mailing list For the past several years, all Internet mail and in out of Kendra Electronic Wonderworks and its associated systems have been forwarded via UUCP to one of two systems on the Internet for processing: eddie.mit.edu or more recently pioneer.ci.net. (pioneer is our current primary feed and eddie, our favorite shipboard computer, remains our back up.) Our own connection to these systems has driven many of the releases of UUPC/extended, and our continued reliance on it for our remote sites in six states insures its continued welcome here. (Not to mention our database full of names we have of people we owe disks and/or manuals to. We haven't forgotton anyone-- we hope!) However, an event of some (mail) importance did take place today. With our PPP link and the recent addition of a small system running FreeBSD (a UNIX clone), Taylor UUCP and sendmail, we are now able to deliver to the outside Internet world directly. Today our primary UUCP system was reconfigured to deliver via UUCP over our LAN to the FreeBSD system for this direct delivery. This _should_ be transparent (pioneer.ci.net also delivered via sendmail on our behalf), but result in faster response time for both personal and bulk delivered messages. Inbound mail will also normally come via the new system. Pioneer and eddie remain as backups. This will allow me to work on some problems with UUCP mail we've seen, and also encourage me to work on a SMTP (Internet) mail gateway for UUPC/extended. It's also a neat toy, which means I could break the entire setup with one keystroke -- I'll try to avoid this. :-) In the near future, our FTP and web servers may also be moved to this new server. The names will remain the same, of course, as ftp.kew.com and www.kew.com. (ftp.clarkson.edu is no longer available, BTW, due to the system the files resided on being taken out of service.) Any questions, comments, problems should be directed to me via e-mail at postmaster@kew.com, or via telephone at 617-279-9812. -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 "You don't know how far I'd go to ease this precious ache You don't know how much I'd give or how much I can take Just to reach you, just to reach you, oh to reach you . . ." - Melissa Etheridge ------------------------------ Date: Sat, 28 Sep 1996 20:03:49 -0400 From: Software@kew.com Subject: new configuration of mail at kew.com To: UUPC/Extended mailing list For the past several years, all Internet mail and in out of Kendra Electronic Wonderworks and its associated systems have been forwarded via UUCP to one of two systems on the Internet for processing: eddie.mit.edu or more recently pioneer.ci.net. (pioneer is our current primary feed and eddie, our favorite shipboard computer, remains our back up.) Our own connection to these systems has driven many of the releases of UUPC/extended, and our continued reliance on it for our remote sites in six states insures its continued welcome here. (Not to mention our database full of names we have of people we owe disks and/or manuals to. We haven't forgotton anyone-- we hope!) However, an event of some (mail) importance did take place today. With our PPP link and the recent addition of a small system running FreeBSD (a UNIX clone), Taylor UUCP and sendmail, we are now able to deliver to the outside Internet world directly. Today our primary UUCP system was reconfigured to deliver via UUCP over our LAN to the FreeBSD system for this direct delivery. This _should_ be transparent (pioneer.ci.net also delivered via sendmail on our behalf), but result in faster response time for both personal and bulk delivered messages. Inbound mail will also normally come via the new system. Pioneer and eddie remain as backups. This will allow me to work on some problems with UUCP mail we've seen, and also encourage me to work on a SMTP (Internet) mail gateway for UUPC/extended. It's also a neat toy, which means I could break the entire setup with one keystroke -- I'll try to avoid this. :-) In the near future, our FTP and web servers may also be moved to this new server. The names will remain the same, of course, as ftp.kew.com and www.kew.com. (ftp.clarkson.edu is no longer available, BTW, due to the system the files resided on being taken out of service.) Any questions, comments, problems should be directed to me via e-mail at postmaster@kew.com, or via telephone at 617-279-9812. -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 "You don't know how far I'd go to ease this precious ache You don't know how much I'd give or how much I can take Just to reach you, just to reach you, oh to reach you . . ." - Melissa Etheridge ------------------------------ Date: Sat, 28 Sep 1996 10:39:47 -0400 From: MarchHare@mome.apk.net Subject: problem calling REXX gateway with "|" in HOSTPATH To: UUPC/Extended mailing list On Fri, 27 Sep 1996 16:09:29 +1200, stephen@digitech.co.nz wrote: >** Reply to note from alarie@ibm.net Tue, 24 Sep 96 09:30:43 -0500 >> >> Using UUCP/Ext 1.12r and Warp Connect. >> >> I'm having difficulty calling a REXX gateway using the "|" option in the >> HOSTPATH file. When the program is called the session crashes with >> register contents dumped to the screen. I can close the window from the >> window list and the rest of the sytem is not (does not seem to be) >> affected. > >It might be the same problem I encountered with piping in the >ALIASES file - when options=imfile is on, UUPC crashes. Try turning >imfile off. Silly me, I didn't even know that imfile was an option. I posted recently to UUPC-HACKERS about a problem with large encoded binaries when SOUPER pipes them to RMAIL. The failure always occurs in the imfiles module. It will write a seemingly random number of temporary files and then die. What, then, are the implications of turning it off? The description in the UUPC manual seem to imply that it will use temporary files instead of memory, which might not only slow performance but make the problem worse in this case. So, does turning it off increase the number of temporary files, or does it totally bypass the imfiles module? What is really aggravating is that there is no reported error in the logs, and no notification sent to the user that it failed. So, I had to be sitting here when it runs to even notice why outgoing mail was not going anywhere. Unfortunately, souper quits processing the file, as well, so any mail messages thereafter also get lost. I'm using souper15, BTW, if it makes any difference. John -- //------------------------------------------------------------------------ // momerath@apk.net sevot yhtils eht dna ,gillirb sawT` // MarchHare@mome.apk.net ebaw eht ni elbmig dna eryg diD // ,sevogorob eht erew ysmim llA // .ebargtuo shtar emom eht dnA In case of stupidity, break glass. ------------------------------ Date: Sun, 29 Sep 96 23:17:37 -0500 From: alarie@ibm.net Subject: problem calling REXX gateway with "|" in HOSTPATH To: UUPC/Extended mailing list On 09/27/96 at 04:09 PM, stephen@digitech.co.nz said: >** Reply to note from alarie@ibm.net Tue, 24 Sep 96 09:30:43 -0500 > >> Using UUCP/Ext 1.12r and Warp Connect. >> >> I'm having difficulty calling a REXX gateway using the "|" option in the >> HOSTPATH file. When the program is called the session crashes with >> register contents dumped to the screen. I can close the window from the >> window list and the rest of the sytem is not (does not seem to be) >> affected. > >It might be the same problem I encountered with piping in the ALIASES >file - when options=imfile is on, UUPC crashes. Try turning imfile off. That was it exactly. The REXX program parses the arguments fine with 'noimfile' set with the options statement. Now I'm puzzled by another problem. What would be the appropriate HOSTPATH entry to route all incoming mail to the gateway? Part of the difficulty may be that the domain is being stripped off all incoming mail and I can't figure out how to prevent that if I can. For instance, in the header for mail to dalarie@centre.com, only 'dalarie' appears in the To: field. If I try to pipe all mail ( *.centre.com | gateway) then inbound mail from the ISP is dumped to the postmaster because it is not addressed to a specific host in the domain, "centre.com" is stripped off, and there's no passwrd file entry for the user. If I try an entry for the local node plus domain name (host.centre.com | gateway), then I get an illegal/duplicate alias warning. So, if I want to divert all inbound mail to a gateway for distribution, then how do I structure the HOSTPATH entry to do that? -- ----------------------------------------------------------- Regards, Dave Alarie ----------------------------------------------------------- ------------------------------ Date: Sat, 28 Sep 1996 10:39:47 -0400 From: MarchHare@mome.apk.net Subject: problem calling REXX gateway with "|" in HOSTPATH To: UUPC/Extended mailing list On Fri, 27 Sep 1996 16:09:29 +1200, stephen@digitech.co.nz wrote: >** Reply to note from alarie@ibm.net Tue, 24 Sep 96 09:30:43 -0500 >> >> Using UUCP/Ext 1.12r and Warp Connect. >> >> I'm having difficulty calling a REXX gateway using the "|" option in the >> HOSTPATH file. When the program is called the session crashes with >> register contents dumped to the screen. I can close the window from the >> window list and the rest of the sytem is not (does not seem to be) >> affected. > >It might be the same problem I encountered with piping in the >ALIASES file - when options=imfile is on, UUPC crashes. Try turning >imfile off. Silly me, I didn't even know that imfile was an option. I posted recently to UUPC-HACKERS about a problem with large encoded binaries when SOUPER pipes them to RMAIL. The failure always occurs in the imfiles module. It will write a seemingly random number of temporary files and then die. What, then, are the implications of turning it off? The description in the UUPC manual seem to imply that it will use temporary files instead of memory, which might not only slow performance but make the problem worse in this case. So, does turning it off increase the number of temporary files, or does it totally bypass the imfiles module? What is really aggravating is that there is no reported error in the logs, and no notification sent to the user that it failed. So, I had to be sitting here when it runs to even notice why outgoing mail was not going anywhere. Unfortunately, souper quits processing the file, as well, so any mail messages thereafter also get lost. I'm using souper15, BTW, if it makes any difference. John -- //------------------------------------------------------------------------ // momerath@apk.net sevot yhtils eht dna ,gillirb sawT` // MarchHare@mome.apk.net ebaw eht ni elbmig dna eryg diD // ,sevogorob eht erew ysmim llA // .ebargtuo shtar emom eht dnA In case of stupidity, break glass. ------------------------------ Date: Mon, 30 Sep 96 17:21:02 +0200 From: sam@musical.fdn.org Subject: Problem with the first From line in mailboxes To: UUPC/Extended mailing list Why UUPC/Extended don't write mailboxes as regular Unix format ? the first From line contain some garbage characters... Sam --- Sam Przyswa System Operator Rock'n Jazz BBS Music & MIDI E-Mail:sam@musical.fdn.org Paris - France French Data Network - http://www.fdn.fr/ 33-1-4054-8604 ------------------------------ Date: Mon, 30 Sep 1996 09:25:22 -0500 From: cipav@cali.cetcol.net.co Subject: Putting email into news To: UUPC/Extended mailing list I have set up an email address to receive email from a particular listserv. I would like to have that email delivered to a news network, thats already functioning - so how do I get mail delivered from an email address into the news network. Thanks in advance, Nicholas Waltham ------------------------------ Date: Thu, 03 Oct 1996 00:15:10 +0000 From: eric@terra.xs4all.nl Subject: Putting email into news To: UUPC/Extended mailing list >>>>> cipav writes: > I have set up an email address to receive email from a particular > listserv. I would like to have that email delivered to a news > network, thats already functioning - so how do I get mail delivered > from an email address into the news network. Try something better: just use Gnus. -- Eric Veldhuyzen TEAM OS/2 Eric.Veldhuyzen@si.hhs.nl CIS: [100010,3051] Eric@terra.xs4all.nl PGP-KeyID: 0xFB64FCB3 ********** FIGHT to keep your right to PRIVACY. Use PGP! ********** ------------------------------ Date: Thu, 3 Oct 1996 08:20:14 -0500 From: cipav@cali.cetcol.net.co Subject: Putting email into news To: UUPC/Extended mailing list >>>>> cipav writes: > I have set up an email address to receive email from a particular > listserv. I would like to have that email delivered to a news > network, thats already functioning - so how do I get mail delivered > from an email address into the news network. Try something better: just use Gnus. Eric, Thank you for the hint - can you tell me what it is and where I can find it? Does it work under Windows 95? Thank in advance, Nicholas Waltham ------------------------------ Date: Thu, 3 Oct 1996 18:36:16 +0200 From: thomas@troehl.hanse.de Subject: SMTP and uupc To: UUPC/Extended mailing list I want to make Rockliffe MailSite and uupc work together. I receive mail via uupc and want to direct the mails for my domain to MailSite. MailSite is a SMPT/POP3 mailsever which works on Win NT/95 (I'm using NT). Does anyone now of a gateway ? thanks for your help Thomas ------------------------------ Date: Fri, 04 Oct 96 12:15:16 -0500 From: alarie@ibm.net Subject: SMTP and uupc To: UUPC/Extended mailing list On 10/03/96 at 06:36 PM, thomas@troehl.hanse.de said: >I want to make Rockliffe MailSite and uupc work together. >I receive mail via uupc and want to direct the mails for my domain to >MailSite. >MailSite is a SMPT/POP3 mailsever which works on Win NT/95 (I'm using >NT). Does anyone now of a gateway ? I don't know of a MailSite gateway, but I'm doing roughly the same thing, passing mail from UUPC to Inet.Mail, an OS/2 SMTP/POP3 server. Outbound is pretty easy using "rmail -t < msg.file" to queue mail for external systems. UUPC can pass off inbound mail in a couple ways. I'm currently using the vmail option to write the messages to a directory where I process them with a REXX procedure and call a delivery agent for Inet.Mail. I'm working on a procedure to handle delivery via the "|" operator in the HOSTPATH file. The HOSTPATH option requires less housekeeping and administration than the vmail setting which requires a discrete ALIASES file entry for each user. (Thank you Stephen Worthington. The "noimfile" setting cured the problems calling the REXX procedure from the HOSTPATH file.) The upshot is that it took less time to write the gateway than I spent looking for one that works with Inet.Mail. That holds, I suppose, as long as you know what arguments MailSite's delivery agent wants passed to it. It's pretty simple to filter the incoming message to create the necessary arguments. Sorry if this is just a manual rehash, but it's pretty fresh in my mind and I thought the summary might be useful. Hell, it might even be relatively accurate. -- ----------------------------------------------------------- Regards, Dave Alarie ----------------------------------------------------------- ------------------------------ Date: Sun, 29 Sep 1996 08:17:20 +4 From: dudley@gr8brdg.net Subject: Snews and UUPC To: UUPC/Extended mailing list Okay, I have everything working (I think) on Windows 95. I can use snews. I can do uucp. What the problem is is that when RNEWS runs it rewrites the moderator flags to "n" in the active file, and later on either rnews or newsrun rewrites the active file to zero length, followed by a zero-length complaint. What have I overlooked? I know the snews active format is different than the one in UUPC. I have put the "snews" option in the uupc.rc file. Has this occurred to anyone? cheers! {---> dudley@gr8brdg.net {---> Great Bridge Internet, Inc. {---> Check out www.gr8brdg.net! ------------------------------ Date: Sun, 29 Sep 1996 16:24:08 -0400 From: MarchHare@mome.apk.net Subject: SYS Files again To: UUPC/Extended mailing list OK, I just really, really don't understand this. The system generates a SYS file of the following: # News configuration file, automatically generated by UUPC/extended 1.12r # at Sun, 18 Aug 1996 11:18:33 -0400 # The local system, mome.apk.net (mome) ME:all # Our news feed, not batched to speed our posts mome:all/!local:L: Now, according to the docs with UUPC, the ME line looks OK. However, the other line confuses me. It is supposed to be for file transmissions. If I am transmitting files to myself, then it would follow that I would also want to transmit local distributions to myself. Also, according to the docs, if I create a new newsgroup hierarchy, momeraths.*, and I want to limit the newsgroup to my system, irregardless of the distribution put on it by the newsreader, then I would enter the site I'm transmitting to and limit the news distribution. However, the following results in NO newsgroups outgoing: # News configuration file, automatically generated by UUPC/extended 1.12r # at Sun, 18 Aug 1996 11:18:33 -0400 # The local system, mome.apk.net (mome) ME:all # A SYS line has four fields, separated by colons: # # system-name/exclusion1 exclusion2:subscriptions/distributions:flags:transmission command # The system name is the name of the system news is being sent # to, and is checked against site names in the news article # Path: headers to avoid sending an article back to a site # that has seen it. The exclusion names are also checked # against the Path: header and articles are not sent to system # name if they have visited any of the exclusions. (The spe- # cial system name ME stands for the name of the machine news # is running on, as determined from the nodename variable in # the local UUPC.RC file). # # The ME line, or a line whose system name is explicitly that # of the machine news is running on, has a rather different # meaning from that of the other SYS file lines: its subscrip- # tions subfield identifies the newsgroups that this site # subscribes to (i.e. is willing to receive), and its other # fields and subfields are ignored. There should be one such # line in the file.) # # subscriptions is a comma-separated list of newsgroup pat- # terns specifying the newsgroups to be transmitted to the # system; each newsgroup from the Newsgroups: header of each # article is matched against the pattern list, and if any # newsgroup matches the pattern list, the article is transmit- # ted. wariat:all,!momeraths/!local:L: The intent of the above is to transmit all newsgroups to wariat, except those beginning with momeraths and those marked for local distribution. However, it results in ALL newsgroups not going anywhere, even to the local system. The system-generated SYS file ends up sending all newsgroups, which is not what I want. Thanks, John-- //------------------------------------------------------------------------ // momerath@apk.net sevot yhtils eht dna ,gillirb sawT` // MarchHare@mome.apk.net ebaw eht ni elbmig dna eryg diD // ,sevogorob eht erew ysmim llA // .ebargtuo shtar emom eht dnA In case of stupidity, break glass. ------------------------------ End of UUPC-Info-Request Digest ******************************