Wassilios Lytras

That can be removed, but should we then also remove the "_duplicate" from the message id on receiving duplicates? This currently prevents the integrity error for the first retry.

Any changes requested for this PR? Options are : - as per the PR, the "_duplicate" is kept in the message id and trailed by a unique value or -...

@satyen4you Please note my answer already given to you in the BOTS forum. Did you check OpenSSL if that certificate is valid there ?

To me, it seems to be a problem related to pyopenssl and your local installation. Could relate to the OpenSSL version used (I am not an SSL expert, but your...

@satyen4you : were you able to resolve this issue and can it be closed?

@satyen4you : any update?

@abhishek-ram : Would like to come back to the above. Just as a general concept: 1. Organizations will also have a second key. 2. Create a new model that links...

@abhishek-ram Partnership approach was the way I was working on and I will adjust pyas2lib. I will adjust my PR to accommodate your point: - The find_org_cb and find_partner_cb will...

Same in case of connection refuse> Failed to send message, error: Failed to send message, error: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 160, in _new_conn (self._dns_host, self.port), self.timeout,...

@avignat : I do think the error is handled correctly. if that error occurs, the message should get the status "Retry". After the retries have executed, only then it will...