mail forwarding Failed after update to plesk 12

[sproit]

Hello, 2 weeks ago I update my plesk 11,5 to 12
And I activate (limit control for smtp)
After this action the email forwarding fails in all domains of plesk.

-----------------------------------------------------------------------
This is the mail system at host fsyc.org.

I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can delete your own text from the attached returned message.

The mail system

<[email protected]>: Command rejected

-----------------------------------------------------------------------


Reporting-MTA: dns; fsyc.org
X-Postfix-Queue-ID: 5B51E2E800BC
X-Postfix-Sender: rfc822; [email protected]
Arrival-Date: Tue, 16 Sep 2014 14:21:10 +0200 (CEST)

Final-Recipient: rfc822; [email protected]
Action: failed
Status: 5.7.1
Diagnostic-Code: X-Postfix; Command rejected
-----------------------------------------------------------------------

Can you help me please?

 

[UFHH01]

First of all, to inform you: "Status 5.7.1" means that this is a permanent failure / Delivery not authorized, message refused

Could you post some mail.log entries with your issues, to investigate WHY the delivery is being refused? You find the specific path to logs here: Parallels Plesk Panel for Linux services logs and configuration files ( KB: 111283 )

 

[sproit]

mailog and undelivery headers

First of all, to inform you: "Status 5.7.1" means that this is a permanent failure / Delivery not authorized, message refused

Could you post some mail.log entries with your issues, to investigate WHY the delivery is being refused? You find the specific path to logs here: Parallels Plesk Panel for Linux services logs and configuration files ( KB: 111283 )

email to [email protected] -> fordwarding to [email protected]
MAILOG
---------
Sep 16 18:14:20 fsyc postfix-local[7244]: postfix-local: [email protected], [email protected], dirname=/var/qmail/mailnames
Sep 16 18:14:20 fsyc spamd[2639]: spamd: using default config for [email protected]: /var/qmail/mailnames/solucionesproit.com/info/.spamassassin/user_prefs
Sep 16 18:14:20 fsyc spamd[2639]: spamd: processing message <[email protected]> for [email protected]:110
Sep 16 18:14:20 fsyc spamd[2639]: spamd: clean message (-0.8/7.0) for [email protected]:110 in 0.4 seconds, 4324 bytes.
Sep 16 18:14:20 fsyc spamd[2639]: spamd: result: . 0 - DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,MIME_HTML_MOSTLY,RCVD_IN_DNSWL_LOW,TVD_SPACE_RATIO scantime=0.4,size=4324,[email protected],uid=110,required_score=7.0,rhost=localhost.localdomain,raddr=127.0.0.1,rport=41194,mid=<[email protected]>,autolearn=ham
Sep 16 18:14:21 fsyc postfix/pipe[6370]: 32C4E2E800C4: to=<[email protected]>, relay=plesk_virtual, delay=1.5, delays=0.28/0/0/1.2, dsn=2.0.0, status=sent (delivered via plesk_virtual service)


Sep 16 18:14:21 fsyc postfix/cleanup[4601]: 3FABB2E800D0: milter-reject: DATA from localhost[127.0.0.1]: 5.7.1 Command rejected; from=<[email protected]> to=<[email protected]>
Sep 16 18:14:21 fsyc postfix/cleanup[4601]: 3FABB2E800D0: to=<[email protected]>, relay=none, delay=0.16, delays=0.16/0/0/0, dsn=5.7.1, status=bounced (Command rejected)


I remove 127.0.0.1 from White list to use smtp control limit
thanks



Undelivery Headers
----------------------
Return-Path: <[email protected]>
Received: by fsyc.org (Postfix, from userid 110)
id 3FABB2E800D0; Tue, 16 Sep 2014 18:14:21 +0200 (CEST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=default; d=fsyc.org;
b=jlVQakoZoQcOEthsGEPmzv0rnzWLc1btofF3rssF2iHVA15YXNY75jeIr5PksDsOtHy7NZ7dSbXdVuXKzNDbAGwV5BYIxg5VOEGz399s9Vf752wpbdP97CwURmhxLCdIHAZFWBtGbflISwpin5/7Ar08mvOdPrPYys0St7yHbSs=;
h=DomainKey-Status:Return-Path:X-Spam-Checker-Version:X-Spam-Level:X-Spam-Status:X-Original-Toelivered-To:Received:Received-SPF:Authentication-Results:ReceivedKIM-Signature:X-Received:Received:From:To:Subjectate:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:X-PPP-Message-ID:X-PPP-Vhost;
DomainKey-Status: no signature
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on fsyc.org
X-Spam-Level:
X-Spam-Status: No, score=-0.8 required=7.0 tests=DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, MIME_HTML_MOSTLY,
RCVD_IN_DNSWL_LOW, TVD_SPACE_RATIO autolearn=ham version=3.3.1
X-Original-To: [email protected]
Delivered-To: [email protected]
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com
[209.85.212.171]) by fsyc.org (Postfix) with ESMTPS id 32C4E2E800C4
for <[email protected]>; Tue, 16 Sep 2014 18:14:20 +0200 (CEST)
Received-SPF: pass (fsyc.org: domain of gmail.com designates 209.85.212.171 as
permitted sender) client-ip=209.85.212.171;
[email protected]; helo=mail-wi0-f171.google.com;
Authentication-Results: fsyc.org; dkim=pass reason="2048-bit key"
header.d=gmail.com [email protected] header.b=vYgBeHRI;
dkim-adsp=pass
Received: by mail-wi0-f171.google.com with SMTP id bs8so6664085wib.4
for <[email protected]>; Tue, 16 Sep 2014 09:14:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=from:to:subject:date:message-id:mime-version:content-type
:thread-index:content-language;
bh=MnW4Pgs4vAJteNeDStpA8FPLeqNIaorq4DU8npEquNA=;
b=vYgBeHRIA+YQxru74mDQui759b579wD8ae7hS/v/iXnaYeR1GuuKYc5Mhfi7NxV9tw
YGFWhCntoHXgyJwXTNe3w38Xq5gNpW5EPa/ire2EbaW1zluTPyuWUTO2yoaXlljH4FOu
qgNmS6hwk0oZt8v3XkBVkP+Iw0HRYBHSOxHrRPbD2U3Za5sQ0ISwzCRoSeSvfUpkVocT
KUJy6qhpVLjWEOp0g3ZALXU6FjRZYitsM8cLM1l+dF/o2feNUeLvVpXEdZCgxEYL71FL
cgCIXJLwh1q/aIJvx/d/8j+HirflXX7Wx6iRcNtEahd0k7vkeQnzOUnJ9j0Tot1FY0+7
HiSA==
X-Received: by 10.180.184.166 with SMTP id ev6mr33610950wic.23.1410884061724;
Tue, 16 Sep 2014 09:14:21 -0700 (PDT)
Received: from RobertoPC ([85.48.253.229])
by mx.google.com with ESMTPSA id i6sm2385553wib.7.2014.09.16.09.14.20
for <[email protected]>
(version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
Tue, 16 Sep 2014 09:14:20 -0700 (PDT)
From: "Roberto Buil Artal" <[email protected]>
To: <[email protected]>
Subject: fordwarding error
Date: Tue, 16 Sep 2014 18:14:18 +0200
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0E7E_01CFD1DA.096E8F30"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: Ac/RyULGA0sUUwrwTVGBWe3HkUOk1g==
Content-Language: es
X-PPP-Message-ID: <[email protected]>
X-PPP-Vhost: solucionesproit.com

 

[UFHH01]

Please check your main.cf in /etc/postfix/ ... according to the log, the milter rejects the mail.

smtpd_milters = , inet:127.0.0.1:12768, inet:127.0.0.1:8891
non_smtpd_milters =
milter_default_action = accept
milter_protocol = 6​

The first milter ist the "psa-pc-remote", the second is the OpenDKIM milter. If you don't use DKIM to sign your emails, please don't include this milter in the config.

---

Some common mistakes as well result by wrong entries here:

mydestination = $mydomain, localhost, localhost.localdomain
relayhost =
mynetworks = ​

---

After changing something in the main.cf, please restart postfix. It doesn't hurt restarting the "psa-pc-remote" as well:

/etc/init.d/postfix restart
/etc/init.d/pc-remote restart​

---

If you still experience problems/issues, please include the complete main.cf and master.cf ( from /etc/postfix ) for investigations and another log entry from the mail.log after the changes were done. You may as well wipe out all specific domainnames and IPs, to protect your sensitive data.

 

[sproit]

Please check your main.cf in /etc/postfix/ ... according to the log, the milter rejects the mail.

smtpd_milters = , inet:127.0.0.1:12768, inet:127.0.0.1:8891
non_smtpd_milters =
milter_default_action = accept
milter_protocol = 6​

The first milter ist the "psa-pc-remote", the second is the OpenDKIM milter. If you don't use DKIM to sign your emails, please don't include this milter in the config.

---

Some common mistakes as well result by wrong entries here:

mydestination = $mydomain, localhost, localhost.localdomain
relayhost =
mynetworks = ​

---

After changing something in the main.cf, please restart postfix. It doesn't hurt restarting the "psa-pc-remote" as well:

/etc/init.d/postfix restart
/etc/init.d/pc-remote restart​

---

If you still experience problems/issues, please include the complete main.cf and master.cf ( from /etc/postfix ) for investigations and another log entry from the mail.log after the changes were done. You may as well wipe out all specific domainnames and IPs, to protect your sensitive data.

Perfect, the problem is solved!
Thank you