• 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

Plesk 10.4.4: External emails not receiving @ mailserver

E

EdwardDekker

Guest
I do not receiving any external emails after a upgrade of plesk.
All local virtual domains are affected.

$ /usr/local/psa/var/log/maillog
Code: 
Nov 19 18:56:14 edwarddekkerhosting postfix/smtpd[22003]: connect from fallback01.hostnet.nl[91.184.8.23]
Nov 19 17:56:14 edwarddekkerhosting postfix/postmap[22010]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Nov 19 17:56:14 edwarddekkerhosting postfix/postmap[22010]: warning: inet_protocols: configuring for IPv4 support only
Nov 19 18:56:14 edwarddekkerhosting /usr/lib/plesk-9.0/psa-pc-remote[3243]: Message aborted.
Nov 19 18:56:14 edwarddekkerhosting /usr/lib/plesk-9.0/psa-pc-remote[3243]: Message aborted.
Nov 19 18:56:14 edwarddekkerhosting postfix/smtpd[22003]: NOQUEUE: milter-reject: MAIL from fallback01.hostnet.nl[91.184.8.23]: 451 4.7.1 Service unavailable - try again later; from=<[email protected]> proto=ESMTP helo=<fallback01.hostnet.nl>
Nov 19 18:56:14 edwarddekkerhosting postfix/smtpd[22003]: disconnect from fallback01.hostnet.nl[91.184.8.23]
Nov 19 18:56:14 edwarddekkerhosting postfix/smtpd[22003]: connect from fallback01.hostnet.nl[91.184.8.23]
Nov 19 17:56:14 edwarddekkerhosting postfix/postmap[22011]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Nov 19 17:56:14 edwarddekkerhosting postfix/postmap[22011]: warning: inet_protocols: configuring for IPv4 support only
Nov 19 18:56:14 edwarddekkerhosting /usr/lib/plesk-9.0/psa-pc-remote[3243]: Message aborted.
Nov 19 18:56:14 edwarddekkerhosting /usr/lib/plesk-9.0/psa-pc-remote[3243]: Message aborted.
Nov 19 18:56:14 edwarddekkerhosting postfix/smtpd[22003]: NOQUEUE: milter-reject: MAIL from fallback01.hostnet.nl[91.184.8.23]: 451 4.7.1 Service unavailable - try again later; from=<[email protected]> proto=ESMTP helo=<fallback01.hostnet.nl>
Nov 19 18:56:17 edwarddekkerhosting postfix/smtpd[22003]: lost connection after RSET from fallback01.hostnet.nl[91.184.8.23]
Nov 19 18:56:17 edwarddekkerhosting postfix/smtpd[22003]: disconnect from fallback01.hostnet.nl[91.184.8.23]
Nov 19 18:57:46 edwarddekkerhosting postfix/smtpd[22003]: connect from fallback01.hostnet.nl[91.184.8.23]
Nov 19 17:57:46 edwarddekkerhosting postfix/postmap[22015]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Nov 19 17:57:46 edwarddekkerhosting postfix/postmap[22015]: warning: inet_protocols: configuring for IPv4 support only
Nov 19 18:57:46 edwarddekkerhosting /usr/lib/plesk-9.0/psa-pc-remote[3243]: Message aborted.
Nov 19 18:57:46 edwarddekkerhosting /usr/lib/plesk-9.0/psa-pc-remote[3243]: Message aborted.
Nov 19 18:57:46 edwarddekkerhosting postfix/smtpd[22003]: NOQUEUE: milter-reject: MAIL from fallback01.hostnet.nl[91.184.8.23]: 451 4.7.1 Service unavailable - try again later; from=<[email protected]> proto=ESMTP helo=<fallback01.hostnet.nl>
Nov 19 18:57:46 edwarddekkerhosting postfix/smtpd[22003]: disconnect from fallback01.hostnet.nl[91.184.8.23]
Nov 19 18:57:46 edwarddekkerhosting postfix/smtpd[22003]: connect from fallback01.hostnet.nl[91.184.8.23]
Nov 19 17:57:46 edwarddekkerhosting postfix/postmap[22016]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Nov 19 17:57:46 edwarddekkerhosting postfix/postmap[22016]: warning: inet_protocols: configuring for IPv4 support only
Nov 19 18:57:46 edwarddekkerhosting /usr/lib/plesk-9.0/psa-pc-remote[3243]: Message aborted.
Nov 19 18:57:46 edwarddekkerhosting /usr/lib/plesk-9.0/psa-pc-remote[3243]: Message aborted.
Nov 19 18:57:46 edwarddekkerhosting postfix/smtpd[22003]: NOQUEUE: milter-reject: MAIL from fallback01.hostnet.nl[91.184.8.23]: 451 4.7.1 Service unavailable - try again later; from=<[email protected]> proto=ESMTP helo=<fallback01.hostnet.nl>
Nov 19 18:57:46 edwarddekkerhosting postfix/smtpd[22003]: disconnect from fallback01.hostnet.nl[91.184.8.23]
It looks like that a Milter support setting will be the cause of this problem (?? maybe grey listing into PSA ??)
I need truly a solution for this problem. My mailserver can't be out of service for a few days.
 
Last edited by a moderator:
Did you try to rebuild mailserver settings with

# /usr/local/psa/admin/sbin/mchk --with-spam

?
 
IgorG said:
Did you try to rebuild mailserver settings with

# /usr/local/psa/admin/sbin/mchk --with-spam

?
Click to expand...
I have made the reset. All do i not see any change into my status.

You got a PM from me.
 
Same Problem

psa-pc-remote makes 100% cpu usage

if i kill the process smtp server dosen't work any longer...

any other ideas?

debian squeeze
 
Same problem here and nothing to find about in the internet...
 
Did you try to enable IPv6 protocol for network interface?
 
Same issue here - Plesk 10.4.4, CentOS 6 x64 -

30717 postfix 20 0 394m 3976 1212 S 100.1 0.1 73:27.53 psa-pc-remote

[root@s mailnames]# ps -aux | grep psa-pc-remote
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.8/FAQ
root 9555 0.0 0.0 103152 828 pts/0 S+ 12:48 0:00 grep psa-pc-remote
postfix 30717 80.0 0.1 404324 3976 ? Ssl 11:15 74:07 /usr/lib64/plesk-9.0/psa-pc-remote -p inet:12768@localhost

A restart of Postfix temporarily resolves the issue.

We have IPv4 and IPv6 configured.

m.
 
I don't want to use QMail. I can approve that a restart resolve the problem for short time. So I use a crontab any 15 minutes to do so.
/etc/init.d/pc-remote restart

Hoping of a working update.
 
Restarting services at random isn't an option for us. Plesk's Postfix implementation lays atop Qmail either way (see /var/qmail/mailnames) and the button line is, Postfix in 10.4.4 isn't ready for prime-time.
 
hmmm, sorry, but I don't want a "PC-Remote" - because of an update I must change the favorite mail config?

Prefer I want to remove "pc-remote".

Are we Plesk or Windows?

The restart works until yesterday. As I said hoping of an working update - maybe with "remove"-Button for "pc-remote".

;)
 
Plesk 10.4.4, Debian Squeeze, Postfix


After update Plesk 10.3 to 10.4.4 Postfix runs psa-pc-remote process up to 200% cpu usage - endless

only a restart
/etc/init.d/pc-remote restart
brings the system back to normal but the endless process starts unpredictable after short time but within 60 minutes.

If the process is stopped no smtp is possible.
 
Switch to Qmail

As I can see, postfix is not good configured.
Qmail looks like the best option to install for now.

You can always return to postfix if a patch has solved the problem.
By the update-page of Plesk can you easily switch the mail-server.
 
I have this Problem too (with my other Problems *hrm*)

---------------------------------------------------------------
PRODUCT
Virtuozzo Plesk

VERSION
10.4.4 (after Updating from 10.3.1)

OPERATING SYSTEM
Linux2.6.18-028stab092.1 Ubuntu 10.04.3 LTS

ARCHITECTURE
x86_64 GNU/Linux

PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
After updating to 10.4.4 external E-Mails did not recieve at the Server.

ACTUAL RESULT
Excerpt from mail.warn
Nov 22 11:42:38 ServerIP postfix/smtpd[3782]: warning: AnotherIP: address not listed for hostname AnotherIP.static.eastern-tele.com
Nov 22 11:42:38 ServerIP postfix/smtpd[3782]: warning: connect to Milter service inet:localhost:12768: Connection refused
Nov 22 11:42:45 ServerIP postfix/smtpd[3782]: warning: AnotherIP: address not listed for hostnameAnotherIP.ids.static.eastern-tele.com
Nov 22 11:42:45 ServerIP postfix/smtpd[3782]: warning: connect to Milter service inet:localhost:12768: Connection refused
Nov 22 11:42:55 ServerIP postfix/smtpd[5130]: warning: connect to Milter service inet:localhost:12768: Connection refused
Nov 22 11:43:26 ServerIP postfix/smtpd[3782]: warning: connect to Milter service inet:localhost:12768: Connection refused
Nov 22 11:43:27 ServerIP pop3d: 1321958607.198163 LOGOUT, [email protected], ip=[::ffff:ServerIP], top=0, retr=55915, time=26, rcvd=42, sent=57369, maildir=/var/qmail/mailnames/userdomain.de/username/Maildir
Nov 22 11:43:36 ServerIP postfix/smtpd[5130]: warning: connect to Milter service inet:localhost:12768: Connection refused
Nov 22 11:44:12 ServerIP pop3d: 1321958652.550239 LOGOUT, [email protected], ip=[::ffff:ServerIP], top=0, retr=21091, time=45, rcvd=58, sent=21752, maildir=/var/qmail/mailnames/username.de/user2/Maildir
Nov 22 11:44:12 ServerIP pop3d: 1321958652.735211 LOGOUT, [email protected], ip=[::ffff:ServerIP], top=0, retr=0, time=0, rcvd=12, sent=39, maildir=/var/qmail/mailnames/username.de/info/Maildir
Nov 22 11:44:25 ServerIP postfix/smtpd[3782]: warning: AnotherIP: address not listed for hostname AnotherIP.airtelbroadband.in
Nov 22 11:44:25 ServerIP postfix/smtpd[3782]: warning: connect to Milter service inet:localhost:12768: Connection refused
Nov 22 11:44:35 ServerIP postfix/smtpd[3782]: warning: connect to Milter service inet:localhost:12768: Connection refused
Nov 22 11:44:36 ServerIP postfix/smtpd[3782]: warning: AnotherIP: address not listed for hostname AnotherIP.unassigned.static.eastern-tele.com
Nov 22 11:44:36 ServerIP postfix/smtpd[3782]: warning: connect to Milter service inet:localhost:12768: Connection refused
Nov 22 11:44:38 ServerIP postfix/smtpd[3782]: warning: AnotherIP: address not listed for hostname AnotherIP.unassigned.static.eastern-tele.com
Nov 22 11:44:38 ServerIP postfix/smtpd[3782]: warning: connect to Milter service inet:localhost:12768: Connection refused
Nov 22 11:44:51 ServerIP last message repeated 4 times
Nov 22 11:45:37 ServerIP last message repeated 2 times
Nov 22 11:45:47 ServerIP pop3d: 1321958747.763512 TIMEOUT, [email protected], ip=[::ffff:IP], top=0, retr=0, time=301, rcvd=12, sent=41, maildir=/var/qmail/mailnames/user2.com/user1/Maildir
Nov 22 11:45:51 ServerIP postfix/smtpd[3782]: warning: connect to Milter service inet:localhost:12768: Connection refused
Nov 22 11:46:37 ServerIP postfix/smtpd[3782]: warning: connect to Milter service inet:localhost:12768: Connection refused
Nov 22 11:46:50 ServerIP last message repeated 2 times
Nov 22 11:47:03 ServerIP postfix/smtpd[5130]: warning: connect to Milter service inet:localhost:12768: Connection refused
Click to expand...

EXPECTED RESULT
Incomming Mails ;-)

ANY ADDITIONAL INFORMATION
http://forum.parallels.com/showthread.php?p=560370

Greetings!
 
Thank you for report. I have forwarded it to developers. I will keep thread updated with results.
 
I'm restarting the service with this cronjob

# cat /etc/cron.1min/watch-psa-pc-remote

#!/bin/sh
mincpu=`top -b -d4 -n3 -u postfix | grep '[p]sa-pc-remote' | awk '{print $9}' | sort -n | head -n1`
expr ${mincpu} \> 80 >/dev/null && /etc/init.d/pc-remote restart
 
Frater said:
I'm restarting the service with this cronjob

# cat /etc/cron.1min/watch-psa-pc-remote

#!/bin/sh
mincpu=`top -b -d4 -n3 -u postfix | grep '[p]sa-pc-remote' | awk '{print $9}' | sort -n | head -n1`
expr ${mincpu} \> 80 >/dev/null && /etc/init.d/pc-remote restart
Click to expand...

What exactly does this do?
 
each minute it will execute 'top' in batch mode (-b) and with an interval of 4 seconds (-d4) it will sample 3 times for all processes running as the user 'postfix' (-u postfix).

The result will be filtered so it will show only 'psa-pc-remote' (grep '[p]sa-pc-remote')
Then it will take out the CPU value (awk '{print $9}')
These values will be sorted numerically (sort -n)
The first value and therefore lowest value will be taken and stored into "mincpu"

You should first check if this command will give you the expected result:


# top -b -d4 -n3 -u postfix | grep '[p]sa-pc-remote' | awk '{print $9}' | sort -n
0.0
0.0
0.0


if this value (most of the time it's 0.0) is higher then 80 it will execute "/etc/init.d/pc-remote restart" and it should at least kill the high cpu-load.

This means it doesn't just restart the service every 15 minutes, but will only do so if it is eating your cpu.

The exact values for interval and cpu-percentages are a rough estimate of mine.
I've only just recently stumbled on this problem and real-world values may be different.

In other words... this trigger may be too sensitive or not sensitive enough


Maybe it should be a 5-minute cronjob with an interval of 20 seconds.
The cpu value could be lowered as well....


as a one-liner in /etc/crontab it would look like this:


* * * * * root expr `top -b -d4 -n3 -u postfix | grep '[p]sa-pc-remote' | awk '{print $9}' | sort -n | head -n1` \> 80 >/dev/null && /etc/init.d/pc-remote restart
 
Last edited:
You must log in or register to reply here.

Similar threads

J
Resolved Start spamassassin.service Failed with result 'timeout'.
Replies
7
Views
2K
Jelle_Timmer
J
nethubonline
Issue Failed to reset statistics for mail exceed limit
Replies
7
Views
9K
AlmaWalters
A
A
Issue Dovecot service(pop3-login) keeps crashing
Replies
3
Views
2K
a.sari
A
K
Issue Docker containers don't start after plesk/extension upgrades
Replies
0
Views
653
kassi
K
T
Issue SMTPD No Auth from IP Issue
Replies
2
Views
1K
Tessxr
T
Back
Top