Hello Tom!

22 May 23, Tom De Puysseleyr wrote to All:

 TP> problem for dupe checking, since husky starts with an empty dupe
 TP> history file. Is there a way to generate this dupe history from the
 TP> existing messagebases?

I think so. For the same reason why there is no need for a messagebase format converter. hpt does generate the dupe database for inbound pkt, just use it.

The magic word for system migration is PKT.

Setup the new husky system as a migration point number of your fmail node.
Link all echos to the point number.
Do a rescan from node to point AKA.

Your messagebase should be exported to pkt, including path and seen-by information. Because points are a part of your node they will not appear in the SEEN+BY lines.

When done and all messages are tossed over to the migration point then remove the point number from the husky config and your migration point AKA will become your node AKA. And your new husky node does have an actual dupe database.

For failsafe reason backup/clear your new nodes outbound, do a hpt scan to all echos and check for dupes in your outbound.

Regards

Kai

--- GoldED+/LNX 1.1.4.7