Eric,

Thursday July 23 2015 17:44, you wrote to All:

 ER> Another strange an unusual question.. This one's regarding HPT.

 ER> Synchronet's sbbsecho currently directly takes NetMail PKT's and
 ER> directly imports them to it's SMB message base. Getting that changed
 ER> is going to take pulling teeth, likely, but here's my goal:

 ER> If I must, I want to use HPT to essentially PRE-process PKT's for
 ER> netmail, ignoring anything for EchoMail, Areafix, etc., just to get
 ER> NetMails out and exported to *.msg messages so that all inbound
 ER> messages destined to any of my AKA's can be saved. After that, THEN
 ER> run sbbsecho on the same, untouched/unmangled/unmodified pkt's to
 ER> handle importing, and areafix, etc..

 ER> I only care about netmail bundles and nothing else, because sbbsecho
 ER> itself will handle all the echomail as appropriate.

 ER> Anyone have any thoughts, ideas of how to accomplish this?

I see a few possible ways:

1. Configure two nodes (requires two node numbers):  Node A - HPT, node B -
Synchronet.  The HPT 'node' A is configured as intermediate system with all
areas set to autoadd passive node B.  Perl filters can be used to sideline
any netmail to your name and move to area regardless of node number found. 
If $kill=1 is set, the message will never be send to downstream synchronet
system even if destined to its node number!  HPT can be configured to pack
to fileboxes (always) and you simply move 'outbound' bundles from HPT into
Synchronet's inbound.   Going from synchronet (which uses bso - if i
recall) will be a tad bit of work but easy since you have just one link in
config.
Caveat: Requires a fairly full hpt configuration.  Will take time.

2. Configure hpt to toss same mail bundles as synchronet.   I suspect if
HPT configured with no badarea echoes are throught into bit bucket.  If
this does not work, few lines of perl code could be crafted to 'kill' all
echomail messages.
Caveat: Requires a lighter hpt configuration.

3. I seen post about netmgr.  I ran that years ago.  I do not recall if it
can handle inbound netmail but I know it had outbound routing capabilities.
 I recall it took a little time to configure (order of operation).

I believe some of these suggestions overlap that made by others except
perhaps in impementation.  I could help a bit with perl script but time is
limited.  :-)

Take care,

Matt

---