Hello everybody!

Anyone know how to stop the double origin lines with Golded and Synchronet (See
Below if it does it again).

Allen


=== GoldED+/W32-MSVC 1.1.5-b20161221
# Origin: LiveWire - Synchronet Experiment (1:2320/101)
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet Test Node (1:2320/101)

Hi Allen!

11 Feb 2017 11:25, from Allen Prunty -> All:

Anyone know how to stop the double origin lines with Golded and
Synchronet (See Below if it does it again).

Well if you write the post in golded it adds the origin, as it is supposed to do.
The tosser AFAIK is not allowed to add another origin if one exists already.
So the way to go is to disable the adding of additional origin lines by the tosser you use (or change your tosser altogether).

Alternatively you can disable the generation of tearlines and origin in golded: CTRLINFOECHO NO

CU, Ricsi

--- GoldED+/LNX
* Origin: Too bad stupidity isn't painful (2:310/31)

* An ongoing debate between Allen Prunty and All rages on ...

Anyone know how to stop the double origin lines with Golded and
Synchronet (See Below if it does it again).

Add CTRLINFO NO to the Echo Group option. May also need CTRLINFOECHO NO ...


.- Keep the faith, --------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| Home page: http://cmech.dynip.com/homepage/ | `----------- WildCat! Board 24/7 +1-337-984-4794 any BAUD 8,N,1 ---'

... Cross-posted from alt.swedish.chef.bork.bork.bork.
--- GoldED+/W32-MSVC v1.1.5-b20161221 ... via Mystic BBS!
* Origin: FIDONet - The Positronium Repository (1:393/68)

On 2017 Feb 11 11:25:52, you wrote to All:

Anyone know how to stop the double origin lines with Golded and Synchronet (See Below if it does it again).

yeah, tell one of them to not add them ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Yes, I am an agent of Satan, but my duties are largely ceremonial.
---
* Origin: (1:3634/12.73)

Re: Double Origin Lines
By: Allen Prunty to All on Sat Feb 11 2017 11:25:53

Anyone know how to stop the double origin lines with Golded and Synchronet (See
Below if it does it again).

Allen

It did it again, and apparently you can turn it off in either Synchronet, or Golded.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Hello Ben!

Replying to a msg dated 11 Feb 17 11:07, from you to me.

Thanks Ben... I went ahead and disabled both to see what happens. Hopefully SBBSECHO will insert the proper MSGID and REPLYTO

Allen


--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet Test Node (1:2320/101)

Hello Allen,

Anyone know how to stop the double origin lines with Golded and Synchronet
Below if it does it again).

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


Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: The OuijaBoard - Anoka, MN (1:282/1031)

Hello Allen!

11 Feb 17, Allen Prunty wrote to All:

Anyone know how to stop the double origin lines with Golded and
Synchronet (See Below if it does it again).

There are no double origin lines. There is only one.

=== GoldED+/W32-MSVC 1.1.5-b20161221
# Origin: LiveWire - Synchronet Experiment (1:2320/101)
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet Test Node (1:2320/101)

The line beginning with " * Origin:" is the origin line. The one beginning with
" # Origin:" is no origin line. Same for the tagline "--- ".

As golded works correct with origin lines by default you better fix that SBBS software. Modification of origin lines was XAB once and is still annoying.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/1351.7)

On 2017 Feb 11 21:18:56, you wrote to Ben Ritchey:

@MSGID: 1:2320/101 589fc62d
@REPLY: 1:393/68 589f4533
@PID: GED+W32 1.1.5-b20161221
@TID: SBBSecho 3.00-Win32 r3.28 Feb 7 2017 MSC 1800
@CHRS: CP437 2
@TZUTC: -0500
Hello Ben!

Replying to a msg dated 11 Feb 17 11:07, from you to me.

Thanks Ben... I went ahead and disabled both to see what happens.

this is just fine...

Hopefully SBBSECHO will insert the proper MSGID and REPLYTO

that's not sbbsecho's job if they're already there as golded properly does...

Allen

--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet Test Node (1:2320/101)
SEEN-BY: 16/101 18/200 34/999 90/1 116/18 123/140 500 128/187 140/1

218/700

SEEN-BY: 222/2 230/150 240/1120 249/303 250/1 261/38 100 266/404 267/155 SEEN-BY: 280/1027 282/1031 1056 292/907 908 320/119 219 340/400 393/68 SEEN-BY: 396/45 712/848 801/161 189 2320/100 3634/12 15 22 24 27 50
@PATH: 2320/101 100 203/0 230/150 261/38 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...
... We Americans are a simple people but piss us off & we'll bomb you.
---
* Origin: (1:3634/12.73)

On 2017 Feb 11 20:20:18, you wrote to Allen Prunty:

=== GoldED+/W32-MSVC 1.1.5-b20161221
# Origin: LiveWire - Synchronet Experiment (1:2320/101)
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet Test Node (1:2320/101)

The line beginning with " * Origin:" is the origin line. The one beginning with " # Origin:" is no origin line. Same for the tagline "--- ".

the first one with the '#' has been properly negated specifically by changing the '*' to a '#'... the tear line, not tag line, has also been negated but needn't have been... tear lines are not required by the specification...

As golded works correct with origin lines by default you better fix
that SBBS software. Modification of origin lines was XAB once and is
still annoying.

sbbsecho works properly and also has config options to disable its insertion of
origin and tear lines... the operator just needs to choose one of the three options available between the two packages... sbbsecho's negating is properly done and is not a violation of any FTN specs...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Go the extra mile. It's never crowded.
---
* Origin: (1:3634/12.73)

Hello Jeff!

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

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

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

Allen


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

Hi Allen!

12 Feb 2017 14:27, from Allen Prunty -> Jeff Smith:

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

# Origin: LiveWire - Synchronet Experiment (1:2320/101)
+ Origin: LiveWire BBS - Synchronet Test Node (1:2320/101)

Your 2 origins are different.
If I had to guess "Synchronet Experiment" is golded, and "Synchronet Test Node"
is from your tosser.

CU, Ricsi

--- GoldED+/LNX
* Origin: Real programmers can't read code while wearing a tie (2:310/31)

Hello Allen,

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

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

That's what I did too. I let Golded take care of the Origin line.

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

Jeff



--- BBBS/Li6 v4.10 Toy-3
* Origin: The OuijaBoard - Anoka, MN (1:282/1031)

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

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

Hello Jeff!

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

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

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

Allen

--- GoldED+/W32-MSVC 1.1.5-b20161221
# Origin: LiveWire - Synchronet Experiment (1:2320/101)
* 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

SEEN-BY: 109/500 116/116 120/544 123/5 52 111 400 500 789 1970
124/5013
5014
SEEN-BY: 135/300 140/1 154/10 203/0 226/600 229/426 261/38 280/464 320/119 SEEN-BY: 322/759 342/11 2320/100 101 3634/12 15 22 24 27 50
@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)

Hello mark!

12 Feb 17, mark lewis wrote to Kai Richter:

As golded works correct with origin lines by default you better
fix that SBBS software. Modification of origin lines was XAB once
and is still annoying.

sbbsecho works properly

Then why the original poster is asking how to fix it?

Why there are answers how to fix it?

Replacement of existing origin lines is NOT properly. There is one real origin line only: The first one of the original writer.

sbbsecho's negating is properly done and is not a violation of any FTN specs...

It is common practice that mailcontent including the original origin line is transported unmodified within Fidonet as long as i can remember.

Other FTNs may have other requirements.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/1351.7)

On 2017 Feb 12 23:40:08, you wrote to me:

As golded works correct with origin lines by default you better fix
that SBBS software. Modification of origin lines was XAB once and is
still annoying.

sbbsecho works properly

Then why the original poster is asking how to fix it?

he wasn't asking how to fix golded or sbbsecho... he was asking how to fix the double tear and origin lines...

Why there are answers how to fix it?

there are no answers to fixing golded and sbbsecho... there are pointers to configuration options... different things...

Replacement of existing origin lines is NOT properly. There is one
real origin line only: The first one of the original writer.

incorrect... the last origin line is the valid one... are you not aware of how proper FTN<->FTN gating is done? they use the same as is documented...

sbbsecho's negating is properly done and is not a violation of any
FTN specs...

It is common practice that mailcontent including the original origin
line is transported unmodified within Fidonet as long as i can
remember.

it is transported unmodified... it originates on that system and is packed with
two tear and origin lines... nothing has changed that along the path...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Deer hunters will do anything for a buck.
---
* Origin: (1:3634/12.73)

Hello mark!

13 Feb 17, mark lewis wrote to Kai Richter:

sbbsecho works properly

Then why the original poster is asking how to fix it?

he wasn't asking how to fix golded or sbbsecho... he was asking how to
fix the double tear and origin lines...

...with golded and synchronet. I recived his mail too, that's why you can't trump me with "alternate facts".

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Cheap, Fast, Reliable - pick any two. (2:240/1351.7)

On 2017 Feb 14 08:14:40, you wrote to me:

sbbsecho works properly

Then why the original poster is asking how to fix it?

he wasn't asking how to fix golded or sbbsecho... he was asking how
to fix the double tear and origin lines...

...with golded and synchronet. I recived his mail too, that's why you can't trump me with "alternate facts".

don't insult me like that ever again... it is/was a configuration problem, not a software code problem as your statement indicated... your brush was too broad
and the wrong color... i pointed that out and now you are the one dumping crap like that? piss off...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Another addition to the Museum of the Kitchen of Gadgets.
---
* Origin: (1:3634/12.73)

Hello mark!

14 Feb 17, mark lewis wrote to Kai Richter:

sbbsecho works properly

Then why the original poster is asking how to fix it?

he wasn't asking how to fix golded or sbbsecho... he was asking
how to fix the double tear and origin lines...

...with golded and synchronet. I recived his mail too, that's why
you can't trump me with "alternate facts".

don't insult me like that ever again... it is/was a configuration
problem, not a software code problem as your statement indicated...
your brush was too broad and the wrong color... i pointed that out and
now you are the one dumping crap like that? piss off...

Calm down, review your arguments and you will understand why your point of view
deserves such a comment.

If you understand "fix a problem" by hunting bugs in software code, then you know now why you didn't understand. For my point of view a solution for a problem with the configuration is a fix too.

Or in other words: A misconfigured software does not work properly.
(even it's called sbbsecho, or whatever...)

You can draw even if you find out what the default behavior of sbbs is.
If sbbs does not touch an existing origin line by default, then i agree that sbbs does work properly. In that case the sysop was responsible for the misconfiguation.
If sbbs does replace the origin line by default, i still call it a bug, even if
the code works as designed. Modification of the origin line without explicit configured by the sysop is a design bug in my point of view.

In any case, it was a not properly working system with golded and sbbs, which is fixed now.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Flying an airwave calypso (2:240/1351.7)

Hello mark,

Replacement of existing origin lines is NOT properly. There is one
real origin line only: The first one of the original writer.

incorrect... the last origin line is the valid one... are you not aware
of how proper FTN<->FTN gating is done? they use the same as is documented...

That may be, but read on...

sbbsecho's negating is properly done and is not a violation of any
FTN specs...

It is common practice that mailcontent including the original origin
line is transported unmodified within Fidonet as long as i can
remember.

it is transported unmodified...

No it is transported and changed, at the local machine between the software packages.

it originates on that system and is packed with two tear and origin lines... nothing has changed that along the path...

incorrect...
the second program (i.e. tosser) changed the message generated by the first program (i.e. GolEd), so that's xab, nothing less.
It also changed the original tearline and original origin line,
by changing the first characters on those lines.
So it is still incorrect behavior despite of config settings.

Henri.

---
* Origin: Connectivity is the Future; UniCorn BBS 31 26 4425506 (2:280/1208)

Hello mark,

--- GoldED+/W32-MSVC 1.1.5-b20161221
# Origin: LiveWire - Synchronet Experiment (1:2320/101)
* 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...

Right sugestion.

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

I think it is more logical to change the no and yes functions in a differend order, so:

local message?
does it alreay have an origin line?
Yes: skip adding one
No: add one
end of routine.

Than it should not be hardcoded to allways add a new origin line
if the config wants to, and never change an already one there.

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer
doin' it wrong...

Writing this in every msg from you for many months can be considered as spam!

Henri.

---
* Origin: Connectivity is the Future; UniCorn BBS 31 26 4425506 (2:280/1208)

On 2017 Feb 14 19:31:00, you wrote to me:

It is common practice that mailcontent including the original origin
line is transported unmodified within Fidonet as long as i can
remember.

it is transported unmodified...

No it is transported and changed, at the local machine between the software packages.

no... it is not ""transported""... it sits in a message base with the golded origin line on it and the tosser scans it out and adds another one instead of using intelligence and detecting there is one already in place...

perhaps you should actually install the software in question and see how it really operates instead of making wild assumptions like so many others...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... A lawyer got his client a suspended sentence. He was hung.
---
* Origin: (1:3634/12.73)

On 2017 Feb 14 19:30:00, you wrote to me:

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer
doin' it wrong...

Writing this in every msg from you for many months can be considered as spam!

no it cannot... besides that, though shit... sue me... or better yet, just skip
my posts...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... All extremists should be shot.
---
* Origin: (1:3634/12.73)

Hello mark!

15 Feb 17, mark lewis wrote to Henri Derksen:

It is common practice that mailcontent including the original
origin line is transported unmodified within Fidonet as long as
i can remember.

it is transported unmodified...

No it is transported and changed, at the local machine between
the software packages.

no... it is not ""transported""... it sits in a message base with the golded origin line on it and the tosser scans it out and adds another
one instead of using intelligence and detecting there is one already
in place...

perhaps you should actually install the software in question and see
how it really operates instead of making wild assumptions like so many others...

No need for me, because i rely on your statement above. You contradicted your own statement "not transported" in the same sentance. The process of the outgoing mail from the saved unsend message to other systems is mail transportation. It includes tosser, mailer and maybe trackers that are used in the transportation process.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/1351.7)

Hello Mark,

It is common practice that mailcontent including the original origin
line is transported unmodified within Fidonet as long as i can
remember.

it is transported unmodified...

No it is transported and changed, at the local machine between the
software packages.

no... it is not ""transported""... it sits in a message base with the golded origin line on it and the tosser scans it out and adds another one instead of using intelligence and detecting there is one already in

place...

Off course it was not intelligent.
Scanning it out and placing it in a pkt _IS_ transportation, nothing less.
The original message sits unchangand in the local database,
but the tranported one to the *.pkt file was changed illegally.
That is what I mean transportation on the local machine,
even before it was sended out tot the rest ot the network.
Copying from one file tot another even in the same directory is
transportation!
Even moving, i.e. deleting original after copying, is transportation.

perhaps you should actually install the software in question and see how
it really operates instead of making wild assumptions like so many others...

That was not a wild assumption, you know very well.
Installing software is not necessarry when you use your imagination.
Besides that, I donot have the resources to spend so much time for so much sillynes. No thanks, I have more important things to do.
Kai was right and still is, period.

Henri.

---
* Origin: Connectivity is the Future; UniCorn BBS 31 26 4425506 (2:280/1208)

On 2017 Feb 16 04:11:48, you wrote to me:

perhaps you should actually install the software in question and see
how it really operates instead of making wild assumptions like so
many others...

No need for me, because i rely on your statement above. You
contradicted your own statement "not transported" in the same
sentance.

no i did not...

The process of the outgoing mail from the saved unsend message to
other systems is mail transportation.

no it is not... it is packaging... shipping comes later...

It includes tosser, mailer and maybe trackers that are used in the transportation process.

nope... the tosser is the packager... netmail trackers are quality control... mailers are shipping... shipping is transportation...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Some people find fault like there is a reward offered.
---
* Origin: (1:3634/12.73)

Hello mark!

19 Feb 17, mark lewis wrote to Kai Richter:

No need for me, because i rely on your statement above. You
contradicted your own statement "not transported" in the same
sentance.

no i did not...

You are still walking the presidential way...

The process of the outgoing mail from the saved unsend message to
other systems is mail transportation.

no it is not... it is packaging... shipping comes later...

Maybe our understanding is lost in translation.

Wikipedia refers to https://en.wikipedia.org/wiki/Parcel_%28package%29

"A parcel is a package bearing the name and address of the recipient
in order to be routed through the services of a postal service"

https://en.wikipedia.org/wiki/Packaging_and_labeling

"Packaging is the technology of enclosing or protecting products for distribution"

The term package is bond to the transportation process, it is done for routing and distribution.

https://en.wikipedia.org/wiki/Network_packet

"A network packet is a formatted unit of data carried by a
packet-switched network"

"Carried by" is transportation and you need a packet for it.

It includes tosser, mailer and maybe trackers that are used in
the transportation process.

nope... the tosser is the packager... netmail trackers are quality control... mailers are shipping... shipping is transportation...

Let's drop the tracker for better understanding.

The tosser has functions for routing control and i don't select a destination if i don't want to transport. The mailer can't ship if the tosser did not set the destination. Tossing must be part of the transportation or the mailer would
never know it's destination and don't know where to transport to.

(There may be mailers that can read *.msg and send them directly as an *.out pkt, but then packaging is transportation with your type of logic because it'ss
done with the mailer.)

The packager does packaging for the purpose of transportation only.

Putting a letter into an envelope or an object into a package is the start of transportation for ages.

The written mail in the messagebase is the letter, the tosser package is the envelope. The rule is to deliver the letter unchanged. Transportation or not, modification of the letter is xab.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Ride the sky! (2:240/1351.7)

Hello mark,

No need for me, because i rely on your statement above. You
contradicted your own statement "not transported" in the same
sentance.

no i did not...

Ofcourse you did, and I will prove it.

The process of the outgoing mail from the saved unsend message to
other systems is mail transportation.

no it is not... it is packaging... shipping comes later...

packaging is also TRANSPORTATION, we did not spoke about shipping.
The message is copied from the stock into the packroom (i.e. other directory) and than changed during that process, i.e. adding a unecessarry origin tot it, and mangling the original Origin.
Copying is transportation and allowed, modifying not.

It includes tosser, mailer and maybe trackers that are used in the transportation process.

nope... the tosser is the packager... netmail trackers are quality control... mailers are shipping... shipping is transportation...

packaging is also tranportation on the same (local) machine, period.
Local transportation has alto to be in line of the FidoNet rules.

Also copying from a local harddisc to a floppy for a modemless point is still transportaion, not only bij POTS modem or internet as you may think.

Henri.

---
* Origin: Connectivity is the Future; UniCorn BBS 31 26 4425506 (2:280/1208)

On 2017 Feb 22 02:48:34, you wrote to me:

The process of the outgoing mail from the saved unsend message to
other systems is mail transportation.

no it is not... it is packaging... shipping comes later...

Maybe our understanding is lost in translation.

apparently... so i'm ending it here... the process is simple... you and henri are being too analytical or are combining details... i'm not going to discuss it any further... EOT

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... It's good to be children sometimes and never better than at Christmas.
---
* Origin: (1:3634/12.73)

Calm down, review your arguments and you will understand why your
point of view deserves such a comment.

Kai,

I've been a bit sick and haven't followed many of my echos. But I
have to say in the South we have an old mountain proverb. "Don't dip
out of the punch bowl until you know what's in it."

Mark was right it was something that -I- turned on in SBBS echo
thinking it was something that needed turning on. So it had nothing
to do with Golded, although not knowing where to look he pointed me in
the right direction.

I've not always agreed with mark on some things, but I can say that
I've always respected his knowledge. I've known him from way back in
the day. I beta tested RemoteAccess from version .003 or some
rediculously old version. I've known him off and on for almost 30
years and he has always been helpful and he knows his stuff. In fact,
he can probably help configure any mailer, any tosser and any BBS
software.

If he says I have SBBSECHO not configured right and it's effecting
Golded I almost assuredly can take it to the bank that I have an issue
with SBBSECHO.

You sir, seem to be here to cause trouble. Even if I wasn't able to
fix it your indictments on marc would not have helped. Remember we
are all here to help one another. Share your knowledge... and respect
those who are trying to share. Mr. mark is someone who won't scare
off easy, but you may scare off someone from sharing their knowlege
for fear of getting sniped. Nothing against you Kai, but think about
it.

Allen
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Allen!

I did read your mail carefully and i will answer it via netmail.

But one for the public please:

03 Mar 17, Allen Prunty wrote to Kai Richter:

If he says I have SBBSECHO not configured right and it's effecting
Golded I almost assuredly can take it to the bank that I have an issue with SBBSECHO.

It was _ME_ who said that on 11 Feb!

MSGID: 2:240/1351.7 589f64ac

+++ cut on +++
As golded works correct with origin lines by default you better fix that SBBS software. Modification of origin lines was XAB once and is still annoying.
+++ cut off +++

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/1351.7)