I'm now setting up additional bases for agoranet and was wondering what the best way is to setup netmail when you have multiple message networks configured.
I'm assuming that outgoing netmail knows which node to send via because
of the "route info" having a asterisk wildcard (i.e. 21:* for fsxnet and
46:* for agoranet). But what about incoming netmail?
Is it best to have a separate netmail message group for each message network, or will mystic know how to handle a single message base for netmail to all connected message networks? I'm guessing for this to
work, I would simply omit a "Net Address" and "Export To" in the netmail base config?
Another thing, you don't need to set 'export to' for netmail bases.
Entertainingly, the not setting an "export to" explains why, when I
tried to post to fidonet, no one seemed to notice.
I just fixed it, though I'm not sure if I really want to post to fidonet.
On 11-10-19 20:34, lemonlime wrote to All <=-
Is it best to have a separate netmail message group for each message network, or will mystic know how to handle a single message base for netmail to all connected message networks? I'm guessing for this to
work, I would simply omit a "Net Address" and "Export To" in the
netmail base config?
So the takeout here is that if you have two echomail nodes with Route To rules that would apply to a netmail being sent out, the first echomail node with the applicable rules wins and the netmail is sent via that.
You can have one base set up for all netmail or you can have multiple bases set up for each network if you want. I went with the latter option because I wanted to see clearly netmails I had sent/recieved by network separately. But you just as easily have one (to keep it simple) and
Mystic will send all netmails to the 'netmail' type base.
Another thing, you don't need to set 'export to' for netmail bases.
Unlike echomail bases Mystic will use the process I described earlier
and linking netmails bases to a given echomail node does not force
Mystic to use that... so leave that field clear and ensure you have a Route To set up on a echomail node you want to handle echomail for a
give zone:net/node etc..
I use a single netmail base and it works fine. Mystic is pretty good at AKA matching.
Is it best to have a separate netmail message group for each message network, or will mystic know how to handle a single message base for netmail to all connected message networks? I'm guessing for this to
work, I would simply omit a "Net Address" and "Export To" in the netmail base config?
It may or may not be the reason... but if you look at your MUTIL logging at level 3 and check your FIDOPOLL logs thereafter you can at least confirm a packet is exported from your system and sent to the echomail
Cool, this is what I wound up doing as well and it seems to work. I liked having separate bases for the areafix/filefix messages I was sending. Seemed to keep things more organized at least.
On 11-11-19 08:59, lemonlime wrote to Vk3jed <=-
I use a single netmail base and it works fine. Mystic is pretty good at AKA matching.
Thanks! I have one per network configured right now, but may try to consolidate them to give it a try.
Speaking of AreaFix/FileFix messages -- is there a way to toggle to auto-sig in Mystic inside the full screen editor?
Having an auto-sig is convenient, but not very good when posting
netmails to AreaFix/FileFix (which by the way do not seem to support someting like %END or similar), as they will treat the text in the sig
as commands... :-O
Having an auto-sig is convenient, but not very good when posting
netmails to AreaFix/FileFix (which by the way do not seem to support someting like %END or similar), as they will treat the text in the sig
as commands... :-O
Speaking of AreaFix/FileFix messages -- is there a way to toggle to auto-sig in Mystic inside the full screen editor?
an older convention was to place three dashes at the bottom of the
netmail to delineate the end of the commands. But unsure if Mystic
honours that.
Yes, it does. I have the same issue with the signature. I use this
method to end commands with a tearline. Technically a tearline is three dashes followed by a space "--- ". I just enter that at the bottom of my messages to Areafix or Filefix and don't get any error messages. It works with Mystic, Synchronet and BBBS and probably most other areafix's.
On 11-11-19 20:50, Zip wrote to lemonlime <=-
However I ended up creating one netmail area per network (OK so I
haven't joined any more networks just yet, but preparing for Fidonet
and maybe some others), mostly because the requirement for posting
using real names differ between networks. :)
Yep, that works. Just as you say, it is smart enough to decide where to send the netmail based on the routing info.
However I ended up creating one netmail area per network (OK so I haven't joined any more networks just yet, but preparing for Fidonet and maybe some others), mostly because the requirement for posting using real
names differ between networks. :)
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 412 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 06:15:31 |
| Calls: | 8,615 |
| Calls today: | 1 |
| Files: | 13,234 |
| Messages: | 5,936,327 |