You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we have a MX loop where we send to ourselves using MTA AND we bounce AND the bounce is to be sent to ourselves (using MTA), we detect the loop, we detect the bounce loop and runner seems to abort but we have an envelope in queue that is to be delivered to MTA and that never has its retry count and last try date set (which makes it immediately reschedulable).
I don't know what causes that yet but as soon as we have retry count and last try date set, the spinning should disappear.
Runner process spinning observed on poolp.org secondary MX
It seems to be related to a missing rule to match local domain, causing local mail to be sent using MTA.
needs to be investigated
The text was updated successfully, but these errors were encountered: