Sorry for replying to myself, my software doesn't give the option to
change the to: field. Any way, my direct netmails for areafix and
filefix are working. Routed mail is not. I've got the routing set
properly in fastecho for 1:229/426 (1:* 2:* 3:* 4:*). Any ideas?
Hey Martin!
On Tue, Aug 19 2025 11:50:00 -0500, you wrote:
Sorry for replying to myself, my software doesn't give the option to change the to: field. Any way, my direct netmails for areafix and
filefix are working. Routed mail is not. I've got the routing set properly in fastecho for 1:229/426 (1:* 2:* 3:* 4:*). Any ideas?
If you're trying to route all of your netmail to 1:229/426, then why do
most of your "fastecho pack" commands start with 1:340/400?
If you take a look at your fastecho logs, you should be able to see where these netmails are getting packed for. If you're sending them to Rob
Starr, and he's not routing your netmail properly, that's probably your problem.
I also haven't used fastecho in ages, but I don't remember anything about the 'via' option, so I probably never used it. If every link is setup correctly, and your routing table is correct, 'fastecho pack' should be
all you need. Maybe even a 'scan' option afterwards to send it over to
your mailer, unless the 'pack' command does both.
If you're trying to route all Fidonet netmail through Nick Andre, then
what you have above is correct. You shouldn't need anything else for Fidonet. Then, you will need a separate route setting for zone 10 where
10:* goes there, a separate route setting for zone 21 where 21:* goes
there, and a separate one for every other network you're a part of.
If what you are trying to do is route everything through Nick, but have a separate direct link to Rob, then you would need a separate route setting for 1:340/400 specifically where you only route 1:340/400.* to him, and it would have to be listed /before/ Nick's entry (as 1:* 2:* 3:* 4:* is the "catch all" that is used if and when any direct links are not used.
Hope that makes it a bit easier to understand, and hope it helps.
Regards, Nick
I can't pack netmail to 30:30/99, only everything else. That is for
gated email. Scan goes before pack. I'm not sure if I need via or
just the node number. A lot of netmail goes to things like 1:40/150
and is going via 1:229/426.
Hey Martin!
On Wed, Aug 20 2025 15:06:00 -0500, you wrote:
I can't pack netmail to 30:30/99, only everything else. That is for
gated email. Scan goes before pack. I'm not sure if I need via or
just the node number. A lot of netmail goes to things like 1:40/150
and is going via 1:229/426.
If you can't pack and scan for 30:30/99, then it probably shouldn't even
be in your tosser's configuration. Is this something you're doing with
IREX or some such?
I'm fairly sure you should pack your netmail before you try to scan it
out. Although, some tossers (like HPT for example), you can enable a configuration option "PACKNETMAILONSCAN" so you don't have to use both commands, but I don't know if FastEcho has that option or not.
You don't need "via". This is what setting 1:229/426 (1:* 2:* 3:* 4:*) already does. Any node number in zone 1-4 will go to Nick Andre first. And if you want to add any direct links for Fidonet, they need to be added /before/ 1:229/426 in order to work properly.
Most tossers read a routing table from top to bottom. So if Nick's entry
is first, no other entries for 1:* 2:* 3:* 4:* will work properly.
While it seems like you're ultimately confused as to how your tosser
works, at this point, you should probably start over with Fidonet, and
just have 1:229/426 as a link, and route 1:* 2:* 3:* 4:* through it.
Once you've done that, and it works properly, then you can add direct
links and/or other route links one at a time while making sure they work before moving on to the next. If you don't need direct links or other routes, then leave it alone with the one Fidonet link, and let Nick's
system send any/all of your echomail and netmail where it needs to go. He kinds knows what he's doing. ;)
If you can't pack and scan for 30:30/99, then it probably
shouldn't even be in your tosser's configuration. Is this
something you're doing with IREX or some such?
It needs to be scanned, not packed.
I'm fairly sure you should pack your netmail before you try to
scan it out. Although, some tossers (like HPT for example), you
can enable a configuration option "PACKNETMAILONSCAN" so you don't
have to use both commands, but I don't know if FastEcho has that
option or not.
Scan scans the message areas for outbound messages, including
netmail. Then pack sends the netmail.
While it seems like you're ultimately confused as to how your
tosser works, at this point, you should probably start over with
Fidonet, and just have 1:229/426 as a link, and route 1:* 2:* 3:*
4:* through it.
I'm trying that, but only 1:* is routing, not 2:* or 4:*.
To work around this, I've got fastecho scanning, then irex sending,Seems like you're doing entirely too much, but whatever works for you I suppose.
then the process waiting to close (it gets put to the background, in
which case pack runs immediately, so I run a tasklist | findstr
rexw.exe and check the error level.), then packing all of the rest
of the netmail. Seems to be working.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 537 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 140:16:41 |
| Calls: | 10,249 |
| Calls today: | 1 |
| Files: | 13,981 |
| Messages: | 6,407,570 |