Open tsilia opened 3 years ago
You are right, I will address the issue in the future.
In this sense I wonder what's the design decision behind catching asio (ssl) errors and rethrow them as mailio errors? Because asio is such a vital core part of the communication layer, we definitely need the underlying communication error.
I personally would let asio errors through to the caller, as they are std::system_error
s these days anyway.
It was meant to move them away as low level errors. But from your and some other comments, I see there is a need to trace these errors as well the errors received from servers. Thus, I plan to extend the mailio exceptions with these additional data. In this version I am dealing with the various encoding issues, so probably I'll let the error handling for the next version.
After 2 and half years this still is very much wanted.
Thanks for pushing this. There is an ongoing refactoring on the codec_folding branch regarding the header folding and policy. Once I finish it (hopefully in the following weeks), the version 0.24 will be concluded. Then I can address this one and few more topics, some of them are already in PRs. So, I put the label Enhancement, so I could prioritize it for the version 0.25. Thank you for the patience.
Hello. Exceptions in
mailio
often don't seem to be very informative, e.g.:throw message_error("Parsing failure of the message ID.");
orthrow pop3_error("Parser failure.");
which unfortunately don't say much about the value that caused this exception or the reason.Perhaps you could somehow extend exception interfaces to allow saving and retrieving additional info which could be the exact value that failed to parse or at least some context that could help to track down the issue if the exact value isn't available at the time when exception is thrown? It probably would be better if there was another parameter for
message_error
(and the likes) constructor, likeconst std::string& token
orconst std::string& context
which could also be retrieved in exception handler using a corresponding method, likeget_error_token()
orget_context()
. This way it doesn't break anything for anyone because all who wants to have nice and clean human-readable messages will still get those with no edits required on their side. It would require editing of the library code though.An example implementation:
Also, it would probably be better to store both the invalid token AND the context in which it appeared because there are cases when few
case
blocks ofswitch
produce exceptions with the same message but for different states of the parser, or the cases like this one when you throwpop3_error
and we lose the original exception reason: https://github.com/karastojko/mailio/blob/f82f7e8e0d9f1c2794a6960e409ddc4899e4881d/src/pop3.cpp#L127-L134 In such cases it probably could be better to saveex.what()
as the exception context similarly to what was described above.