[comp.archives] [comp.sources.misc] v15i098: pc-mail release 2 patch 3

wswietse@svbs01.bs.win.tue.nl (Wietse Venema) (01/17/91)

Archive-name: mail/uucp/pc-mail/1990-12-16
Archive-directory: ftp.win.tue.nl:/pub/pc-mail2/ [131.155.2.8]
Original-posting-by: wswietse@svbs01.bs.win.tue.nl (Wietse Venema)
Original-subject: v15i098: pc-mail release 2 patch 3
Reposted-by: emv@ox.com (Edward Vielmetti)

This is the third patch for the pc-mail release 2 package that appeared
in comp.sources.misc january 1990. 

Sources and earlier patches can be obtained via anonymous ftp from the
comp.sources.misc archives at uunet.uu.net, or from the author's
machine at ftp.win.tue.nl (internet address 131.155.2.8). The latter
host also has a directory tree with up-to-date MS-DOS binaries.

The following four problems are taken care of by this patch:

1 - Allow UUCP control messages (S, H, etc.) to span more than one packet.
    The problem would manifest itself as garbage appearing at the
    beginning of incoming e-mail messages, but only if the g protocol
    was being used. Thanks to Jim OBrien (JEO01@albnydh2.bitnet) for
    providing the information that led to the resolution of the problem.

2 - The sscanf(3) implementations with Microsoft C and Turbo C behave 
    different from the UNIX versions that I tested the programs with. 
    This caused the displayed numbers of (new, out, in or sent) messages 
    to be wrong. The program no longer uses sscanf(3) to parse file names. 

3 - Turbo C thrashes memory when it is freed. The program no longer
    tries to access members of data structures that have been freed.
    Thanks to Richard Brittain (richard@calvin.spp.cornell.edu) for
    pointing out the problem and its solution.

4 - After the protocol negotiation has completed, the program now allows 
    the remote host some time to change its tty mode settings. The problem 
    would sometimes result in the loss of the first packet sent by the PC, 
    and could cause 'g' protocol initialization failures. Thanks to Richard
    Brittain (richard@calvin.spp.cornell.edu) for reporting the problem.

[Patch deleted.  --Ed]