============================================
 * Original To  : Scott Dudley, 1:249/106.1
 * Original From: Paul Edwards, 3:711/934.9
 * Original Date: 1995-08-23 12:47
============================================

Scott, I thought I would raise the following bugs that I think
exist in Squish 1.11...

1. My boss, 3:711/809, who uses Squish 1.11 send me (3:711/934)
a packet with a destination address of 3:711/934.2 (instead of
the normal 3:711/934).  I do not know how the packet managed
to get addressed to 3:711/934.2.  In the packet was a single
message, which was indeed for 3:711/934.2.  I have not attempted
to reproduce the problem here, you just might want to bear it
in mind as a possibility.

2. Under some circumstances (which occur on say 2% of echomail
at an estimate), Squish is taking in a message with SEENBY and
PATH, and NO extraneous  and then adding an extraneous .
Normally (98%) Squish does not add any extraneous CRs.  The
extraneous  is put into the outgoing packets.

3. The remap commands are documented as readdressing mail that
has been sent to your Address.  It is actually remapping stuff
that is addressed to points off that address to, instead of
just the base address.  So e.g. if someone sends mail to "Fred"
at 3:711/934.13, and I have a "Remap Fred 3:711/934.9" then it
will remap this message, even though the message is destined
for 3:711/934.13 and NOT 3:711/934.

4. When mail is exported to a point that is not on this system,
their node gets added to the SEENBY when I don't think it should.
E.g. at 3:711/934 I send echomail to 3:640/305.9, and "640/305"
goes into the SEENBY.  The meaning of "640/305" in the SEENBY
line is that 640/305 has seen the message.  Since this is
clearly not the case, I do not think this behaviour is correct.

I would appreciate it if you could tell me which, if any of
these bugs you:

1. Have fixed.
2. Plan on fixing.
3. Can reproduce.
4. Know about already.
5. Do not consider to be a bug.

BFN.  Paul.
@EOT:

---