When packetizing netmail, the "origin" address in the created packet header
was copied from the netmail (*.msg) message file. This is fine for locally
created netmail, but nof for forwarded netmail (!). This would end up creating
outbound packets with a foreign source/origin address which may or may not
be deliverable.

Sort of related, if there are stray packets in the outbound directory with a
foreign source/origin address - don't packetize them! Just log a msg and ignore
these foreign outbound packets.

This explains at least part of the problem Nelgin reported where a routed
netmail was delivered to him (on Vert) from a hop running SBBSecho v3.01 and
I saw this packet header oddity. Now, why the actual netmail message itself
had the wrong origin address has not been identified.

If your system routes netmail messages (e.g. your hub), you'll want his update!