We have a person from outside our organization who deos most of the posting
to one of our lists in particular by Cc'ing it to use when he sends it out
to several others. It's a document that comes out weekly or so. We have
need to make this process as convenient for this person as possible (i.e.
I don't want to even ask the person to stick an Approved: password header
in the message going out).
My question is this: We receieved a new ``issue'' of this document just
now. It was returned to the sender as BOUNCED: Need Approval and was sent
to me (the list owner) as well. I used MH's ``forw'' command and resent
it to the list with an Approved: password header. Is there any cleaner
way to do aall of this? Subscription requests which need approval are
trivial because the list owner is told exactly what to do, etc, whereas
posting approval is basically "OK, here, someone sent this to the list and
I bounced it back to them. Do something with it."
I'd really like to not be bouncing things back to this person as well --
it causes extra work onhis part and he's doing us a favor.
-------
Jeff Blaine
CIESIN Operations
|
|
