Hello All...

My apologies over the recent issue with dumping messages in the FTSC_Public area. It was not my intention nor done maliciously. There was a bug introduced in the tosser software that has already been rectified.

Again, my apologies..

--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: 6697
Radio: radio.tequilamockingbirdonline.net:8010/live
--- SBBSecho 3.02-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Hello Bill,

07 Nov 17 19:53 at you wrote to All:

Again, my apologies..

Castigation is the Fidonet way.

Later,
Sean

... It is morally wrong to allow suckers to keep their money.
--- GoldED+/LNX 1.1.5-b20170303
* Origin: Outpost BBS * Limestone, TN, USA (1:18/200)

On 11/07/17, Bill McGarrity pondered and said...

Again, my apologies..

It's all good here Bill :) you're doing fine... take care. Best, P.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

Hey Sean!

Castigation is the Fidonet way.

No it isn't. You should be banned from posting in this echo and have your nodenumber revoked for even suggesting such a thing. Tsk, tsk.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.4.12(1)-release (x86_64-silvermont-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hello Bill.

07 Nov 17 19:53, you wrote to all:

Hello All...

My apologies over the recent issue with dumping messages in the FTSC_Public area. It was not my intention nor done maliciously.
There was a bug introduced in the tosser software that has already
been rectified.

Again, my apologies..

That's fine. Any chances that this might have affected other Synchronet
systems?

Flavio

... "Get out of my way, @N@-R! N└o funcionou Reptile." - Mel
--- MacFidoIP 1.0 (OSX)
* Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)

Hello Bill!

07 Nov 17 19:53, you wrote to all:

There was a bug introduced in the tosser software that has already
been rectified.

The lesson of the month: Never put untested software into production, at least unattended. :)

'Tommi

---
* Origin: [f360.n221.z2.fidonet.fi] (2:221/360)

On 2017 Nov 08 16:38:40, you wrote to Bill McGarrity:

There was a bug introduced in the tosser software that has already
been rectified.

The lesson of the month: Never put untested software into production,
at least unattended. :)

lesson zero: always clear the outbound and turn off the mailer when working with (new/alpha/beta) tosser software on established systems... when finished testing the tosser software, check and clear the outbound again before turning the mailer back on... taking these steps ensures that erroneously scanned out mail is not regurgitated into the rest of the network... highwater marks are not all managed the same way in all software... even in the same message base...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... You send 'em to school...they eat the books.
---
* Origin: (1:3634/12.73)

Sean Dennis wrote to Bill McGarrity on 11-08-17 00:58 <=-

07 Nov 17 19:53 at you wrote to All:

Again, my apologies..

Castigation is the Fidonet way.

Just a political necessity... ;)


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Paul Hayton wrote to Bill McGarrity on 11-08-17 19:57 <=-

On 11/07/17, Bill McGarrity pondered and said...

Again, my apologies..

It's all good here Bill :) you're doing fine... take care. Best, P.

Thank you sir!!


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Flavio Bessa wrote to Bill McGarrity on 11-08-17 09:13 <=-

07 Nov 17 19:53, you wrote to all:

Hello All...

My apologies over the recent issue with dumping messages in the FTSC_Public area. It was not my intention nor done maliciously.
There was a bug introduced in the tosser software that has already
been rectified.

Again, my apologies..

That's fine. Any chances that this might have affected other Synchronet
systems?

Most likely those who updated between Oct. 31st and Nov. 5th. were affected. ANyone using sbbsecho below 3.49 and 3.51 were affected. Release 3.54 is now the current one which resolved the issue.


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Tommi Koivula wrote to Bill McGarrity on 11-08-17 16:38 <=-

07 Nov 17 19:53, you wrote to all:

There was a bug introduced in the tosser software that has already
been rectified.

The lesson of the month: Never put untested software into production,
at least unattended. :)

'Tommi.. it was one day of an issue... I've certainly seen worse. The author was quick to resolve it.




--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Hello Bill!

08 Nov 17 13:31, you wrote to me:

@TID: SBBSecho 3.02-Win32 r3.54 Nov 7 2017 MSC 1800

There was a bug introduced in the tosser software that has
already been rectified.

The lesson of the month: Never put untested software into
production, at least unattended. :)

it was one day of an issue... I've certainly seen worse. The
author was quick to resolve it.

And once again you installed an untested version to your production system. ;)

'Tommi

---
* Origin: telnet://v6.fidonet.fi (2:221/360)

Hello Bill.

08 Nov 17 13:29, you wrote to me:

That's fine. Any chances that this might have affected
other Synchronet
systems?

Most likely those who updated between Oct. 31st and Nov. 5th. were affected. ANyone using sbbsecho below 3.49 and 3.51 were affected.
Release 3.54 is now the current one which resolved the issue.

We have a few Synchronet nodes in Brazil, I'll let the Sysops know about this. Thank you.

Flavio

... "Deu a louca no Dirceu..." - Reptile Shaman
--- MacFidoIP 1.0 (OSX)
* Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)

Flavio Bessa wrote to Bill McGarrity on 11-10-17 10:41 <=-

08 Nov 17 13:29, you wrote to me:

That's fine. Any chances that this might have affected
other Synchronet
systems?

Most likely those who updated between Oct. 31st and Nov. 5th. were affected. ANyone using sbbsecho below 3.49 and 3.51 were affected.
Release 3.54 is now the current one which resolved the issue.

We have a few Synchronet nodes in Brazil, I'll let the Sysops
know about this. Thank you.

Good deal. Just let them know the revision is now 3.57.


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Re: Latest dump...
By: Flavio Bessa to Bill McGarrity on Fri Nov 10 2017 10:41 am

That's fine. Any chances that this might have affected
other Synchronet
systems?

Most likely those who updated between Oct. 31st and Nov. 5th. were
affected. ANyone using sbbsecho below 3.49 and 3.51 were affected.
Release 3.54 is now the current one which resolved the issue.

We have a few Synchronet nodes in Brazil, I'll let the Sysops know
about this. Thank you.

Yes, I let a few of mine know but mostly I seem a hotbed of Mystic development folks. Best thing to pass to them Flavio, is auto-updating can have it's issues if it involves a tosser.

Here's simple steps that maybe we can develop into something in an FTSC product line though the old 'How-To' FAQ set seems to have fallen by the wayside.

----
When swapping software, nodenumber or tossers, there can be issues causing duplicate messages going out. Any one of the 3 or any combination needs to be done carefully to prevent this. Shifting feeds and not properly detaching from the old feed, can also cause problems. {author note, adding that later if folks seem to want it, it's close but not addressed below}

1. The first step before you upgrade or change anything, is to deliver all outbound you have, or as much as you can. {author note: it's a bit more complex if you have downlinks and are changing node numbers, add details later at need} - Be sure to run a fresh outbound run and deliver that.
- If you feed many, make a snapshot that shows what undeliverable files go to who.

2. Drop your mailer. This will stay down for the rest of the process to prevent exporting your message base. This is EXTREMELY IMPORTANT.
- Copy any undeliverable from your outbound directory to someplace your mailer knows nothing about. Now, delete all that are in your outbound directory. You will file attach them later.

3. Make a system backup of your BBS so you can roll back if something doesn't go right.
- Now start reading any upgrade docs carefully depending on what you are doing. - It may be a smaller thing like just a tosser. Auto-updating tossers is generally not recommended.
- Move any inbound you may have to a separate place your tosser doesnt know about. You will move this back later.

4. Once you have followed all the directions and placed the upgrade in place, run your outbound routine. You should see no outbound packets built. Exception, if you have any game leagues, you may produce tiny updates but they will be 1k. BRE is an example of that when running under SBBS and automation events. Those are harmless.
- If you built anything significant other than a game packet, side line it to someplace else your tosser doesnt know about so you can look at it later. This is a duplicating message base. You will never put it back in outbound but it can be useful to see what was going on later. It can be especially ccritical to have that later for the developer.
- Run your tosser outbound again. You should see nothing built (exception, potential tiny game packets again which depending on game, can happen every toss).
- If you had untossed inbound, now copy it back to your inbound directory and make one more outbound toss. If you feed others, you should see a normal sized load for them. It you do not feed others, you should not see anything (again, except tiny game packets in a league game potentially).

5. Bring up your mailer again at last. If you had undeliverable files for downlinks, use the notes you took earlier and attach them to the correct sites. - Make a mailer run with your uplink. Watch and as soon as it ends, it is best to drop mailer again for a little bit to make sure your outbound is normal but that is only a triple protection.
- {author note, this is where you can see you built packets for your old uplink if you swapped feeds but this FAQ doesn't go in depth on it. Can be added later but it means you forgot to remove the old uplink when you swapped so you are backfeeding from the new uplink to the old uplink.)

------ end draft

Ok it's not perfect but I can move this to another area more appropriate since we are in election mode here to clear traffic, or wait for the election to finish if folks here want to help work on it as a ready resource.

xxcarol

--- SBBSecho 2.12-Win32
* Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)

Good ${greeting_time}, Tommi!

08 Nov 2017 16:38:40, you wrote to Bill McGarrity:

There was a bug introduced in the tosser software that has already
been rectified.

The lesson of the month: Never put untested software into production,
at least unattended. :)

+1

Also: "keep production and test software at properly separated systems".


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-cmlxxvii-mmxlviii

... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
--- /bin/vi
* Origin: http://openwall.com/Owl (2:5020/545)

Hello Carol.

11 Nov 17 10:36, you wrote to me:

Most likely those who updated between Oct. 31st and Nov. 5th.
were affected. ANyone using sbbsecho below 3.49 and 3.51 were
affected. Release 3.54 is now the current one which resolved the
issue.

We have a few Synchronet nodes in Brazil, I'll let the Sysops
know about this. Thank you.

Yes, I let a few of mine know but mostly I seem a hotbed of Mystic development folks. Best thing to pass to them Flavio, is
auto-updating can have it's issues if it involves a tosser.

Here's simple steps that maybe we can develop into something in an
FTSC product line though the old 'How-To' FAQ set seems to have fallen
by the wayside.

Thanks Carol, will crosspost it to my fellow Synchronet Z4 sysops.

Flavio

... "Eu sei de tudo! Eu sou uma g┬nia!" - Fielding
--- MacFidoIP 1.0 (OSX)
* Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)

Re: Latest dump...
By: Flavio Bessa to Carol Shenkenberger on Fri Nov 17 2017 12:56 pm

We have a few Synchronet nodes in Brazil, I'll let the Sysops
know about this. Thank you.

Yes, I let a few of mine know but mostly I seem a hotbed of Mystic
development folks. Best thing to pass to them Flavio, is
auto-updating can have it's issues if it involves a tosser.

Here's simple steps that maybe we can develop into something in an
FTSC product line though the old 'How-To' FAQ set seems to have
fallen by the wayside.

Thanks Carol, will crosspost it to my fellow Synchronet Z4 sysops.

Welcome Flavio! I saw no additions from other members yet so maybe I didn't miss anything.

Some who are more software specific could add it it but the FTSC got out of FAQs of this generic level now decade ago.

Carol
--- SBBSecho 2.12-Win32
* Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)