This particular DPA error is usually caused by one of two things:

1. a temporary outage of the DPD server. If multiple shipments with DPA get this same error in the same time frame then it's likely this is the cause. Waiting and retrying your booking until DPD solves the outage is the only way forward.

2. if only specific shipments with DPA get this error then it's likely that your booked receiver e-mail address contains a domain name (@xxxxx) that DPD does not recognise as valid. We have no control over what DPD considers a valid e-mail domain so please contact your DPD account manager if you believe this to be the cause. 

The carrier has promised us to improve this error logging thoroughly sometime in Q3 2024.

The full booking error is shown below:

Shipment submit failure: Shipment booking failed. Internal service call failed. Bad Request: An internal server error occurred, - I/O error: Read timed out; nested exception is java.net.SocketTimeoutException: Read timed outShipment submit failure: Shipment booking failed. Internal service call failed. Bad Request: An internal server error occurred, - I/O error: Read timed out; nested exception is java.net.SocketTimeoutException: Read timed out DPA DPD mail domain