BL> Put Netmail first in your tenmin.tbl like this, and you can't go
BL> wrong.

FM> Actually, I don't understand why I should put Netmail first anyway!
FM> (It's always been first, BTW - that's how it came from Brenton.)

It was once required in an earlier version of PQWK, no longer needed.
I dont have it first and my areafixes work fine, other netmail too.

FM> It seems to me I just have to address it to the right conference.

Yep.

FM> There's no way something can *know* a message is netmail and
FM> send it to the right conference - you have to put it there.

I think you are getting caught by the QWK reader getting a bit tricky
about trying to keep track of your echomail areas between QWKs. Some
try to keep that data themselves and that means that they can get
seriously confused if you are massaging your CONTROL.DAT and TENMIN.TBL
tables. The reason they do that it is to allow you to enter a new
message when you dont have a QWK open, so they need some record of
areas.

I would carefully check you have your CONTROL.DAT and/or TENMIN.TBL
ok and then deal with a new set of PKTs, producing a new QWK. Actually
check the area list with that QWK open and see that your areas are right
in the OLX display. Depending on how you use QWK, you dont necessarily
need to have both the CONTROL.DAT and TENMIN.TBL

You can also read the created PKTs with a file viewer to see what its
done with the areas when its been created from a QWK.

AND BlueRipple keeps the BBS status on areas in QWKs differently to how
OLX does too, just to add another level of confusion.

--- PQWK202