Article ID: 114704, created on Sep 3, 2012, last review on May 11, 2014

  • Applies to:
  • Plesk 11.x for Linux
  • Plesk 10.x for Linux
  • Plesk 9.x for Linux/Unix
  • Plesk 11.x for Windows
  • Plesk 10.x for Windows
  • Plesk 9.x for Windows

Symptoms

Note: This article applies to Windows as well. However, some of the below commands for checking IP addresses can be run on Linux only.

Mail cannot be sent from my Parallels Plesk Panel (PP) server via SMTP.
In fact, messages reach the remote mailbox, but are always recognized as SPAM.

Cause

This may happen if the sender's IP address does not match the MX record of the server.

Diagnostics

Determine the sender's IP address. On a PP server, it is the IP address of the domain the mail is sent from:

# nslookup domain.tld
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   domain.tld
Address: 1.1.1.1



Determine the hostnames of your MX-es:

# dig MX domain.tld

; <<>> DiG 9.7.3-P3-RedHat-9.7.3-8.P3.el6_2.2 <<>> MX domain.tld
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28034
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;domain.tld.           IN      MX

;; ANSWER SECTION:
domain.tld.    43200   IN      MX      30 mx1.domain.tld.
domain.tld.    43200   IN      MX      20 mx2.domain.tld.


Now determine the IP addresses of your MX-es:

# nslookup mx1.domain.tld
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   mx1.domain.tld
Address: 2.2.2.2

# nslookup mx2.domain.tld
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   mx2.domain.tld
Address: 3.3.3.3



As you can see, the sender's IP address (1.1.1.1) does not match those of the MX-es (2.2.2.2 and 3.3.3.3). This causes messages to be recognized as SPAM.

Resolution

Make sure that your MX-es resolve to the same IP address as the sender's IP address.

bd7fc88cf1b01f097749ae6f87272128 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 85a92ca67f2200d36506862eaa6ed6b8 dd0611b6086474193d9bf78e2b293040 29d1e90fd304f01e6420fbe60f66f838 6ef0db7f1685482449634a455d77d3f4 aac4a8fcd879de03758354e15495d69a c796c01d6951fa24ed54c7f1111667c6 0a53c5a9ca65a74d37ef5c5eaeb55d7f

Email subscription for changes to this article
Save as PDF