23 Jan 16 20:30, you wrote to me:

 RM>>> It seems that the Flag does not make it to Golded.
 ml>> not sure what you mean by this "does not make it to golded"
 ml>> statement...

 RM> Golded can answer RRq messags itself.
 RM> See below template.

you've mixed up the RRQ and the CFM flags 

RRQ is responded to by the tosser/mailer (if the mailer unpacks the netmail
from the PKTs al la frontdoor)... CFM is responded to by the sysop editor or
BBS software when the destination user reads the message...

[chomp]

 ml>> then there's also the CFM flag... this one causes you reader
 ml>> software. if it is configured to honor it, to generate a receipt to
 ml>> the originator when you read the message... sysop readers and bbs
 ml>> software would be the ones to honor this flag...

 ml>> so two flags for two different receipts... one receipt for the
 ml>> netmail's arrival and unpacking and another receipt when the destinee
 ml>> reads the message... honoring either is optional...

 RM> Aaah ... OK, so RRq is answered by the tosser, CFM by the editor.

yes...

 RM> Strangely Golded also mentions RRq in the documentation ...

 RM> Thanx!

 RM> ==== Begin "golded.cfm"  ====
 RM> *** Confirmation Receipt Message ***

 RM> Hello @TFName!

 RM> This automatically generated message is a confirmation that your
 RM> message to @DName, dated @ODate @OTime, has in fact been read. If
 RM> your message requires an answer, @DFName will answer when time
 RM> permits.

 RM> Have a nice day,  @CName.

 RM> ==== End "golded.cfm" ====

that's a template for responding to the CFM flag 

)\/(ark

... Jewish Dilemma: Pork chops; half-price.
---
 * Origin:  (1:3634/12.73)