jr@taurus.UUCP (Jim R Oldroyd) (01/14/84)
Can someone help? I don't have time to trace this one myself, so I'd appreciate any leads. If I try to send mail (or more usually reply to a news message) and the address is long the uux of the mail to the first remote site fails. By "long" I mean addresses over about a line and a third (is that about 128 bytes??). There is no error message; at the time all looks ok. But later on I will find things like C.K?#xx!A0782 files in the /usr/spool/uucp dir. I do NOT have a site called K?#xx! or any of the other things I've seen there!!! Having just noticed that it seems to have something to do with 128, I'd have a wild guess and say that a buffer is overflowing. Does anyone know where? -- ++jim <england>!ukc!hirst1!taurus!jr ++jim
jr@taurus.UUCP (Jim R Oldroyd) (01/24/84)
This is the fix for the problem I outlined in a recent message whereby the uux of a message to a "long" address failed causing files like C.ha^#2@A0019 to be created in the SPOOL dir. Our version of uucp is that distributed by the EUUG with news 2.10, so watch out if you're in EUROPE, you may have the same problem. It's important that everyone fixes it, *particularly* HIRST1 and UKC, else my mail to distant sites *still* won't get through!! Ok, the problem's this: there is a buffer in uux.c declared as: char rest[MAXFULLNAME]; That's right, you guessed it: MAXFULLNAME is #defined as 100. So addresses over 100 chars don't work! Working out the fix for this requires a considerable amount of brainpower, so I save you the trouble by outlining it below: in file uucp.h, about line 67, change MAXFULLNAME to something more suitable: #define MAXFULLNAME 256 then recompile uux.c -- ++jim <england>!ukc!hirst1!taurus!jr ++jim
honey@down.UUCP (code 101) (01/26/84)
i don't want to give away any secrets here, but in honey danber we #define MAXFULLNAME BUFSIZ (sorry ma -- one little one won't hurt.) peter honeyman