• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Duplicate email messages from cloud-based email sending services

Shanti

New Pleskian
Server operating system version
AlmaLinux 9.8
Plesk version and microupdate number
Plesk Obsidian v18.0.80_build1800260909.19 os_RedHat el9
Hi!
I have system-wide problem where all email users get some multiple (from 2-3 to 11) duplicate email messages. I have noticed that these are almost always from cloud-based email sending services like Amazon AWS SES or Postmark. So the recipient gets multiple message whereas the service (I also use Postmark) sees these with status Undeliverable.

I have tried with or without Plesk Email Security. Also my Grey listing checking is currently disabled. What could it be?

This is log excerpt from one such occasion:
| 2026-09-13 10:52:36 | postfix/qmgr [1332] | 96C189614A6: removed
| 2026-09-13 10:52:36 | postfix/pipe [1759012] | 96C189614A6: to=<[email protected]>, relay=plesk_virtual, delay=266, delays=132/0.01/0/134, dsn=2.0.0, status=sent (delivered via plesk_virtual service)
| 2026-09-13 10:52:36 | postfix-local [1759013] | 96C189614A6: arc-sign: stderr: PASS
| 2026-09-13 10:52:35 | postfix-local [1759013] | 96C189614A6: spam: stderr: PASS
| 2026-09-13 10:52:33 | postfix-local [1759013] | 96C189614A6: dmarc: stderr: PASS
| 2026-09-13 10:52:33 | postfix-local [1759013] | 96C189614A6: dk_check: stderr: PASS
| 2026-09-13 10:50:22 | postfix-local [1759013] | 96C189614A6: from=<010201a09a61b60d-39cddabc-25cd-4202-a8ab-2ad0ec126561-000000@awsses.3djake.com>, to=<[email protected]>, dirname=/var/qmail/mailnames
| 2026-09-13 10:50:22 | postfix/qmgr [1332] | 96C189614A6: from=<010201a09a61b60d-39cddabc-25cd-4202-a8ab-2ad0ec126561-000000@awsses.3djake.com>, size=120095, nrcpt=1 (queue active)
| 2026-09-13 10:50:22 | psa-pc-remote [822] | 96C189614A6: spf: stderr: PASS
| 2026-09-13 10:48:10 | psa-pc-remote [822] | 96C189614A6: check-quota: stderr: SKIP
| 2026-09-13 10:48:10 | psa-pc-remote [822] | 96C189614A6: py-limit-out: stderr: SKIP
| 2026-09-13 10:48:10 | psa-pc-remote [822] | 96C189614A6: py-limit-out: stderr: INFO:__main__:No SMTP AUTH and not running in sendmail context (incoming or unrestricted outgoing mail). SKIP message.
| 2026-09-13 10:48:10 | postfix/cleanup [1758816] | 96C189614A6: message-id=<010201a09a61b60d-39cddabc-25cd-4202-a8ab-2ad0ec126561-000000@eu-west-1.amazonses.com>
| 2026-09-13 10:48:10 | psa-pc-remote [822] | 96C189614A6: from=<010201a09a61b60d-39cddabc-25cd-4202-a8ab-2ad0ec126561-000000@awsses.3djake.com> to=<[email protected]>
| 2026-09-13 10:48:10 | postfix/smtpd [1758809] | 96C189614A6: client=a6-158.smtp-out.eu-west-1.amazonses.com[54.240.6.158]
 
Yes, there are same Message-ID for separate delivery entries (where mail_id: and Queue-ID: will be different).
 
Thanks for the confirmation. I suspect that the issue you are experiencing could be related to a known bug (PPPM-8012), but I will need you to check a few additional details, please. Kindly look at the /etc/resolv.conf file on your server and test whether outgoing connection to port TCP 53 is possible for all DNS servers configured:

Code:
telnet <DNS_SERVER> 53

If the connection is timing out, then the issue is caused because of the bug and suggested workaround until the same is fixed is allowing outgoing requests to port 53 (TCP and UDP) for all configured nameservers.
 
Hi @Sebahat.hadzhi,

the result of my resolv.cnf:
Code:
# cat /etc/resolv.conf
; Created by cloud-init automatically, do not edit.
;
search localhost
nameserver 153.92.2.6
nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 8.8.4.4
nameserver 1.0.0.1

So, yes, for the first entry I just get Trying 153.92.2.6... for others it appears it can connect:
Code:
% telnet 1.0.0.1 53
Trying 1.0.0.1...
Connected to one.one.one.one.
Escape character is '^]'.
Connection closed by foreign host.

So the first entry is from Hostinger, which is not under my control. So is it safe that I just comment that entry and leave all the rest entries as is?
 
Yes, please. As a temporary troubleshooting step, try commenting it out and monitor if the issue continues.
 
Back
Top