• 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.

Qmail relaylock Problem

D

diadem.support

Guest
Hello,

We are running Plesk 8.1 on Enterprise Linux 4,4psa Spam guardian and greylist. Recently we are facing the problem that mails from "css.one.microsoft.com" are not entering our server. What we have found from the maillog entry is like:

Jul 10 18:23:56 plesk02 relaylock: /var/qmail/bin/relaylock: mail from 131.107.70.12:40066 (mail4.mssupport.microsoft.com)

We have checked that this domain is not blacklisted in the spamassassin nor we have implemented any DNS blacklisting. The /etc/xinet.d/smtp_psa in our server looks like:


service smtp
{
socket_type = stream
protocol = tcp
wait = no
disable = no
user = root
instances = UNLIMITED
server = /var/qmail/bin/tcp-env
server_args = -Rt0 /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var
/qmail/bin/cmd5checkpw /var/qmail/bin/true
}

Can anybody suggest why the IP is blocked in Relaylock or what may be the cause of this problem. We have also tried by white listing the Microsoft mail server IP from the "MAIL" section in Plesk Server tab but no result!!!

Thanks in advance

Regards,
Diadem
 
The sender of the mail will eventually get a message back stating why the mail was not delivered. Ideally you know the sender (that is, it's not an automated mail your getting) and can ask them to send you the reason it did not go through.

But I rarely see such problems on Plesk hosts unless they use RBLs which you do not. So I think you should ask 4PSA about this one, it looks like they are the cause. Or try disabling your greylisting altogether.
 
Anyone know more about this? Or where I can go to find out more about relaylock?

I have a customer who is using Postini and I see a number of errors in the log like so:

Aug 15 13:50:46 linux1 relaylock: /var/qmail/bin/relaylock: mail from 64.18.2.32:56377 (exprod7mx3.postini.com)

I need to whitelist this host...
 
Dear nathacof,

could you solve this problem?
I face the same problem.

Thx in advance
 
Back
Top