On 2017 Feb 12 14:27:42, you wrote to Jeff Smith:

 AP> @MSGID: 1:2320/101 58a0b761
 AP> @REPLY: 1:282/1031.0 5506e42a
 AP> @TID: SBBSecho 3.00-Win32 r3.28 Feb  7 2017 MSC 1800
 AP> @CHRS: CP437 2
 AP> @TZUTC: -0500

 AP>    Hello Jeff!

 AP> 12 Feb 17 00:24, you wrote to me:

 JS>> I had the same problem when I installed Golded+ on another Linux
 JS>> machine here. I simply told one to stop using an origin line. There
 JS>> usually a  config entry keyword that will en/disable the use of the
 JS>> origin line.

 AP> I think I figured it out in Synchronet.  I would rather leave the Golded
 AP> origins in first so if there's problems I can figure out if it's golded or
 AP> sync.

 AP> Allen


 AP> --- GoldED+/W32-MSVC 1.1.5-b20161221
 AP>  # Origin:  LiveWire - Synchronet Experiment (1:2320/101)
 AP>  * Origin: LiveWire BBS - Synchronet Test Node (1:2320/101)

welll... uummmm... i was pretty sure that sbbsecho had a way to not place the
origin line if there was one already in place on locally written posts... you
should ask DM about this in the synchronet echo... they've recently done work
on sbbsecho that someone else wrote years ago... this should be a simple check
to add...

local message?
  does it already have an origin line?
    no: add one
    yes: skip adding one


 AP>  AP> 124/5013
 AP> 5014
 AP>  AP>  AP> @PATH: 2320/101 100 123/500 3634/12



)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Every time my world gets interesting, they cut to commercial.
---
 * Origin:  (1:3634/12.73)