Oct
12
2026
Outbound connection tracking
- Failed outbound connection attempts are now tracked per session partner, including the number of retries and the latest error
- If an outbound connection could not be established for 5 minutes, a system event is triggered and a notification is sent (mail or webhook, depending on the notification settings). If the problem persists, the notification is repeated every 24 hours
- Every waiting transmission and every waiting EERP/NERP gets a log entry when its outbound connection fails and when the connection is up again, including the downtime and the number of retries. This makes it possible to see whether a delayed transmission or EERP was caused by an unreachable partner system
- The cipher suites 8, 9 and 10 (SFIDCIPH_AES256CBC_RSA_OAEP_PSS_SHA256, SFIDCIPH_AES256CBC_RSA_OAEP_PSS_SHA512, SFIDCIPH_AES256CBC_RSA_OAEP_PSS_SHA3_512) could not be assigned to a partner, the partner configuration rejected them with "unsupported cipher suite"
- Linux/Mac OS: The script oftp2_send.sh passed the third parameter twice and used an incomplete classpath
- OFTP2 Client: In the system event dialog, changing a filter (for example the category) sometimes did not display the search result, the search had to be started again manually
- OFTP2 Client: Images in balloon tooltips were not scaled
- OFTP2 Client: Images in the partner graph were blurry when display scaling was active