Store & Forward - what are the requirements for using it?

Support
1

I ask this for the case of the S&F and client node having firmwear 2.5.7 stable and above.

  1. Does using Store & Forward require the node providing the Store & Forward (the S&F node) and the client node retrieving missed messages from that S&F node, to each have at least one same private channel set up, with full PSK, in their channel list?

  2. If yes, does the order of the channels in either the S&F node or client node matter?

  3. I do not use the new app, and use Android 2.4.4 . Does using the the newer updated app influence the answers above?

  4. Is a node database reset in both the client and S&F node essential to make the direct messages from the client, that activate the S&F node, function?

  5. Is a restart of the Meshtastic app required when adding or changing channels?

Reason for asking now: I want to know if the new public/private key system has made the need for a private channel in common obsolete, or if this is still an absolute requirement for S&F to be used.

Use case / motivation: I need to double-check. I am intending to make a private channel with full PSK, whose PSK is then shared widely in the local mesh, to make the S&F nodes of the local mesh fully accessible to the whole mesh, to those mesh users who have knowledge of the PSK via e.g. WhatsApp or Telegram groups of Mesh users, or longfast or other extant channels for the local area.

Thanks for any clarification, and sorry if I kind-of asked this before. I did not find any statement on this in the docs

and would really like some hard info for the superb Store & Forward functionality of Meshtastic.