MR>> Yes, but the recommended method is: MR>> ...,IBN,INA:agency.bbs.geek.nz,...
ml> that's actually backwards and/or wasted... the INA should be listed ml> /before/ the flags that it affects... in the above, the shown IBN flag ml> is associated with the preceeding unknown portion of the entry while ml> INA is for the trailing unshown portion of the entry...
MvdV> No, it is not. FTS-5000 and FTS-5001 do not mandate any MvdV> particular order for the flags. I would have preferred the INA MvdV> flag to always be before the protocol flags. That way a one pass MvdV> parser would do. Current practise however has not followed that MvdV> rule, so now nodelist parsers must find the INA flag wherever it MvdV> is.
so where does that put multiple INA entries? does the last INA apply to the entire entry or how is that supposed to work?
)\/(ark
If you think it's expensive to hire a professional to do the job, wait until you hire an amateur.
