Any help/ideas what is wrong there would be much appreciated!
btw, i now see that in the ftn folder a new folder pinet.13a has been created holding a clo file. But i have defined OUTBOUND pointing to ftn/out in magimail.prefs. Is it required to define the folders multiple times for each network?
domain fidonet /usr/local/fido/outbound 1
domain fsxnet /usr/local/fido/outbound 1
domain fidonet /usr/local/fido/outbound 1
domain fsxnet /usr/local/fido/outbound 1
Just a quick addendum. The number at the end is your default (first used in your config I think) zone, so it might be something other than 1 or
2. If your first net was fsxnet then it would be 21.
Yes, you need a domain line for each network. I have fidonet and fsxnet and my default domain in zone one, so my doomain lines look like this..
domain fidonet /usr/local/fido/outbound 1
domain fsxnet /usr/local/fido/outbound 1
If you are in zone 2 you'll need to change the numbers at the end of the lines to 2.
not sure if that was it. i gonna test it. actually i think it is something related to magimail as everything was working but the outbound folder used was pinet.13a instead of out.
domain fidonet /usr/local/fido/outbound 1
domain fsxnet /usr/local/fido/fsxnet 21
you want:
domain fidonet /usr/local/fido/outbound 1
domain fsxnet /usr/local/fido/fsxnet 1
NODE 314:314/0 "ZIP" "" AUTOADD PACKNETMAIL CRASH
DEFAULTGROUP B
NODE 314:314/0 "ZIP" "" AUTOADD PACKNETMAIL CRASHI think you want to remove the CRASH to make it poll straight away.
DEFAULTGROUP B
On 08-08-20 14:12, Al wrote to Mindsurfer <=-
I am using a 3D tosser so my outbound directories are all the same with something like .13a or for fsxnet .015 added to them.
If you are working with a 5D outbound it works differently. You can
have different outbound directories for each net.
domain fidonet /usr/local/fido/outbound 1
domain fsxnet /usr/local/fido/fsxnet 21
When working with a 3D outbound you need to use the same outbound directory name along with the same number at the end of the domain
line. Your outbounds will get the zone number in hex appended to them.
I'm not sure but I think MagiMail uses a 3D outbound.
On 08-09-20 08:32, apam wrote to Al <=-
domain fidonet /usr/local/fido/outbound 1
domain fsxnet /usr/local/fido/fsxnet 21
you want:
domain fidonet /usr/local/fido/outbound 1
domain fsxnet /usr/local/fido/fsxnet 1
domain fidonet /usr/local/fido/outbound 1
domain fsxnet /usr/local/fido/fsxnet 21
Actually, with the tossers I've seen, you have to use the same number
for all zones in binkd.conf, to make it work, so in the 5D example
above, all the zone numbers would still be 1.
domain fidonet /usr/local/fido/outbound 1
domain fsxnet /usr/local/fido/fsxnet 1
Same as I use with SBBSEcho in 5D mode.
On 08-09-20 04:07, Al wrote to Vk3jed <=-
If your getting .015 added to your outbound directory then you would
need to use the same default zone number.
I always thought that a 5D outbound would need the actual zone number
and not get the .015 added to the outbound for that zone but I have
never had a fully 5D tosser to play with.
Mystic seems to create outbound directories per net, but also has the
.015 zone in hex appended to the outbound. Is that a fully 5D outbound structure?
There can be other cases to like Blue White who needs to use the actaul zone number with binkleyterm along with squish.
On 08-09-20 04:14, Al wrote to Vk3jed <=-
Hello Vk3jed,
domain fidonet /usr/local/fido/outbound 1
domain fsxnet /usr/local/fido/fsxnet 1
Same as I use with SBBSEcho in 5D mode.
Is SBBSecho a 5D tosser? My outbound directories are all named outbound with the zone number in hex appended as I have always seen.
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 68 |
Nodes: | 4 (0 / 4) |
Uptime: | 07:51:51 |
Calls: | 941 |
Files: | 7,941 |
Messages: | 297,563 |