Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!comp.vuw.ac.nz!jwright From: Julian.Wright@comp.vuw.ac.nz (Julian Wright) Newsgroups: comp.sys.acorn Subject: Re: Archimedes RUCP. Message-ID: <1991Jun03.231216.3204@comp.vuw.ac.nz> Date: 3 Jun 91 23:12:16 GMT References: Sender: news@comp.vuw.ac.nz (News Admin) Organization: Not to speak of... Lines: 35 Nntp-Posting-Host: halswell.comp.vuw.ac.nz Originator: jwright@halswell.comp.vuw.ac.nz In article , kelvin@thed (Kelvin Hill) writes: |> Newsgroups: comp.sys.acorn |> Subject: Re: Archimedes RUCP. |> Message-ID: |> From: kelvin@thed (Kelvin Hill) |> Date: 3 Jun 91 13:44:37 GMT |> Sender: @mips2.ma30.bull.com ^^^^^^^^ ????!!!! |> References: |> Organization: Bull HN Informations Systems Inc. |> Lines: 10 |> |> I have used the RUCP 0.11 distribution to a Unix systemm with no problems. |> I've also used Waffle 1.64 to the same Unix node, again with no problems. Check your Sender: field - there is a manifestation of the bug here too! It is most likely that some mailers WILL handle multiple spaces between field names and their parameters in the header, so it is not surprising that RUCP<->Unix UUCP works fine. But I'll bet the Unix UUCP end doesn't tabulate it's header fields... that's why Waffle will work with it as well. I have 'fixed' my copy of mail by changing two format strings in the executable at about address &B400 (unsqueezed (manually) of course!) from "%-10s %s" to "%s %s" and terminating with \0 as usual. Now mail no longer tabulates the header and I have no problems. But I would rather it was Waffle that was fixed... a tabulated header looks so much neater... Cheers, Julian. -- ;`````````````````````````````````````````````````````````````````````````````; ; I would if I could but I can't so I won't but I might if I find I can later ; ;,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,; jwright@comp.vuw.ac.nz|julian@sideways.welly.gen.nz|julian@bridge.welly.gen.nz