• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Issue mail stuck in waitlist mails

qfactory

New Pleskian
Server operating system version
AlmaLinux 8.8
Plesk version and microupdate number
Plesk Obsidian v18.0.53
Hi, i have an issue, all of my mails send stay stuck in waitlist, i have try to change my DNS but nothing, i try to change the SMTP connexion but nothing too. The mail is send from the prestashop website, i have only one website, juste the prestashop, in logs i have nothing too :/

An idea for this issue?
 
Could you take one mail from the mail queue and try to find its log entries in /var/log/maillog, please? What do the log entries say? There must be some, else the mail could not wait in the queue.
 
the maillog
Aug 2 13:33:47 www postfix/smtpd[761890]: connect from localhost[127.0.0.1]
Aug 2 13:33:47 www postfix/smtpd[761890]: 833693740273: client=localhost[127.0.0.1]
Aug 2 13:33:47 www postfix/smtpd[761890]: disconnect from localhost[127.0.0.1] helo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Aug 2 13:33:47 www postfix/pickup[758374]: 85B6D3740781: uid=10000 from=<[email protected]>
Aug 2 13:33:47 www postfix/cleanup[761892]: 85B6D3740781: message-id=<[email protected]>
Aug 2 13:33:47 www postfix/qmgr[1995]: 85B6D3740781: from=<[email protected]>, size=706, nrcpt=1 (queue active)
Aug 2 13:33:50 www plesk_saslauthd[627322]: select timeout, exiting
Aug 2 13:34:17 www postfix/smtp[758752]: connect to mx0.mail.ovh.net[178.33.252.245]:25: Connection timed out
Aug 2 13:34:47 www postfix/smtp[758752]: connect to mx1.mail.ovh.net[188.165.36.237]:25: Connection timed out
Aug 2 13:35:17 www postfix/smtp[758752]: connect to mx2.mail.ovh.net[87.98.160.167]:25: Connection timed out
Aug 2 13:35:47 www postfix/smtp[758752]: connect to mx3.mail.ovh.net[91.121.53.175]:25: Connection timed out
 
Is port 25 open on your server and in the firewall of your data center? As far as I know, OVH may need an extra setting in your data center backend to open port 25. If that is not opened, mails cannot be sent.
 
Hm.. ok thanks, i have open the port in my server, but nothing again, after a nmap scan, the port is filtered so i have send a ticket to OVH for open the port, i don't have any option in my backoffice for open the port on my dedicated :/
 
Even if you have the option, All cloud service providers block all sending ports by default to protect thire IP Pools from possible abuse from any customer. you must request them to open it, they may possibly request you to attach your server IP with rDNS/TXT record to your domain name to detect email abuse.
 
Back
Top