Date: Sun, 11 May 97 16:06:10 EDT From: Snuffles@kew.com Subject: UUPC-Info-Request Digest 1997 #10 To: uupc-info-digest@kew.com Message-ID: Reply-To: UUPC-Info-Request@kew.com UUPC-Info-Request Digest Sun, 11 May 97 Volume 1997: Issue 10 Today's Topics: Bouncing wrong addresses & Pegasus gateways earthlink.net to banned on 5/5/1997 mis-directed? personal mailer RMAIL on a network (3 msgs) SMTP support in UUPC/extended tcpip issues UNIX sendmail testers uucico aborting at line 590 UUCP/SMTP Gateway (2 msgs) UUPC/extended uupc cofiguring help 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: Fri, 25 Apr 1997 23:40:45 -0500 From: "Drew Derbyshire - UUPC/Extended Support" Subject: Bouncing wrong addresses & Pegasus gateways To: "Michael Hughes" On Fri, 23 Aug 1996 21:46:49 -0600, "Michael Hughes" wrote: > I am using UUPC/extended v1.12r under Windows NT 3.51 and have a > question about bouncing incorrectly addressed email back to the sender. > Currently, misdirected email gets sent back to the mail server instead > of the person in the From: field. What am I doing wrong and what do I > do to correct this? I would be happy to send you more detailed > information, such as configuration files and/or a copy of a bounced > email message, if necessary. Just let me know. I think it's a bug, pure and simple. Not fixed in 1.12s, which I'm trying to test and ship, but soon after (1.12t), because others have reported it as well. > Also, would you happen to know of any good gateways for transferring > mail messages between UUPC and Pegasus Mail? Good? Ah ... Look at the rmail gateway function/ > UUPC has worked very well for me thus far under NT. If I can get this > bounce problem figured out I will register my copy. Registering your copy will encourage me to fix the bounce. We are, unfortunately, running a major negative balance here and may have to shutdown the ftp/web service because of it. -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 "That which thy fathers have bequeathed to thee, earn it anew if thou wouldst possess it." - Goethe "Faust" ------------------------------ Date: Thu, 01 May 1997 08:08:31 -0500 From: "UUPC Postmaster" Subject: earthlink.net to banned on 5/5/1997 To: spam@earthlink.net, ki-info@kew.com, Earthlink.net has yet to give a proper (human) reply to our _repeated_ complaints on their forwarding SPAM from third-party sites. Unless we do receive an update from them, ALL mail from earthlink.net will banned at the kew.com gateway on Monday, May 5, 1997. Before this is done, all earthlink.net users will be dropped from our mailing lists (while we could continue to send them mail, they could not resign from the lists.) Note that I do not claim earthlink is originating the mail, but their failure to maintain their sendmail in a reasonable fashion and prevent such relaying is absurd given the exploitation of _their_ resources and annoyance of the receivers. The latest example of the offending mail will br forwarded directly to spam@earthlink.net. I see no reason to abuse the lists with the junk. ------------------------------ Date: Sat, 26 Apr 1997 23:56:33 -0500 From: "Drew Derbyshire - UUPC/Extended Support" Subject: mis-directed? To: ken@kgwcal.cuug.ab.ca I think you wanted to send this to uupc-info or uupc-hackers, not just me. Note that the post will be rejected if you have "Return-Receipt-To:" enabled, we reject such headers to prevent 200 mail messages come flying back at posters (or US). > From: Ken Wiens > To: "'software@kew.com'" > Subject: mailers for NT4 > Date: Sat, 26 Apr 1997 08:47:39 -0600 > Return-Receipt-To: > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > In keeping with Drew's move from OS/2 to NT (did I get that right?), I = > have followed suit (it's really not very good in comparison to OS/2 - = > maybe in another 5-10 years). Anyway - whats available by way of a = > mailer for NT that works with uupc? OS/2 actually had some really good = > mailers that worked with UUPC - are there any available for NT? > > TIA > > Ken Wiens > =20 -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 Cannot find REALITY.SYS. Universe halted. ------------------------------ Date: Sat, 26 Apr 1997 23:38:32 -0500 From: "Drew Derbyshire - UUPC/Extended Support" Subject: personal mailer To: "=?iso-8859-1?q?K.-P.__Kirchd=F6rfer?=" On Sat, 26 Apr 97 11:31:01 +0100, "=?iso-8859-1?q?K.-P._Kirchd=F6rfer?=" wrote: > On Fri, 25 Apr 1997 23:08:34 -0500, Drew Derbyshire - UUPC/Extended > Support wrote: > > >> Good news. A word about new features, like smtp, or major bug fixes? > > > >smtp is doubtful for may 1997. Numerous small bug fixes in news, imfile > >support, and perhaps UUCP From lines. > > Ok; a last, more general question. > Will we see the same support in the future for UUPC/extended as in > the old days in 94/95? > I mean it has been an unusual long time since 1.12r, your really > behind with mails. I know about some of the reasons, you had > explained them on the list, no criticism from here. I prefer not predict any more, but I hope for an improvement over '96. It will not be up to the levels of pre-94, it may match the quieter times of 95-96. -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 Cannot find REALITY.SYS. Universe halted. ------------------------------ Date: Thu, 8 May 1997 09:20:32 GMT-10 From: Peter Richards Subject: RMAIL on a network To: uupc-info@kew.com Hi, The setup here is a WIN for Workgroups LAN running Pegasus Mail and using UUPC software as the mail gateway. I can read/write the Pmail folders from either computer on the LAN, but only successfully use RMAIL on the (local) computer to spool mail. Have had several attempts at trying to get RMAIL to 'push' the spooled files across the network. Here is the log file: 05/07-14:27 RMAIL: UUPC/extended 1.12k (Dec 11 1994 12:33:55) (4) rmail argv[1] = "-x" (4) rmail argv[2] = "10" (4) rmail argv[3] = "-t" (4) rmail argv[4] = "-f" (4) rmail argv[5] = "c:\tmp\95D7EDA0.pm" (5) inithost: Allocated room for 32 host entries (2) Run time library error in d:\src\uupc\lib\hostable.c at line 486 ... (0) C:/PMAIL/systems: No such file or directory (1) Extended DOS Error Information: Number = 2, Class = 8, Action = 3, Locus = 4 (0) RMAIL aborting at line 487 in file d:\src\uupc\lib\hostable.c I was running RMAIL from c:\pmail directory; does the 'no such file' require the 'systems' file to be in the same directory ? (It is on the computer I am trying to send spooled mail to). Peter ----------------------------------------------------------------- ( (|) ) | Peter & Kathy Richards | | Jehoshua Computing /^\ | 16 Perry Avenue Phone: (047) 517220 Christ to | Springwood NSW 2777 Fax: (047) 517220 the World | Australia By Radio | Email: Peter@jehoshua.dialix.oz.au FEBC | WWW : http://www.febc.org ----------------------------------------------------------------- ------------------------------ Date: Thu, 8 May 1997 09:20:32 GMT-10 From: Peter Richards Subject: RMAIL on a network To: uupc-info@kew.com Hi, The setup here is a WIN for Workgroups LAN running Pegasus Mail and using UUPC software as the mail gateway. I can read/write the Pmail folders from either computer on the LAN, but only successfully use RMAIL on the (local) computer to spool mail. Have had several attempts at trying to get RMAIL to 'push' the spooled files across the network. Here is the log file: 05/07-14:27 RMAIL: UUPC/extended 1.12k (Dec 11 1994 12:33:55) (4) rmail argv[1] = "-x" (4) rmail argv[2] = "10" (4) rmail argv[3] = "-t" (4) rmail argv[4] = "-f" (4) rmail argv[5] = "c:\tmp\95D7EDA0.pm" (5) inithost: Allocated room for 32 host entries (2) Run time library error in d:\src\uupc\lib\hostable.c at line 486 ... (0) C:/PMAIL/systems: No such file or directory (1) Extended DOS Error Information: Number = 2, Class = 8, Action = 3, Locus = 4 (0) RMAIL aborting at line 487 in file d:\src\uupc\lib\hostable.c I was running RMAIL from c:\pmail directory; does the 'no such file' require the 'systems' file to be in the same directory ? (It is on the computer I am trying to send spooled mail to). Peter ----------------------------------------------------------------- ( (|) ) | Peter & Kathy Richards | | Jehoshua Computing /^\ | 16 Perry Avenue Phone: (047) 517220 Christ to | Springwood NSW 2777 Fax: (047) 517220 the World | Australia By Radio | Email: Peter@jehoshua.dialix.oz.au FEBC | WWW : http://www.febc.org ----------------------------------------------------------------- ------------------------------ Date: Wed, 07 May 1997 22:50:37 -0500 From: "Drew Derbyshire - UUPC/Extended Support" Subject: RMAIL on a network To: "Peter Richards" On Thu, 8 May 1997 09:20:32 GMT-10, "Peter Richards" wrote: > Hi, > > The setup here is a WIN for Workgroups LAN running Pegasus Mail and > using UUPC software as the mail gateway. I can read/write the Pmail > folders from either computer on the LAN, but only successfully use > RMAIL on the (local) computer to spool mail. Have had several attempts at > trying to get RMAIL to 'push' the spooled files across the network. Here > is the log file: > > 05/07-14:27 RMAIL: UUPC/extended 1.12k (Dec 11 1994 12:33:55) > (4) rmail argv[1] = "-x" > (4) rmail argv[2] = "10" > (4) rmail argv[3] = "-t" > (4) rmail argv[4] = "-f" > (4) rmail argv[5] = "c:\tmp\95D7EDA0.pm" > (5) inithost: Allocated room for 32 host entries > (2) Run time library error in d:\src\uupc\lib\hostable.c at line 486 ... > (0) C:/PMAIL/systems: No such file or directory > (1) Extended DOS Error Information: Number = 2, Class = 8, Action = 3, > Locus = 4 > (0) RMAIL aborting at line 487 in file d:\src\uupc\lib\hostable.c > > I was running RMAIL from c:\pmail directory; does the 'no such file' > require the 'systems' file to be in the same directory ? (It is on the > computer I am trying to send spooled mail to). I do not have knowledge of the PMAIL directory. Have you made it work with a native UUPC/extended configuration first? (I.e. gotton the MAIL program to run?) In general, UUPC/extended's configuration files all must be excessible to the various programs, especially HOSTPATH, SYSTEMS, and PASSWD for RMAIL. -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 VM programmers do it virtually all the time. ------------------------------ Date: Sun, 11 May 1997 15:36:59 -0500 From: "Drew Derbyshire - UUPC/Extended Support" Subject: SMTP support in UUPC/extended To: uupc-info@kew.com By beginning with code generously contributed by Jacques Rebiscoul of S.S.T.I., the next release of UUPC/extended will include at least one half of SMTP support. The code now added to rmail uses the existing TCP/IP support written by David Watt and the standard RMAIL delivery logic combined with the code from Jacques and various new support to glue it all together. The highlights: 1) The host path file can now include entries of the form: host @ smtp.gateway *.host @ smtp.gateway This will route all mail for the host or domain to the specified gateway via SMTP. The specified host can be the mail server, which to say all outbound mail can be redirected to the gateway. 2) By default, mail is only queued by RMAIL if running in -w or -t mode (new mail being queued from a Mail front-end); such queuing is performed under the local host name (the same queue used for local news processing), one (or more as required) per SMTP gateway host used. 3) When running in -t mode, RMAIL can be requested to be deliver immediately by setting the new boolean option 'fastsmtp'. Mail in daemon mode (-w) cannot be forced for immediate delivery, to prevent endless recursion. 4) Mail locally queued for SMTP delivery will be processed by UUXQT and RMAIL normally, and RMAIL will automatically be passed the new -q option on the command line to flag it should be processed in SMTP mode. When running in this mode, failure to connect to the remote host will result in a the new RMAIL exit status of 75, which will cause UUXQT to gracefully leave the spooled mail in untouched for later processing. 5) When running in -q mode, RMAIL will deliver ALL queued mail on the command line to the same SMTP host as determined by the first addressee's routing. (This is consistent with the queuing performed described above.) 5) If the hostpath file is changed after the mail has been queued but before the mail is actually delivered via SMTP, and the first addressee is no longer delivered via SMTP as defined by the hostpath file, the mail will automatically be delivered via normal RMAIL routing. 6) This full support is included for 32 bit OS/2 and 32 bit Windows only. No DOS or 16 bit Windows SMTP delivery will be provided. The standard distributed Windows 3.1 package normally does not include RMAIL or UUXQT, and we include NO TCP/IP support at all with the DOS versions. 7) The 16 bit environments which do not support SMTP delivery still understand the new hostpath syntax and SMTP local queuing; this means that 16 bit environments (DOS, OS/2 and Windows) can share a hostpath and a spool directory with the SMTP enabled 32 bit environments, which will deliver the mail on the behalf of the 16 bit environments. 8) The SMTP support is designed for connecting to one or more friendly local gateways which can handle general delivery; it is not designed for general Internet use, having no MX (host lookup) support, only a single timeout period for all network reads, and no anti-SPAM protection. 9) No SMTP server currently exists for receiving mail; this facility only supports sending mail. We expect to release the support, along with various bug fixes and other more limited enhancements, by the end of May 1997. A limited number of beta testers will be accepted immediately. Bribes in the form of new registrations will be welcomed to encourage the production of the receiving side of the gateway. -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 "Who knows what evil lurks in the hearts of men? The Shadow . . ." ------------------------------ Date: Sat, 26 Apr 97 12:40:44 -0400 From: Gary A Zaidenweber Subject: tcpip issues To: Software@kew.com (Drew Derbyshire - UUPC/Extended Support) Drew Derbyshire - UUPC/Extended Support writes: > > On Wed, 28 Aug 1996 08:42:48 -0400, "Curtis Maurand" wrote: > > The problem is that the person handling the mail for us has his UUCP > > configured not to listen on port 117 (tcpip defines this port as the > > uucp-path in the services file) I am assuming that UUPC is trying to > > connect on that port. The provider is trying to do this on the telnet > > port. Is there any way of changing the port by which UUPC connects to the > > host on? > > No, you use port 540, and run uucpd ojn the remote side. This is a > standard daemon for FreeBSD, I don't know about Linux. Taylor UUCP 1.06.1 is part of the Networking [N] package of the Slackware Distribution of Linux. Very detailed configuration and administration istructions (as well as some comforting words :) can be found in the Linux Network Administrator's Guide under the Linux Documentation Project: < http://sunsite.unc.edu//LDP/LDP/nag/nag.html >. -- Gary == gaz@spokes.boston.ma.us http://www.channel1.com/~spokes/ -- Gary == gaz@spokes.boston.ma.us http://www.channel1.com/~spokes/ -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 Cannot find REALITY.SYS. Universe halted. ------------------------------ Date: Sun, 27 Apr 1997 12:53:35 -0500 From: "Drew Derbyshire - UUPC/Extended Support" Subject: UNIX sendmail testers To: "UUPC Mailing List" I need a UNIX tester or two. I've taken the sendmail 8.8.5 RMAIL module and modified it to properly parse UUCP From lines which include a domain name; this corrects the otherwise bogus sendmail behavior of presenting an address received via UUCP uucp.domain.com!user routed via tcpip.host.com as uucp.domain.com!user@tcpip.host.com when it shoud just be converted to user@uucp.domain.com. The file is in ftp://ftp.kew.com/pub/unix/rmail.c. -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 "You say that I'm the boy who can make it all come true Well I'm tellin ya that I don't know, I don't know what to do . . ." ------------------------------ Date: Sat, 26 Apr 1997 16:08:06 +0200 From: Mark Jonckheere Subject: uucico aborting at line 590 To: Drew Derbyshire - UUPC/Extended Support Drew Derbyshire - UUPC/Extended Support wrote: > > On Tue, 13 Aug 1996 00:04:21 +0000, "Mark Jonckheere" wrote: > > I have a problem using uupc 1.12p on windows 3.11 over a tcp/ip > > connection. When I give two uucp commands on my UNIX machine to send a > > file to my pc, it will start two uucico processes at the same time. The > > first one transmits the two files, the second one fails and does a number > > of retries. At the same time on the pc uupoll restarts uucico after > > running uuxqt. This second uucico aborts at line 590 because > > "tpassiveopen: bind(pollingSock)failed", "bind: (10048) Address already > > in use". > > I corrected this problem several months ago and sent a solution in a mail with subject: "keeping uupoll and uucico up and running in a win 3.x environment" I include here the suggested modifications: > 3. in passive mode, a second incoming tcp/ip connection is not > accepted, but keeps the address in use long enough to provoke > an "address in use error" the next time uucico restarts and > calls the bind function. This gives the error message: > "error at line 590 in modem.c". I added a setsocketoption > REUSEADDRESS to the code. > I suppose that the 'bind' at line 113 in pwinsock.c must be 'pbind'. > > $ diff old/lib/ulibip.c new/lib/ulibip.c > 422a423 > > int sockopt = 1; > 492a494,504 > > printmsg(15, "tpassiveopen: doing setsockopt()"); > > if (setsockopt( pollingSock, SOL_SOCKET, SO_REUSEADDR, > > (char FAR *) &sockopt, sizeof(int)) == SOCKET_ERROR) > > { > > int wsErr = WSAGetLastError(); > > > > printmsg(0, "tpassiveopen: setsockopt() failed"); > > printWSerror("setsockopt", wsErr); > > return KWTrue; > > } > $ diff old/lib/pwinsock.c new/lib/pwinsock.c > 113c113 > < int PASCAL FAR (*bind)(SOCKET s, > --- > > int PASCAL FAR (*pbind)(SOCKET s, > 144a145,150 > > int PASCAL FAR (*psetsockopt) (SOCKET s, > > int level, > > int optname, > > char FAR * optval, > > int optlen); > 199a206 > > psetsockopt = GetProcAddress(hWinsock, (LPSTR)MAKELONG( 21,0)); > $ diff old/lib/pwinsock.h new/lib/pwinsock.h > 75a76 > > #define setsockopt psetsockopt > 106a108,109 > > > > extern int PASCAL FAR (*psetsockopt) (SOCKET s, int level, int optname, char FAR * optval, int optlen); > Mark Jonckheere -- jonckheere@innet.be ------------------------------ Date: Fri, 02 May 1997 08:28:12 -0400 From: "Drew Derbyshire - UUPC/Extended Support" Subject: UUCP/SMTP Gateway To: serls@dashs.denver.co.us On Mon, 7 Apr 97 17:35:31 -0700, "Dave Serls" wrote: > Have you any documentation or sample .cf file for sendmail to UUPC? > I'm actually interested in an OS/2 platform, but I'll take anything! > Thanks for any help. No. We run sendmail and Talor UUCP on a FreeBSD box which also acts as a firewall and connect to our OS/2 server via UUCP over TCP/IP. So we just run the stock sendmail (with anti-spam filters, etc) on FreeBSD. -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 "I just program for Drew because Binkley Bunny (who is as snowy white as I am) and Gunther Bear used to help Drew program from the top of kendra's monitor. They went west in September [1990] with Mom so that Mom and Binkley could work on their PhDs. That made the Wonderworks understaffed, so at Christmas [1990] Mom asked me to live with Drew." - Snuffles P. Bear ------------------------------ Date: Fri, 2 May 1997 18:22:42 -0700 From: =?iso-8859-1?Q?Pedro_A=2E_Rodr=EDguez_Paz?= Subject: UUCP/SMTP Gateway To: "serls@dashs.denver.co.us" , I'm writing an UUCP Gateway for Microsoft Exchange Server, and I should be very grateful for suggestion about.. To meet people with certain grade of expertise writing Microsoft Exchange Server gateways is another purpose of this message. Thank in advance Peter peter@bioca.edu.cu ---------- From: Drew Derbyshire - UUPC/Extended Support[SMTP:Software@kew.com] Sent: Friday, May 02, 1997 5:28 AM To: serls@dashs.denver.co.us Cc: UUPC Mailing List Subject: Re: UUCP/SMTP Gateway On Mon, 7 Apr 97 17:35:31 -0700, "Dave Serls" wrote: > Have you any documentation or sample .cf file for sendmail to UUPC? > I'm actually interested in an OS/2 platform, but I'll take anything! > Thanks for any help. No. We run sendmail and Talor UUCP on a FreeBSD box which also acts as a firewall and connect to our OS/2 server via UUCP over TCP/IP. So we just run the stock sendmail (with anti-spam filters, etc) on FreeBSD. -ahd- -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 "I just program for Drew because Binkley Bunny (who is as snowy white as I am) and Gunther Bear used to help Drew program from the top of kendra's monitor. They went west in September [1990] with Mom so that Mom and Binkley could work on their PhDs. That made the Wonderworks understaffed, so at Christmas [1990] Mom asked me to live with Drew." - Snuffles P. Bear . ------------------------------ Date: Sun, 27 Apr 1997 14:03:29 -0400 From: "Drew Derbyshire - UUPC/Extended Support" Subject: UUPC/extended To: "Jeff Stillinger" On Wed, 17 Jul 1996 20:37:45 -0700, "Jeff Stillinger" wrote: > I was thinking that the newsgroup list was too long. > Messages that where not crossposted to every group worked fine. The > newsgroup listing was well over 256 char on the crossposted messages. > Do not worry, Waffle has the same problem with long newsgroup lists. We should handle ~ 512. I'm going to put checks in to blow off the overlong lines in 16 bit environments, since most overlength newgroup lines seem to be SPAM or generally clueless people in alt.* groups. I will offer a kill file. > Maybe while you are hacking away you can look at the maximum packet > size alotted for the 'g' protocol. 4096 seems to be the Taylor > standard. I would not mind being compatible. I don't think it matters over ~ 1024 with a good window size, and the smaller size improves recovery after errors and uses much less memory under 16 bit environments (8 * 2 4K is 64K, a fair chunk of memory for DOS). I keep it consistent between 16 and 32 bit versions because I have not seen the improvement when I have tried the larger number. -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9712 "You say that I'm the boy who can make it all come true Well I'm tellin ya that I don't know, I don't know what to do . . ." ------------------------------ Date: Wed, 08 May 1996 08:01:01 -0700 From: Datalink International Pakistan Subject: uupc cofiguring help To: uupc-info@kew.com Dear I download uupc file for dos and windows. i am using waffle in dos and windows 3.11 Worgroup. Pl help me in instalation as following. we recive/prepare mails in waffle and send thes mails by uupc to smtp server. pl help me Iftilhar Ahmad Faisalabad Pakistan ------------------------------ End of UUPC-Info-Request Digest ******************************