imaps
2 TopicsIMAP-S External Health monitor
Here an external health monitor to check IMAPS service. My F5 version is 17.1.1. Working successfully. #!/bin/bash # IMAP Health Check for F5 with IPv4-only adjustment HOST=$(echo $1 | sed 's/::ffff://') # Force IPv4 format PORT=993 # Capture response with error handling response=$(echo -e "A1 CAPABILITY\nA1 LOGOUT" | /usr/bin/openssl s_client -connect "$HOST:$PORT" -crlf -ign_eof 2>&1) # Log for debugging and check for a successful IMAP response echo "Debug: OpenSSL response for $HOST: $response" | logger -p local0.notice -t IMAPMonitor if echo "$response" | grep -q "OK"; then echo "UP" exit 0 else echo "DOWN" exit 1 fi18Views0likes1CommentLogging IMAPS payload with SSL::collect doesn't work, any solution?
Hi, We have a Big-IP 13.x acting as an IMAPS SSL-offloading front-end for our IMAP backend servers. The problem is the backends don't see the real source IP. I want to log the client IP and imap login username on the Big-IP. Therefore I will have to search the decrypted payload, which is normally no problem. However, when I use SSL::collect my connection stalls. This seems to be the cause of my problem: https://support.f5.com/csp/article/K12646 Basically, when I start collecting, the serverside connection is not created until the client sends something. But the client is waiting on the server to start the conversation. Has anybody been able to work around this? Or simply put: has anybody been able to log imaps logins? Kind regards Vincent382Views0likes1Comment