From Newsgroup: alt.bbs.synchronet

Hello everybody!

For those of you running SBBS and using Golded, what is your setup to read Synchronet E-mail and Fidonet netmail? I have 2 seperate setting, one for E-mail (smb) and the other for netmail (Opus).

AREADEF Syncmail "Synchronet E-Mail" N Net SMB z:\sbbs\data\mail . (Net Pvt) "Live Wire BBS"

AREADEF NETMAIL "FTN Netmail" N Net OPUS z:\sbbs\fido\netmail . (Net Pvt) "Live Wire BBS"


Thanks,
Sabre



---
þ Synchronet þ Live Wire BBS [livewirebbs.com:1025]
--- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2

From Newsgroup: alt.bbs.synchronet

To: Sabre
Hey Sabre!

On Tue, 04 Nov 2025 12:34:46 -0600, you wrote:

Hello everybody!

For those of you running SBBS and using Golded, what is your setup to
read Synchronet E-mail and Fidonet netmail? I have 2 seperate setting,
one for E-mail (smb) and the other for netmail (Opus).

AREADEF Syncmail "Synchronet E-Mail" N Net SMB
z:\sbbs\data\mail . (Net Pvt) "Live Wire BBS"

This one by itself should read both email and Fidonet netmail, since it is all stored in the mail base.

* However, don't try to write anything there, as you risk corrupting your mail base.

AREADEF NETMAIL "FTN Netmail" N Net OPUS z:\sbbs\fido\netmail . (Net Pvt) "Live Wire BBS"

I'm guessing this one does nothing for you. Synchronet's "netmail" is stored in the same base as email (/sbbs/data/mail.*). This is why you shouldn't write to it, because Golded doesn't know the difference between what is BBS email, POP/SMTP email, or netmail.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (723:1/1)
ï¿­ Synchronet ï¿­ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
--- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2

From Newsgroup: alt.bbs.synchronet

To: Sabre
Hey Sabre!

On Wed, 05 Nov 2025 08:40:12 -0600, you wrote:

AREADEF Syncmail "Synchronet E-Mail" N Net SMB
z:\sbbs\data\mail . (Net Pvt) "Live Wire BBS"

AREADEF NETMAIL "FTN Netmail" N Net OPUS
z:\sbbs\fido\netmail . (Net Pvt) "Live Wire BBS"

ok, I see now. I do use the second netmail with GoldED, SBBS see's it
and sendsout that mail. But from a GoldED point, I can't use the SMB
E-mail to write netmail. So really GoldED can't use E-mail/Netmail to
write outbound mail.

So what you're saying is, writing a new netmail in the "FTN Netmail" area works? If that's true, I'm guessing you don't /receive/ netmail there, as it goes in the "Synchronet E-Mail" area instead?

If that is the case, I suppose maybe when you receive a netmail in "Synchronet E-Mail", maybe you could reply to it (using ALT-N so you can choose a different area to write to) in the "FTN Netmail" area.. Hmm..

Also, before I forget, you can't use 'smbutil' to pack/renumber your message bases when using Golded, either. This is pretty common/standard with any external message reader that doesn't share message/newscan pointers, though. You'll end up with something like *123048979 new messages in each area 'smbutil' renumbers, and Golded won't know where you left off, so it'll start back at the first message.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (723:1/1)
ï¿­ Synchronet ï¿­ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
--- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2

From Newsgroup: alt.bbs.synchronet

To: Digital Man
Hey Digital!

On Wed, 05 Nov 2025 18:00:44 -0800, you wrote:

Packing and renumbering are 2 different things. Packing should have no effect on Golded. And a sysop shouldn't renumber any message base
without a very good reason.

The default timed event for '%!smbutil% mp100 /path/to/sbbs/data/subs/*.shd' definitely has a bad effect on Golded. I imagine it probably has to do with deleting olds messages, messages over max, and renumbering the messages. If your max is 2000 messages, the 2014th message in the area that gets posted before smbutil is ran, gets changed to message number 2000.

All I was saying is that needs to be disabled or Golded will spaz out the next time you run it after smbutil runs.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (723:1/1)
ï¿­ Synchronet ï¿­ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
--- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2

From Newsgroup: alt.bbs.synchronet

To: Accession
Re: GoldED and Synchronet Question
By: Accession to Digital Man on Thu Nov 06 2025 04:35 pm

Hey Digital!

On Wed, 05 Nov 2025 18:00:44 -0800, you wrote:

Packing and renumbering are 2 different things. Packing should have no effect on Golded. And a sysop shouldn't renumber any message base
without a very good reason.

The default timed event for '%!smbutil% mp100 /path/to/sbbs/data/subs/*.shd' definitely has a bad effect on Golded. I imagine it probably has to do with deleting olds messages, messages over max, and renumbering the messages.

Technically that command doesn't renumber of the messages. I believe it could be messing up Golded, but it's not due to renumbering.

If
your max is 2000 messages, the 2014th message in the area that gets posted before smbutil is ran, gets changed to message number 2000.

Each message has a unique monotonically-increasing number that's not changed by maintaining or packing a message base. 'fixsmb' has a -renumber option (which understably would have a bad effect on Golded), smbutil doesn't have that option.

All I was saying is that needs to be disabled or Golded will spaz out the next time you run it after smbutil runs.

Gotcha.
--
digital man (rob)

Sling Blade quote #2:
Karl (re: killing Doyle): I hit him two good whacks in the head with it.
Norco, CA WX: 69.2øF, 63.0% humidity, 5 mph WNW wind, 0.00 inches rain/24hrs --- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2

From Newsgroup: alt.bbs.synchronet

To: Digital Man
Hey Digital!

On Thu, 06 Nov 2025 16:22:10 -0800, you wrote:

Technically that command doesn't renumber of the messages. I believe it could be messing up Golded, but it's not due to renumbering.

Ok. Yeah, it definitely messes up Golded.

On the other hand, any newsreader I've used with Synchronet doesn't have an issue with the smbutil event.

If
your max is 2000 messages, the 2014th message in the area that gets
posted before smbutil is ran, gets changed to message number 2000.

Each message has a unique monotonically-increasing number that's not
changed by maintaining or packing a message base. 'fixsmb' has a
-renumber option (which understably would have a bad effect on Golded), smbutil doesn't have that option.

Understood, and no.. I've never used that fixsmb option. I would imagine that the last read pointers move and Golded doesn't know they moved, or something. The same happens when using Golded to read /sbbs/data/mail. When an event of some sort kills read mail (or maybe it's killed after 30 days or something), Golded craps the bed there, too.

I just chalk it up as Golded's Synchronet support not being updated. Besides the one fix Vitaliy did somewhat recently, and the patches you've made somewhat recently.. nobody has updated that code in ages. *shrug*

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (723:1/1)
ï¿­ Synchronet ï¿­ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
--- Synchronet 3.21a-Linux NewsLink 1.2
* Vertrauen - Riverside County, California - telnet://vert.synchro.net
--- Synchronet 3.20b-Win32 NewsLink 1.2