On 2024/07/07 16:55, Qingyao Sun wrote: > 1. make sendbug(1) block on smtpd(8) until the mail goes through, and > then print > a URL of the message on > https://marc.info/?l=openbsd-bugs&m=XXXXXXXXXX as a > confirmation.
sendbug *does* block until your local mail system accepts the message, if that system is not working there's not too much sendbug can do. Waiting for the message to show up on marc.info is not sanely possible. Apart from anything else, what happens if the mailing list is down, if the 3rd party list archive is down or updating slowly, if your internet connection is broken, etc - should it just sit there retrying until you hit ^C? Normal use of sendbug requires working email setup on the machine where you run it. If mail(1) doesn't work, sendbug(1) won't work either. If you don't have a working email setup on your machine, run sendbug -P redirected to a file, move that file to a machine with working email, and send via a standard mail client. > 2. move the temporary problem reports to /tmp/sendbug/p.XXXXXXXXXX and > never delete > anything in /tmp/sendbug. In this case smtpd(8) could still sliently > fail, but > at least we keep a copy of the message available (until reboot). It might possibly make sense to have a way to prevent sendbug deleting its tmpfile, but /tmp is cleaned automatically in various circumstances so that might not help you. Best save a copy from your editor if you want to keep it, really.
