> -- When something went wrong during 'sending' from acme Mail, I did not > get any information that the mail had not been sent.
acme/mail sends by handing messages to upas/marshal, and doesn't check for return status. The assumption is probably that if marshal fails, you'll see its sysfatal message in an acme error window, and once marshal has handed the message to upas/send it will either be successfully delivered or you'll get an asynchronous bounce message back by email. Just last week I hit a case where that assumption wasn't true. My file system became full, so upas/send couldn't queue the message. Sadly it couldn't send a bounce message back either, because ... the file system was full. Even more sadly, I missed the "file system full" message, because my terminal didn't have a console window for the cpu server open.
