Correction handling

[Ken Olum <kdo cosmos phy tufts edu>]

Hmm, not everything is perfect about correction handling.  In the public
message:

   From: bapc submit gmail com
   Date: Wed, 17 Jun 2026 11:04:43 -0700
   To: bapc-future cosmos phy tufts edu

   The following BAPC event has been corrected:

   BAPC ID: BAPC-mq88rhwu-fc1l

Should this be here?  I'd think the ID should go only to the submitter.

   The regular weekly BAPC digest schedule is unchanged.

I'm not sure the meaning of this.  Does it mean, "Even though we sent you
this correction email at with some random time, we're still going to send
out digests on Thursdays as usual"?  Or something else?  Maybe this
causes more confusion then it prevents and it would be better to leave
it out.

In the reply that I got from the system:

   From: bapc submit gmail com
   Date: Wed, 17 Jun 2026 11:04:44 -0700

   Your BAPC event BAPC-mq88rhwu-fc1l was successfully updated.

   ...

   The event will also appear in the next weekly digest.

But presumably it won't because the next digest should have only next
week's events.

Another issue is that I first gave a wrong command to my test mailing to
bapc.submit.  The result was silence.  Maybe it has sent it to you to
process. But even if so, I think every message to bapc.submit (except
bounces, I guess) should yield a response (e.g., "invalid command")
soon.  Otherwise the sender has no idea what is happening.

Thanks, Ben!

                                        Ken