Last Errors |
time | error |
2025-07-18 13:46:54 |
Timed out, status = ETIMEDOUT while connecting from api3.dizifrost.com (216.117.173.185) to mx.daily.co.uk (195.26.90.18) |
2025-07-18 13:34:54 |
Timed out, status = ETIMEDOUT while connecting from api3.dizifrost.com (216.117.173.185) to mx.daily.co.uk (195.26.90.18) |
2025-07-18 13:22:54 |
Timed out, status = ETIMEDOUT while connecting from api3.dizifrost.com (216.117.173.185) to mx.daily.co.uk (195.26.90.18) |
2025-07-18 13:10:54 |
Timed out, status = ETIMEDOUT while connecting from api3.dizifrost.com (216.117.173.185) to mx.daily.co.uk (195.26.90.18) |
2025-07-18 12:58:54 |
Timed out, status = ETIMEDOUT while connecting from api3.dizifrost.com (216.117.173.185) to mx.daily.co.uk (195.26.90.18) |
2025-07-18 12:46:54 |
Timed out, status = ETIMEDOUT while connecting from api3.dizifrost.com (216.117.173.185) to mx.daily.co.uk (195.26.90.18) |
2025-07-18 12:34:54 |
Timed out, status = ETIMEDOUT while connecting from api3.dizifrost.com (216.117.173.185) to mx.daily.co.uk (195.26.90.18) |
2025-07-18 12:31:55 |
message rate limit reached (based on VirtualMTA's or pool's max-smtp-msg-rate in configuration) |
2025-07-18 12:31:41 |
message rate limit reached (based on VirtualMTA's or pool's max-smtp-msg-rate in configuration) |
2025-07-18 12:21:41 |
Timed out, status = ETIMEDOUT while connecting from api3.dizifrost.com (216.117.173.185) to mx.daily.co.uk (195.26.90.18) |