Hello Richard


 >>> [..] it would appear to me that one using netmgr's bounce
 >>> function could conceivably fly this flag.  Am I mistaken?
 ac>>> This seems to work for me:
 RW>> Thanks, had the mask figured, just didn't know if enough header info
 RW>> was shown to legally fly ping flag.
 MK>> I tried it, but miss reflecting the via-lines (as described in the
 MK>> nodelist).

 RW> Hmmm, hadn't actually tried it.  I might get a couple of folks to
 RW> send routed netmails to ping at my address and see what they get
 RW> back.

At the time i send out three 'ping'. I get back my mail (bounce-function),
but only one with via-lines (done by I/O-Track). The fourth is on way to
you.

 RW> IF it meets specs then I"ll change my listing. iF not, oh well
.

I think i will list a PING-flag on the coordinator line.

It is already testable writing to 'ping' at 2:2468/1.

===
xMask
 to         "PING" or "Ping" or "ping"
 dest       2:2468/1.0
 attr       +p-r
End
Action  display -- PING to NC ->
Action  file d:\log\pinging.log
Action  xbounce d:\mbox\nmr\ping.txt NC2468, *, *, *, *, +l+p
Action  rewrite *, *, *, *, *, -l+r
Action  move e:\mb\msg\rob
=== end ===

Some notes:
- xmask-to: NetMgr is case sensitive
- action-display: for better human look in log
- action-file: for logging incoming 'ping' mail (only for test time)
- action-xbounce: use x-function for rewrite send name
- action-rewrite/move: save mail to my robot mail area


Micha

--- FMailX 1.48b