• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Outgoing emails have stopped sending

M

mreine

Guest
Outgoing emails have stopped sending

When I do the following....
tail -f /usr/local/psa/var/log/smtp_pendings.log


I get this...
1218452789.277428 starting delivery 27412: msg 967230 to remote [email protected]
1218453755.085063 starting delivery 27447: msg 967230 to remote [email protected]
1218453796.167623 starting delivery 27451: msg 967230 to remote [email protected]
1218452634.112281 starting delivery 27405: msg 967230 to remote [email protected]
1218452634.081450 starting delivery 27402: msg 967230 to remote [email protected]
1218452665.521591 starting delivery 27407: msg 967230 to remote [email protected]
1218452725.722255 starting delivery 27410: msg 967230 to remote [email protected]
1218453754.899980 starting delivery 27444: msg 967230 to remote [email protected]
1218453754.900807 starting delivery 27446: msg 967230 to remote [email protected]
1218453818.444173 starting delivery 27457: msg 967230 to remote [email protected]

When I run this I get nothing in the queue
./qmhandle/qmhandle-1.3.2/qmHandle -R

I tried qmhandle -D and the smtp_pendings will not clear out.

Can anyone tell me how to clear out the outgoing smtp emails or what the above report means?
 
I left out that emails would queue up in the system, but remote emails would not leave the queue. Local emails were functioning fine to any domain within the VPS. This morning everything is working fine now. Tech support said they didn't find anything, but I think they did on their end, fixed it and aren't about to admit anything. I see nothing different in the configuration from last night when things weren't functioning. I have no explanation for what happened.
 
Back
Top