• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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