Hello everybody!

I've just had a new node do a areafix request and the body of the netmail just has

%+ALL

in it, and the system reports that:


Here is the result of your Areamgr request:

* Area %ALL not found.


Reading the helpfile a "%+ALL" should work.


Recomendations?




Stephen


--- GoldED+/LNX 1.1.5-b20170303
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- (3:633/280)

Re: areafix bug?
By: Stephen Walsh to All on Mon Apr 13 2020 18:35:39

I've just had a new node do a areafix request and the body of the
netmail just has

%+ALL

that must be tom's new node, eh? i don't have an answer for the problem... only
dropping a line to note that i've been helping him get his FTN stuff going and he/we were wondering why there hadn't been a response to his areafix request at
the time it was sent... delayed processing maybe? no matter, really... just curious ;)


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello mark!

13 Apr 20 06:45, you wrote to me:

I've just had a new node do a areafix request and the body of the
netmail just has

%+ALL

that must be tom's new node, eh? i don't have an answer for the
problem... only dropping a line to note that i've been helping him get
his FTN stuff going and he/we were wondering why there hadn't been a response to his areafix request at the time it was sent... delayed processing maybe? no matter, really... just curious ;)

The mail hub system process mail just a few seconds after it's dropped off. I have done a test from my bbs
system, and it receives the message about not fiding +ALL as well, so it's not Tom's system at fault.

This issue wasn't present in versions before 1.0.7.13, as I've had nodes use the %+ALL before.



Stephen


--- GoldED+/LNX 1.1.5-b20170303
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- (3:633/280)

Re: areafix bug?
By: Stephen Walsh to mark lewis on Mon Apr 13 2020 21:46:31

that must be tom's new node, eh? i don't have an answer for the
problem... only dropping a line to note that i've been helping him get
his FTN stuff going and he/we were wondering why there hadn't been a response to his areafix request at the time it was sent... delayed processing maybe? no matter, really... just curious ;)

The mail hub system process mail just a few seconds after it's
dropped off.

cool... i wasn't sure... some systems (still) use scheduled processing instead of instant...

I have done a test from my bbs system, and it receives the message
about not fiding +ALL as well, so it's not Tom's system at fault.

ok... i know we found some few problems here and there with his mailer setup that we got fixed... missing directories here and there and a few other things... we got that all fixed and we were able to test direct netmail between
our systems... had tried before but scott's system bounced my routed reply because tom wasn't in the nodelist yet... that should be a non-problem pretty soon, i guess ;)

this issue wasn't present in versions before 1.0.7.13, as I've had
nodes use the %+ALL before.

yeah, sounds like a bug in recent versions... i saw vince posted about another bug, too... but anyway, hope you guys find and kill this bug pretty easily :)


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello Stephen,

On Mon Apr 13 2020 18:35:38, Stephen Walsh wrote to All:

I've just had a new node do a areafix request and the body of the
netmail just has

%+ALL

in it, and the system reports that:

Here is the result of your Areamgr request:

* Area %ALL not found.

Reading the helpfile a "%+ALL" should work.

Recomendations?

Have him try %+ALL instead of %ALL. ;)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello mark!

13 Apr 20 08:40, you wrote to me:

The mail hub system process mail just a few seconds after it's
dropped off.

cool... i wasn't sure... some systems (still) use scheduled processing instead of instant...

The hub system runs as a vps on my server in a datacentre, so has plenty of bandwidth and cpu power to do
processing right away. #_)

I have done a test from my bbs system, and it receives the
message about not fiding +ALL as well, so it's not Tom's system
at fault.

ok... i know we found some few problems here and there with his mailer setup that we got fixed... missing directories here and there and a
few other things... we got that all fixed and we were able to test
direct netmail between our systems... had tried before but scott's
system bounced my routed reply because tom wasn't in the nodelist
yet... that should be a non-problem pretty soon, i guess ;)

It's taken Tom (you) untill the easter weekend to get things working. I was waiting for him to get inbound binkp
sessions going before submitting the new net segment. That only happended on sunday.

this issue wasn't present in versions before 1.0.7.13, as I've
had nodes use the %+ALL before.

yeah, sounds like a bug in recent versions... i saw vince posted about another bug, too... but anyway, hope you guys find and kill this bug pretty easily :)

So do I, as a lot of new nodes use that when siging up. #-)






Stephen


--- GoldED+/LNX 1.1.5-b20170303
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- (3:633/280)

Hello Nicholas!

13 Apr 20 16:52, you wrote to me:

I've just had a new node do a areafix request and the body of the
netmail just has

%+ALL

in it, and the system reports that:

Here is the result of your Areamgr request:

* Area %ALL not found.

Reading the helpfile a "%+ALL" should work.

Recomendations?

Have him try %+ALL instead of %ALL. ;)

%+ALL was used, and I can confirm that as well as I used the same from my Mystic bbs system.
It's just that mbse is reporting back the %ALL as not found. (I've not edited the areamanger response files)





Stephen


--- GoldED+/LNX 1.1.5-b20170303
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- (3:633/280)

Hello Stephen!

Monday April 13 2020 18:35, you wrote to All:

Hello everybody!

I've just had a new node do a areafix request and the body of the
netmail just has

%+ALL

in it, and the system reports that:

Here is the result of your Areamgr request:

* Area %ALL not found.

Reading the helpfile a "%+ALL" should work.

Recomendations?

From share/int/macro/en/areamgr.help

-!-
In the body of the message to AreaMgr:

+<areaname> To connect to an echomail area
-<areaname> To disconnect from an echomail area
%+ALL To connect to all echomail areas
%-ALL To disconnect from all echomail areas
%+<group> To connect all echomail areas of a group
%-<group> To disconnect from all echomail areas of a group
%HELP To request this help message
%LIST To request a list of echomail areas available to you
%QUERY To request a list of echomail areas for which you are active %UNLINKED To request a list of echomail areas available to you
to which you are not already connected
%FLOW To request a flow report of available areas
%STATUS To request a status report for your system
%PAUSE To temporary disconnect from the connected echomail areas %RESUME To reconnect the temporary disconnected echomail areas %PWD=newpwd To set a new AreaMgr and FileMgr password
%MSGS <n> To set max. number of messages to be rescanned
%RESCAN <area> To request messages from 'area' again
%NOTIFY=On/Off To switch the notify function on or off
[---] Everything below the tearline is ignored
-!-

So the line
%+ALL

Should work - what do you have in log/manager.log for the date time of his request?


Out of interest has any one else had the same problems that I am suffering from
when compiler mbse in that there are loads of warnings being issued during the compile - see my previous post.



Vincent

--- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello Vincent!

14 Apr 20 13:58, you wrote to me:

I've just had a new node do a areafix request and the body of the
netmail just has

%+ALL
Reading the helpfile a "%+ALL" should work.

From share/int/macro/en/areamgr.help

-!-
In the body of the message to AreaMgr:

+<areaname> To connect to an echomail area
-<areaname> To disconnect from an echomail area
%+ALL To connect to all echomail areas

My areamgr.help is the same.

Should work - what do you have in log/manager.log for the date time
of his request?

Not a lot to go on. #-(
The "%+ALL" in the netmail didn't get a response, and the "+FRED" was not found as it should be...


+ 13-Apr-2020 09:43:00 mbfido[10951] AreaMgr request from Tom Aberdeen of 3:633/416@fidonet start
+ 13-Apr-2020 09:43:00 mbfido[10951] AreaMgr: Connect group ALL
+ 13-Apr-2020 09:43:00 mbfido[10951] AreaMgr request from Tom Aberdeen of 3:633/416@fidonet finished

+ 15-Apr-2020 09:50:29 mbfido[25234] AreaMgr request from Stephen Walsh of 3:633/281@fidonet start
+ 15-Apr-2020 09:50:29 mbfido[25234] AreaMgr: Connect group ALL
+ 15-Apr-2020 09:50:29 mbfido[25234] AreaMgr request from Stephen Walsh of 3:633/281@fidonet finished

+ 15-Apr-2020 09:59:30 mbfido[25324] AreaMgr request from Stephen Walsh of 3:633/281@fidonet start
+ 15-Apr-2020 09:59:30 mbfido[25324] AreaMgr: Connect group ALL
+ 15-Apr-2020 09:59:30 mbfido[25324] AreaMgr: connect "+FRED"
+ 15-Apr-2020 09:59:30 mbfido[25324] Area FRED not found
+ 15-Apr-2020 09:59:30 mbfido[25324] AreaMgr request from Stephen Walsh of 3:633/281@fidonet finished





Stephen


--- GoldED+/LNX 1.1.5-b20170303
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- (3:633/280)

Hello Stephen!

Wednesday April 15 2020 10:48, you wrote to me:

%+ALL
Reading the helpfile a "%+ALL" should work.

From share/int/macro/en/areamgr.help

-!-
In the body of the message to AreaMgr:

+<areaname> To connect to an echomail area
-<areaname> To disconnect from an echomail area
%+ALL To connect to all echomail areas

My areamgr.help is the same.

Should work - what do you have in log/manager.log for the date
time of his request?

Not a lot to go on. #-(
The "%+ALL" in the netmail didn't get a response, and the "+FRED" was
not found as it should be...

+ 13-Apr-2020 09:43:00 mbfido[10951] AreaMgr request from Tom Aberdeen
of
3:633/416@fidonet start
+ 13-Apr-2020 09:43:00 mbfido[10951] AreaMgr: Connect group ALL
+ 13-Apr-2020 09:43:00 mbfido[10951] AreaMgr request from Tom Aberdeen
of
3:633/416@fidonet finished

+ 15-Apr-2020 09:50:29 mbfido[25234] AreaMgr request from Stephen
Walsh of
3:633/281@fidonet start
+ 15-Apr-2020 09:50:29 mbfido[25234] AreaMgr: Connect group ALL
+ 15-Apr-2020 09:50:29 mbfido[25234] AreaMgr request from Stephen
Walsh of
3:633/281@fidonet finished

+ 15-Apr-2020 09:59:30 mbfido[25324] AreaMgr request from Stephen
Walsh of
3:633/281@fidonet start
+ 15-Apr-2020 09:59:30 mbfido[25324] AreaMgr: Connect group ALL
+ 15-Apr-2020 09:59:30 mbfido[25324] AreaMgr: connect "+FRED"
+ 15-Apr-2020 09:59:30 mbfido[25324] Area FRED not found
+ 15-Apr-2020 09:59:30 mbfido[25324] AreaMgr request from Stephen
Walsh of
3:633/281@fidonet finished

It is reporting 'ALL' and as a group that does not look right as it should be seeing '%+ALL' which is hardly the same.

At the moment I cannot test this without screwing up existing settings.

Will try and take a look later in the week.

Vincent

--- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)