• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

Emails not being delivered!!!

T

tutt

Guest
The email system on my Plesk 8.0 (CentOS 4) server seemed to work fine until it went live. No emails seem to get lost in space. Nothing shows up in the spool files at /var/qmail/mailnames/xxx.com/user/Maildir/new, and this is what I see in the mail log when trying to send an email from a remote server:

Jun 21 02:18:00 dedicated relaylock: /var/qmail/bin/relaylock: mail from 64.191.93.88:44218 (64-191-93-88.hostnoc.net)
Jun 21 02:18:00 dedicated relaylock: /var/qmail/bin/relaylock: mail from 64.191.93.88:44263 (64-191-93-88.hostnoc.net)
Jun 21 02:18:00 dedicated relaylock: /var/qmail/bin/relaylock: Unable to connect to the mysql database, relay will work in closed mode & white list will not work
Jun 21 02:18:00 dedicated relaylock: /var/qmail/bin/relaylock: mail from 64.191.93.88:44236 (64-191-93-88.hostnoc.net)
Jun 21 02:18:00 dedicated relaylock: /var/qmail/bin/relaylock: mail from 64.191.93.88:44225 (64-191-93-88.hostnoc.net)
Jun 21 02:18:00 dedicated relaylock: /var/qmail/bin/relaylock: mail from 64.191.93.88:44227 (64-191-93-88.hostnoc.net)
Jun 21 02:18:01 dedicated relaylock: /var/qmail/bin/relaylock: mail from 64.191.93.88:44259 (64-191-93-88.hostnoc.net)
Jun 21 02:18:01 dedicated relaylock: /var/qmail/bin/relaylock: Unable to connect to the mysql database, relay will work in closed mode & white list will not work
Jun 21 02:18:01 dedicated relaylock: /var/qmail/bin/relaylock: mail from 64.191.93.88:44226 (64-191-93-88.hostnoc.net)
 
Wasn't using SPF and it was not happening on the other domain on the server. I did get it fixed. I removed the listing of the particular domain from some file in /var/qmail/control where the other (working) domain did not appear. This I believe fixed the problem. I do not remember which file it was exactly.
 
You must log in or register to reply here.

Similar threads

M
Issue Postfix - warning: connect to transport private/plesk-domain.org.uk-123.145.167.189-: Connection refused
Replies
8
Views
7K
MHC_1
M
J
Resolved MSMTP - 554 error from Ionos
Replies
2
Views
2K
jrolland
J
W
Issue Mail forwarded on the server in the target mailbox is delivered to the SPAM folder
Replies
0
Views
4K
W4ru
W
mapodec
Resolved Emails sent from Plesk accounts are not delivering only to Google Workspace
Replies
2
Views
4K
mapodec
mapodec
EnriqueR
Question Incoming mail is stored in Junk folder
Replies
6
Views
7K
EnriqueR
EnriqueR
Back
Top