If I leave the route info blank in my node setup will it send direct to whatever node I am netmailing, provided there's a nodelist entry? I prefer crash direct for just about everything.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)

Tuesday September 27 2016 17:35, you wrote to All:

If I leave the route info blank in my node setup will it send direct
to whatever node I am netmailing, provided there's a nodelist entry? I prefer crash direct for just about everything.

If you want to route netmail in this net add 21:* to the route info on 21:1/100's node entry in your echomail nodes and everything will be routed to that address. If you want to crash netmail to a node you need to add that node to your echomail nodes.

... My opinions are my own; mistakes are the computer's fault.
--- GoldED+/LNX 1.1.5-b20160322
* Origin: The Rusty MailBox - Penticton, BC Canada (21:1/110)

Tuesday September 27 2016 17:35, you wrote to All:

If I leave the route info blank in my node setup will it send direct
to whatever node I am netmailing, provided there's a nodelist entry? I prefer crash direct for just about everything.

Fidopoll recently got the option to search and poll nodes not in your echomail nodes as long as they can be found in your nodelist. It wouldn't take much at this point to send netmail directly. We would need a way to mark netmail as direct or crash and mutil would need to know what to do with that.

... Good judgement comes from experience which comes from poor judgement
--- GoldED+/LNX 1.1.5-b20160322
* Origin: The Rusty MailBox - Penticton, BC Canada (21:1/110)

On 09/27/16, Al pondered and said...

If you want to route netmail in this net add 21:* to the route info on 21:1/100's node entry in your echomail nodes and everything will be
routed to that address. If you want to crash netmail to a node you need
to add that node to your echomail nodes.

That is correct, Mystic will route netmail direct to echo nodes that are defined in the config. By using 21:* in the 21:1/100 echonode it tells Mystic to route all Zone 21 netmail to the HUB.

Nodes that are using 21:2/100 for Usenet content need to be wary of doing
this as there are different settings required for routing netmail to net 2 - check the docs I have hatched out about that ... that said I'd say most who
are set up for Usenet feeds have already worked things out as per the docs already else they would not have been getting their feeds :)

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 09/27/16, Al pondered and said...

Fidopoll recently got the option to search and poll nodes not in your echomail nodes as long as they can be found in your nodelist. It
wouldn't take much at this point to send netmail directly. We would need
a way to mark netmail as direct or crash and mutil would need to know
what to do with that.

Yes correct, and in config > message base settings - there are switches to
set netmail with those flags, but be aware it's a blanket approach as all netmails are set that way. I have not experimented with those settings very much. I've found not using them has not impacted on my ability to send items via crash traffic as the echonode settings dictate the way the .bso style
files are being created for fidopoll to act on :)

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 09/28/16, peconi pondered and said...

hey all,

so im trying to send netmail to 46:1/100 alas even though it gets sent
and I see it outgoing via fidopoll to this node Nick on the other end
says he sees my mail coming as if from 1/0/0 and for that reason my messages to AreaFix to AgoraNet are failing.

OK.

i only have 1 netmail message base and network on it is set to local and it is set to export to no nodes. this setup seems to work fine for
fsxNet and retroNet as both of those respond to netmails and I am
getting stuff properly, but AgoraNet isn't doing it.

Export to nodes is correct, it should not be set up, Mystic uses routing info in your echonodes to look for where to send netmail or if the netmail is addressed to an echonode it will just send it direct to it.

What does your routing line look like for your Agoranet echonode?

in my node settings for this network i have a route set properly as well as my my own zone info.

Can you share this please. Minus the passwords :)

I agree with Al's comments in his reply to you in FSX_GEN about restarting
MIS or MIS2 when making changes in this area.

My experience around this leads me to think that despite the matching that is going on with echonodes the network address set in the netmail base does influence what is being sent with your netmail. That's why in the case of Usenet netmails to 21:2/100 I had to create instructions to folks to create a different netmail base using their net 2 address.

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | New Zealand | agency.bbs.geek.nz (21:1/101)

Avon wrote to peconi <=-

My experience around this leads me to think that despite the matching
that is going on with echonodes the network address set in the netmail base does influence what is being sent with your netmail. That's why in the case of Usenet netmails to 21:2/100 I had to create instructions to folks to create a different netmail base using their net 2 address.

Possible bug? I cut down to only one netmail area, which works fine with my nets in different zones. Perhaps the AKA matching only matches zones, not nets? When I ran multiple netmail areas in the past, I had netmails imported to multiple bases, which was annoying too!


... Don't sweat petty things.... or pet sweaty things.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

On 09/29/16, Vk3jed pondered and said...

Possible bug? I cut down to only one netmail area, which works fine
with my nets in different zones. Perhaps the AKA matching only matches zones, not nets? When I ran multiple netmail areas in the past, I had netmails imported to multiple bases, which was annoying too!

I'm just not sure... I'll need to do some more testing as time permits.

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Avon wrote to Vk3jed <=-

Possible bug? I cut down to only one netmail area, which works fine
with my nets in different zones. Perhaps the AKA matching only matches zones, not nets? When I ran multiple netmail areas in the past, I had netmails imported to multiple bases, which was annoying too!

I'm just not sure... I'll need to do some more testing as time permits.

No probs. In the meantime, I'll try adding another netmail base and see what happens, and if it fixes my netmail issues in 21:2/*.


... Honk if you love peace and quiet!
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

Found a couple of issues.

1)

If an echonode is made inactive Mystic will still try to deliver netmail to it.

Details:

I had a test echonode set up as 21:2/101 at the 1/100 HUB it had no routing info stated and the domain name was not fsxnet. This echonode was inactive and sat higher up the list of echonodes than the active 21:2/100 echonode that
sat further down and had routing info to direct 21:2/* traffic to it.

Incoming netmails to 1/100 could not be processed by it and passed correctly
on to 2/100 as the earlier 'inactive' entry was confounding things.

[snip]

+ Oct 18 20:29:03 Importing 0b2b13f7.pkt (21:1/101 to 21:1/100)
! Oct 18 20:29:03 No netmail route Nigel Reed@21:2/101

[snip]

changing the 'inactive' echonode to a different zone:net/node number like 99:99/999 solved the issue.

[snip]

+ Oct 18 21:13:24 Importing 0b2f1335.pkt (21:1/101 to 21:1/100)
+ Oct 18 21:13:24 Route (21:1/101 to 21:2/101) via 21:2/100

[snip]

Recommend:

Ensure 'inactive' really is inactive for netmail handling and any echomail and/or file echo tossing to the node.


2)

Netmail sent to a HUB with a packet password is routed with the password
intact causing downstream problems.

Details:

A node (also 2/101 in this case) sent me netmail addressed to 1/101 via 2/100 but was using a packet password.

The packet password was known at 2/100 and so the message was processed and routed to 1/100 on it's way to me.

But at 1/100 there is no echonode entry for 2/101 so nothing set up with any packet passwords etc. so 1/100 failed to process route the netmail to 1/101

[snip]

+ Oct 18 21:18:13 Importing 0ad22395.pkt (21:2/101 to 21:1/100)
! Oct 18 21:18:13 Invalid PKT password

[snip]

Recommend: HUBs accepting routed netmail strip packet passwords before
routing the netmail on to another HUB.



Hope this all helps :)

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

If an echonode is made inactive Mystic will still try to deliver netmail to it.
Netmail sent to a HUB with a packet password is routed with the password intact causing downstream problems.

Thank you for the great detail. I will look into these next time I have some time to do some programming.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 10/22/17, g00r00 pondered and said...

If an echonode is made inactive Mystic will still try to deliver netm to it.
Netmail sent to a HUB with a packet password is routed with the passw intact causing downstream problems.

Thank you for the great detail. I will look into these next time I have some time to do some programming.

You're welcome, and thanks!

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

ok, New issue, I am trying to send netmail to areafix@42:1/1 but Mystic keeps telling me it's an unknown user.

-Dallas Vinson

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Before the Web (21:4/102)

On 09/05/18, Lupine Furmen pondered and said...

ok, New issue, I am trying to send netmail to areafix@42:1/1 but Mystic keeps telling me it's an unknown user.

Netmail or BBS email??

That could be why... or you may have enforced nodelist lookup set to yes?

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Netmail or BBS email??

That could be why... or you may have enforced nodelist lookup set to yes?

Netmail. email between BBS'. And I just double checked and Nodelist lookup is turned off.

-Dallas Vinson

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Before the Web (21:4/102)

ok, New issue, I am trying to send netmail to areafix@42:1/1 but Mystic keeps telling me it's an unknown user.

Ok, everyone can disregard this one. I was trying to use the "Write Email" command rather than "Post" to the netmail message base. All is good now. Just need to get the NTVDM issues resolved so I can get all my doors back online.

Changed Windows versions and now my NTVDM is not wanting to work with NetFoss for some reason. Have reinstalled Netfoss, but it did not help any.

-Dallas Vinson

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Before the Web (21:4/102)

Changed Windows versions and now my NTVDM is not wanting to work with

NetFoss

for some reason. Have reinstalled Netfoss, but it did not help any.

What version of Window$ did you change to?
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: fsxNet: Omicron Theta * Southaven, MS * winserver.org (21:2/136)

What version of Window$ did you change to?

Went from Win7Ultimate to Win7Pro because we could not find the installs we
had used for Ultimate.

-Dallas Vinson

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Before the Web (21:4/102)

Went from Win7Ultimate to Win7Pro because we could not find the installs we had used for Ultimate.

Gotcha!!!
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: fsxNet: Omicron Theta * Southaven, MS * winserver.org (21:2/136)

On 09/06/18, Lupine Furmen said the following...

Went from Win7Ultimate to Win7Pro because we could not find the installs we had used for Ultimate.

-Dallas Vinson

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Before the Web (21:4/102)

Why are you running A38? That's one release behind the current A39. While
there maybe minor bugs in A39, netmail and all the basics work fine with no real problems.

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Workpoint (21:1/145.3)

Mystic Sysop question... How do you organize your Netmail areas if you have multiple (4-5) networks? E.g. A "Netmail (NETWORK)" message area in every network message base? A Netmail Message Group that pulls each area into a consolidated group? Or, a single NETMAIL area/file for all, so they are
in a single location?

Probably preference-based, but just curious.

Alpha

--- Mystic BBS v1.12 A44 2020/02/04 (Linux/64)
* Origin: Card & Claw BBS | Analog Gaming: Board Games, RPGs (21:4/158)

into a consolidated group? Or, a single NETMAIL area/file for all, so
they are in a single location?

I have a single Netmail area. It will auto detect the destination address and set the message to the appropriate server defined in your route.

Another thing I did was HIDE the netmail area from the message group list. I have a dedicated email/netmail menu that will set your group/base to the Netmail g/b when you check for messages or post a netmail. I lump
email/netmail as a seperate thing from echomail.

Just my preference.

|20|15ÚÄ|16|08´ |08De|07ad|15be|07a|08tz b|07b|15s
|08ÀÄÙÃÄ¿ |08:>.|07A|08rk |0710|08:|07101|08/|0714|08.
|04þ |08À|20|15Ä|16|08Ù |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
|04A|07n|15al|07o|08g |08:>.|12F|04sx |1221|08:|122|08/|12123|08. |15.|04p|07HENOM|15. |08:>.|15S|07ci |1577|08:|151|08/|15131|08. |04°±°|08±ÛÛÜÝ|08:>.|11T|03qw |111337|08:|113|08/|1113|08.

--- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
* Origin: deadbeatz.org (21:2/123)

Probably preference-based, but just curious.

Correct. I have a unique netmail base per net. It just keeps things a bit cleaner IMO.

--- Mystic BBS v1.12 A44 2020/02/04 (Linux/64)
* Origin: monterey bbs (21:1/168)

I have a single Netmail area. It will auto detect the destination
address and set the message to the appropriate server defined in your route.

That's a good idea!

-Alpha

--- Mystic BBS v1.12 A44 2020/02/04 (Linux/64)
* Origin: Card & Claw BBS | Analog Gaming: Board Games, RPGs (21:4/158)

Mystic Sysop question... How do you organize your Netmail areas if you have multiple (4-5) networks? E.g. A "Netmail (NETWORK)" message area in

I just use a single Netmail area, and I have it set to show up in all of my groups that are not my local message group.

--- Mystic BBS v1.12 A44 2020/02/04 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 06 Feb 2020, Alpha said the following...

Mystic Sysop question... How do you organize your Netmail areas if you have multiple (4-5) networks? E.g. A "Netmail (NETWORK)" message area in every network message base? A Netmail Message Group that pulls each area into a consolidated group? Or, a single NETMAIL area/file for all, so
they are in a single location?

I include each netmail base in my group for each network AND also have a separate group that includes all netmail bases. When anyone goes to send a netmail message I chain commands. First I have them join the netmail group, then Change area and finally post the netmail.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)

On 02-06-20 09:13, ryan wrote to Alpha <=-

Probably preference-based, but just curious.

Correct. I have a unique netmail base per net. It just keeps things a
bit cleaner IMO.

I tried that initially, but had issues. Switched to a single netmail base and no problems.


... The older you get, the more important is is not to act your age.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

Hi

I sent a message to garycrunk via netmail. I didn't get a reply, because
for some reason when you reply to my message on Another f-ing bbs, it
uses 21:4/100 as the reply address.

Looking at the kludges of my netmail they all look right, but why would
mystic prompt you for the return address and autofill it with something
other than the origin address?

I did notice, that my address is 21:1/126 and gary's is 21:4/126.. ie the
same node number (just different nets).

Also the net mail I sent was routed, so I guess technically it came from 21:4/100

Hmm.

Andrew


--- TitanFTN (Linux/x86_64)
* Origin: Wunderlust BBS - wunderlust.ddns.net:2023 (21:1/126)

Never mind. I figured it out. Mystic expects a MSGID kludge in netmail.

Andrew

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Another F-ing BBS (21:4/126)

Re: Re: Netmail
By: apam to apam on Tue Aug 11 2020 05:34 am

Never mind. I figured it out. Mystic expects a MSGID kludge in netmail.

That's interesting, it seems mystic is using the @MSGID to address replies
in netmail?

I've reported the issue of netmail having the wrong from address before and I have seen others report it also. It only happens to netmail that was routed.

g00r00 has looked at it but hasn't yet figured out a better way to deal with this.

Ttyl :-),
Al

... You! What PLANET is this? McCoy, stardate 3134.0.
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Hello All,

I've just been looking over my Mystic BBS after a time. Can somebody send me a netmail? I wondering if anything has changed in the way it displays the from address and how it addresses a reply.

I'm also wondering about the web server. I have it enabled currently but I just
get an error 404, page not found error although I do have an index.html in the webroot directory. Does anyone have that working?

Ttyl :-),
Al

--- Mystic BBS v1.12 A47 2020/10/13 (Linux/64)
* Origin: Equinox BBS - Penticton, BC Canada (21:4/106.2)

Hello All,

I've just been looking over my Mystic BBS after a time. Can somebody
send me a netmail? I wondering if anything has changed in the way it displays the from address and how it addresses a reply.

I'm also wondering about the web server. I have it enabled currently but
I just get an error 404, page not found error although I do have an index.html in the webroot directory. Does anyone have that working?

Ttyl :-),
Al

--- Mystic BBS v1.12 A47 2020/10/13 (Linux/64)
* Origin: Equinox BBS - Penticton, BC Canada (21:4/106.2)

Al,
I am a little confused. When I tried to send you a netmail and did a look
up of Equinox BBS, nothing showed up in the node list by that name. So I did
a search by node number 21:4/106 and the below information showed up. As you notice your message post tag line is showing something completely different.

In short, your tag is showing Equinox BBS at 21:4/106 , but in the node
browser no such BBS name exists.

Address: 21:4/106
System Name: The Rusty Mailbox BBS
Location: Penticton CAN
Operator: Alan Ianson
Phone: -Unpublished-
Internet: trmb.ca

---

Rocket Town BBS - Telnet: rtbbs.ddns.net
fsxNET: 21:1/203 fidoNET:1:135/383 - sciNET: 77:1/125 Titusville, FL. USA

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Rocket Town BBS (21:1/203)

On 14 Oct 2020, Argos said the following...

I am a little confused. When I tried to send you a netmail and did a look up of Equinox BBS, nothing showed up in the node list by that name. So I did a search by node number 21:4/106 and the below information showed up. As you notice your message post tag line is showing something completely different.

My node is 21:4/106 and I have an MBSE BBS setup that handles that.

In short, your tag is showing Equinox BBS at 21:4/106 , but in the node browser no such BBS name exists.

Address: 21:4/106
System Name: The Rusty Mailbox BBS
Location: Penticton CAN
Operator: Alan Ianson
Phone: -Unpublished-
Internet: trmb.ca

Yep, that is my node. I am looking for a netmail to 21:4/106.2, that's the address of my Mystic BBS that I want to check on. It'll travel the net to my node (up above there) and then be directed from there to 21:4/106.2 so I'll be able to read it on my Mystic BBS. In a nutshell, my node feeds my point netmail, echomail and files, it's a different setup than my main node.

Ttyl :-),
Al

--- Mystic BBS v1.12 A47 2020/10/13 (Linux/64)
* Origin: Equinox BBS - Penticton, BC Canada (21:4/106.2)

Re: Netmail
By: Al to All on Wed Oct 14 2020 08:39 am

I've just been looking over my Mystic BBS after a time. Can somebody send

me a netmail? I wondering if anything has changed in the way it displays the from address and how it addresses a reply.

I sent you one last night - hopefully you got it.

...ëîåï

... A feature is a bug with seniority.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 15 Oct 2020, alterego said the following...

I've just been looking over my Mystic BBS after a time. Can somebody me a netmail? I wondering if anything has changed in the way it displ the from address and how it addresses a reply.

I sent you one last night - hopefully you got it.

Nothing yet but thanks, I'll keep an eye out.

Ttyl :-),
Al

--- Mystic BBS v1.12 A47 2020/10/13 (Linux/64)
* Origin: Equinox BBS - Penticton, BC Canada (21:4/106.2)

Re: Netmail
By: Al to alterego on Wed Oct 14 2020 10:19 pm

I sent you one last night - hopefully you got it.

Nothing yet but thanks, I'll keep an eye out.

Hmm.. you should have got it by now - unless its in quaranteen? :)

2020-10-14 22:05:18 Created NetMail (1.msg) from Deon George (21:2/116) to Al (21:4/106.2), attr: 0181, subject: Netmail
2020-10-14 22:05:18 Packing NetMail (1.msg) from Deon George (21:2/116) to Al (21:4/106.2), attr: 0181, subject: Netmail
2020-10-14 22:05:18 Routing NetMail (1.msg) to 21:2/100
2020-10-14 22:05:18 SBBSecho (PID 26393) exiting with error level 0, NetMail(0 imported, 1 exported, 1 packed)

Oct 14 22:05:20 p-4-1 synchronet: evnt BINKOUT Attempting callout for 21:2/100@fsxnet, file: /opt/sbbs/fido/outbound.015/00020064.cut
Oct 14 22:05:20 p-4-1 synchronet: evnt BINKOUT JSBinkP/1.123 callout to 21:2/100@fsxnet started
Oct 14 22:05:20 p-4-1 synchronet: evnt BINKOUT Connecting to 21:2/100@fsxnet at
error404bbs.ddns.net:24555
Oct 14 22:05:24 p-4-1 synchronet: evnt BINKOUT Peer version: Mystic/1.12A46 binkp/1.0
Oct 14 22:05:24 p-4-1 synchronet: evnt BINKOUT Authentication successful: secure
Oct 14 22:05:24 p-4-1 synchronet: evnt BINKOUT Sending file: /opt/sbbs/fido/outbound.015/00020064.cut (0.7KB)
Oct 14 22:05:24 p-4-1 synchronet: evnt BINKOUT Sent file: /opt/sbbs/fido/outbound.015/00020064.cut (0.7KB)
Oct 14 22:05:24 p-4-1 synchronet: evnt BINKOUT We got an M_EOB, but there are still 1 files pending M_GOT
Oct 14 22:05:24 p-4-1 synchronet: evnt BINKOUT Deleted file: /opt/sbbs/fido/outbound.015/00020064.cut

...ëîåï

... Never underestimate the power of human stupidity.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 15 Oct 2020, alterego said the following...

Nothing yet but thanks, I'll keep an eye out.

Hmm.. you should have got it by now - unless its in quaranteen? :)

Your logs indicate it went to 21:2/100. Something has happened between here and
there.. not exactly sure what..

Ttyl :-),
Al

--- Mystic BBS v1.12 A47 2020/10/13 (Linux/64)
* Origin: Equinox BBS - Penticton, BC Canada (21:4/106.2)

On 15 Oct 2020, alterego said the following...

Nothing yet but thanks, I'll keep an eye out.

Hmm.. you should have got it by now - unless its in quaranteen? :)

I found it. It's bouncing back and forth between 21:4/106 and 21:4/106.2. It's up to 13K of via lines now. ;)

I'll have to see if I can figure out why that is happening.

Ttyl :-),
Al

--- Mystic BBS v1.12 A47 2020/10/13 (Linux/64)
* Origin: Equinox BBS - Penticton, BC Canada (21:4/106.2)

On 14 Oct 2020 at 10:19p, Al pondered and said...

Nothing yet but thanks, I'll keep an eye out.

Have also belatedly sent you a reply to a test netmail you sent me :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Nothing yet but thanks, I'll keep an eye out.

Have also belatedly sent you a reply to a test netmail you sent me :)

Still nothing here. I deleted one that never got tossed into the message base, it just kept going back and forth between 4/106 and 4/106.2. Looking at Mystic's log, Mystic seemed to think the message was to 1/186 and so sent it back to 4/104 and it would get sent back to 4/106.2 again.

I'll try to figure out what's up there.

I do send netmail back and forth between the two, areafix and filefix without issue so I'm not sure what going on.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Hello Al,

I'm also wondering about the web server. I have it enabled currently but I jus >get an error 404, page not found error although I do have an index.html in the
webroot directory. Does anyone have that working?

The actual Mystic webroot here is /home/mystic/webroot/www/index.html

There should actually be a /www and a /cfg directory under /mystic with /www being the directory that Mystic serves your html files from. The /cfg directory as I understand it is for future use.

Jeff

--- BBBS/Li6 v4.10 Toy-5
* Origin: FSXNET: The Ouija Board - bbs.ouijabrd.net (21:1/128)