Hello,
in general a busy/full mail queue won't be a reason for delayed responces on TCP level, there is also a protection mechanism in place (resource conservation) that kicks in when the system runs out of resources due high traffic. Of course, on higher levels than TCP delays may occur because i.e. the appliance is waiting for a response from Senderbase, DNS, or LDAP. But back to your problem, those errors often indicate problems on routing, quoting a submission from another forum here:
"The most common cause of the problem? Asymmetric routing or using firewall pairs and not sharing TCP state information between them.
When you have asymmetric routing the data might be going via the path sender -> router 1 -> router 2 -> receiver in one way but the return path is receiver -> firewall -> router 1 -> sender. In this scenario the firewall is not seeing the TCP session establish properly as its missing all the traffic from the sender to the receiver so it will always drop it as "out of state". "
Are you using a Checkpoint firewall BTW? Because it seems most of these errors reported relate to stateful inspection.
Regards,
Andreas
