Is the Fidonet Netmail echo suppose to be processed with the other
Fidonet echo packets or separate from it?

At one time I had it that way and my uplink said my netmail was coming
in with the regular echo packets and wasn't suppose to work like that
that they should be separate.

I was able to get ONE netmail to go out but that was only to my uplink
all the others are sitting there in the netmail conference and
netmail queue with a status of "Pending" whatever that means, if I add
the netmail echo with the other fido echos these other netmails
will go out.

Thanks for any insight.
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: TECHWARE BBS - Since 1995 - www.techware.dynip.com/ (1:102/401)

On 2018 Nov 17 19:55:26, you wrote to All:

Is the Fidonet Netmail echo suppose to be processed with the other
Fidonet echo packets or separate from it?

netmail areas are not "echos"... they are "netmail" ;)

At one time I had it that way and my uplink said my netmail was coming
in with the regular echo packets and wasn't suppose to work like that
that they should be separate.

they are incorrect... the only defining difference between echomail and netmail
is that echomail has an AREA control line in it specifying which echomail echo tag it belongs to... echomail and netmail messages can be all packed into one PKT or sent separately... the mail tosser will/should handle them as needed on the receiving end...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... A lawyer got his client a suspended sentence. He was hung.
---
* Origin: (1:3634/12.73)

On 2018 Nov 17 19:55:26, you wrote to All:

Is the Fidonet Netmail echo suppose to be processed with the other Fidonet echo packets or separate from it?

netmail areas are not "echos"... they are "netmail" ;)

At one time I had it that way and my uplink said my netmail was coming in with the regular echo packets and wasn't suppose to work like that that they should be separate.

they are incorrect... the only defining difference between echomail and

netmail

is that echomail has an AREA control line in it specifying which echomail

echo

tag it belongs to... echomail and netmail messages can be all packed into

one

PKT or sent separately... the mail tosser will/should handle them as needed

on

the receiving end...

Ok, I will try it that way let me know if you get your netmail reply
that's just been sitting there for days.

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin'

it

wrong...
... A lawyer got his client a suspended sentence. He was hung.
---
* Origin: (1:3634/12.73)

--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: TECHWARE BBS - Since 1995 - www.techware.dynip.com/ (1:102/401)

On Nov 17, 2018 08:03pm, Lee Green wrote to All:

Is the Fidonet Netmail echo suppose to be processed with the other
Fidonet echo packets or separate from it?

At one time I had it that way and my uplink said my netmail was coming
in with the regular echo packets and wasn't suppose to work like that
that they should be separate.

I was able to get ONE netmail to go out but that was only to my uplink
all the others are sitting there in the netmail conference and
netmail queue with a status of "Pending" whatever that means, if I add
the netmail echo with the other fido echos these other netmails
will go out.

They usually DO go out separate based on destination node. Could you give a little more detailed explanation as to what problem you are having? And you might also want to scan out netmail using the PXNET.EXE command like so:

PKXNET.EXE /scan /fastpack <destination address>

This will pack up your outbound netmail for <destination address> and mark it as read in Wildcat!. I have this command run in my Internet Rex BETWEEN.BAT file for each system I connect to to make sure any netmail destined for their systems is packed and ready to go on the next mail run. Als, you might want
to check and make sure your routing is set up correctly for netmail as well.

... Platinum Xpress & Wildcat!..... Nice!!!!
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: Omicron Theta (1:116/17)

On Nov 17, 2018 08:03pm, Lee Green wrote to All:

Is the Fidonet Netmail echo suppose to be processed with the other Fidonet echo packets or separate from it?

At one time I had it that way and my uplink said my netmail was coming in with the regular echo packets and wasn't suppose to work like that that they should be separate.

I was able to get ONE netmail to go out but that was only to my uplink all the others are sitting there in the netmail conference and
netmail queue with a status of "Pending" whatever that means, if I add the netmail echo with the other fido echos these other netmails
will go out.

They usually DO go out separate based on destination node. Could you give a little more detailed explanation as to what problem you are having? And you might also want to scan out netmail using the PXNET.EXE command like so:

The only netmail that goes out is when I send one to my uplink 1:218/700
all the other netmails to others just sit there, they are seen by pxnet
they just don't get put into a packet ever. I receive all INcoming
netmail fine. I believe Ruben is having the same problem.

PXNET.EXE /scan /fastpack <destination address>

That's what I use, and it runs from between.bat

This will pack up your outbound netmail for <destination address> and mark

it

as read in Wildcat!. I have this command run in my Internet Rex BETWEEN.BAT file for each system I connect to to make sure any netmail destined for

their

systems is packed and ready to go on the next mail run. Als, you might want to check and make sure your routing is set up correctly for netmail as well.

Where is routing for netmail located? I think I've checked everything
multiple times.

... Platinum Xpress & Wildcat!.... PITA !!!
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: Omicron Theta (1:116/17)

--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: TECHWARE BBS - Since 1995 - www.techware.dynip.com/ (1:102/401)