| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 47 |
| Nodes: | 6 (1 / 5) |
| Uptime: | 12:29:53 |
| Calls: | 683 |
| Calls today: | 1 |
| Files: | 1,194 |
| D/L today: |
31 files (20,004K bytes) |
| Messages: | 198,444 |
| Posted today: | 1 |
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"
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
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.
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.
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.
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.
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.