• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Mail from Amazon SES takes a long time to be delivered

maximid

New Pleskian
Server operating system version
Debian 11.9
Plesk version and microupdate number
Plesk Obsidian Version 18.0.60
Hello,

we have problems on our Plesk server that mails from amazonses taken long to get them. For 2FA this is very bad....
I whitelisted globaly @amazonses.com and also the IP spaces from them.

Any idea what to do next?

Thanks and Regards!
 
External Domain configred, mailtester shows 10/10 and all other mails coming in instant. Yes, Spam Assassin. Using SoGo as webmail client, nothing else.
 
This there a (significant) time difference between the first related log entry in the mail log (Tools & Settings > Log Browser > Mail) and when the email appears in you mailbox? Of does the time of the first related log entry more or less corresponds to the time if the mailbox?

For example log entry in the mail log:
2024-04-19 17:14:17INFOpsa-pc-remote [28320]EC90A858F31: from=<[email protected]> to=<[email protected]>

In my mailbox:
From Kaspar <[email protected]> on 19-04-2024 17:14
 
Hi, it was greylisting. I added *@amazonses.com and all IPs to the Server-wide Whitelists.

Only after adding *.amazonses.com to the White domains pattern list via cli it was working.

Thanks for your help and have a great weekend! :)
 
Back
Top