On 18 Aug 17  13:57:33, C.G. Learn said the following to All:

CL> Well, I'm trying Dbridge again, downloaded the newest version, and started 
CL> scratch. Everything seems to be fine except all my netmail in fidonet is be
CL> put on hold, just like last time. I'm using the internal message editor, an
CL> it's seeing the correct node, but when I save it, or any netmail, it goes o
CL> hold/Unlisted and never goes out, even if the hub calls in. I have everythi
CL> set to crash and hub route. This is where I gave up before, what am I missi

Change the flags to nothing. Do NOT specify the HUB flag. Now type up a quick 
Netmail using the editor. Save and exit.

Then go into Config - Scheduler, and ensure that you have an appropriate ROUTE
TO statement in the system UN-EVENT. If there are any other MAIL events, 
delete them for the time being. The ROUTE TO statement is very important.

For example, if your hub was from some guy named Roger at 1:3828/7, your
Un-Event routing should be 1:3828/7 FOR 1:ALL

For troubleshooting purposes, you could just put your hubs address, FOR ALL 
and that will make sure ALL Netmail gets routed to him. For example, 1:3828/7 
FOR ALL. You get the idea.

Next, go into Config-Internet sessions. Make sure your Hub's system is 
specified in there. Make sure he is listed in the appropriate nodelists, or 
just create a dummy override in the DBNL.AUT file if absolutely necessary.

Now rebuild the nodelist manually (Utilities-Build Nodelist), and also rebuild
the outbound queue (Alt+R). If you have followed these instructions there 
should be no more HOLD/UNLISTED for him.

If the mail does get moved but is not being picked up by the hub, then we move
on to troubleshooting the directory.

If the mail is still on hold/unlisted, then there is something else going on 
that I am not seeing. In that case do a DB EXPORT CG.CFG and email me at 
nandre -at- net229 -dot- org and I'll take a look,

Nick

--- Renegade vY2Ka2
 * Origin: Joey, do you like movies about gladiators? (1:229/426)