Subj : Re: Netmail
To   : pos
From : ogg
Date : Thu Feb 09 2023 01:04 pm

On 09 Feb 2023, pos said the following...
 
 po> Hi,
 po> 
 po> Does anyone have small writeup on how to set up Mystic if I cant just one
 po> Netmail area (and not one for each FTN)?
 po> 
 po> Thanks,
 po> Per
 po> 
 po> ... Everyone smiles in the same language.
 po> 
 po> --- Mystic BBS v1.12 A48 (Linux/64)
 po>  * Origin: Phrenetic BBS (21:1/233)

Here's a snippet that I was given that helped me get my netmail into one area:

You're running the latest version, so there's no issue with one netmail area
whatsoever. Since it's not letting me copy/paste, I can try to give you a short
version of my netmail area's config:

Name: Netmail
Base Type: Netmail
Newsgroup: Netmail
QWK Name: NETMAIL
Echo Tag: NETMAIL
FIle Name: netmail
Path: /home/user/mystic/msgs
List ACS: s20(g2|g3|g4|g5|g6)
Read ACS: s20(g2|g3|g4|g5|g6)
Post ACS: s20(g2|g3|g4|g5|g6)
Sysop ACS: s255(g2|g3|g4|g5|g6)

Net Address: 0:0/0 (Local Address)
Export To: 3 node(s)

That should get you started. Take note on the last one above, you're exporting
to every uplink's individual address for each network with AKA matching. And
list, read, post, and sysop ACS should include every group that is an echomail
network that includes a netmail area (g1 here is my Local areas, so not
needed).

The key for me was to have the "group access" in the message area for netmail set to all of the groups that are going to have netmail (ie. s255(g2|g3|g4|g5|g6)"

Let me know if you need anything else.

ogg
Sysop, Altair IV BBS
altairiv.ddns.net:2323

.... Computers are not intelligent. They only think they are.

--- Mystic BBS v1.12 A49 2023/01/28 (Windows/64)
 * Origin: Altair IV BBS (21:2/147)

.