api: It kind of sucks.

[Yawning]

mailproxy was written to be a standalone daemon above anything else, and it shows. The API could be made a lot better by exposing more control and information such as:

• Information about the connection status.
• Information about the send queue.
• Control over the send queue.
• The ability to dynamically configure accounts (#21).

I see this effort as being an on going task based on feedback from consumers of the API, and it would be nice if people that aren't me tackled this along with #4.

[Valodim]

I can make use of almost any event that happens:

• connection successful
• connection error (io / login / provider not found)
• successful message delivery (do we have that? we do have reliability things, right?)

[Yawning]

Ok. I went and added events for:

• Send completion.
• Send failures (though the default timeout is 5 days)
• Failure to create a connection
• A existing connection being torn down

The one area lacking event reporting is failure to fetch the PKI directly from the authority (though you'll get an event saying that the connection attempt has failed due to the lack of a document/descriptor after a while). There should be events for PKI fetch failures, but the way the code is structured makes this somewhat annoying to implement, so I'm punting on this for now.

[david415]

I do not get the Send completion event: https://github.com/katzenpost/tools/blob/add_zcash_wallet_proxy.0/loopix_ping/main.go

Also it doesn't shutdown but instead hangs... but maybe that's because I've got a mistake somewhere.