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

The "handlers permanentfail" is still present

J

J0hnD03

Guest
Hi I updated the panel, turn on all the domainkeys options for all the domains and then the option in the system panel, and I can't use the alias and redirects yet :(

What could I do ?

Thanks.

Delivered-To: googleaccountxyz@gmail.com
Received: by 10.100.163.12 with SMTP id l12cs300787ane;
Tue, 29 Jul 2008 08:13:34 -0700 (PDT)
Received: by 10.114.170.2 with SMTP id s2mr6736965wae.170.1217344412973;
Tue, 29 Jul 2008 08:13:32 -0700 (PDT)
Return-Path: <>
Received: from dedicated.csltda.com (ip-72-55-133-236.static.privatedns.com [72.55.133.236])
by mx.google.com with ESMTP id s27si3811285qbs.12.2008.07.29.08.13.32;
Tue, 29 Jul 2008 08:13:33 -0700 (PDT)
Received-SPF: neutral (google.com: 72.55.133.236 is neither permitted nor denied by best guess record for domain of dedicated.csltda.com) client-ip=72.55.133.236;
Authentication-Results: mx.google.com; spf=neutral (google.com: 72.55.133.236 is neither permitted nor denied by best guess record for domain of dedicated.csltda.com) smtp.mail=
Message-Id: <488f339d.1b2d400a.4e00.ffff8289SMTPIN_ADDED@mx.google.com>
Received: (qmail 17531 invoked for bounce); 29 Jul 2008 10:13:31 -0500
Date: 29 Jul 2008 10:13:31 -0500
From: MAILER-DAEMON@dedicated.csltda.com
To: googleaccountxyz@gmail.com
Subject: failure notice

Hi. This is the qmail-send program at dedicated.csltda.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<googleaccountxyz@gmail.com>:
handlers permanentfail

--- Below this line is a copy of the message.

Return-Path: <googleaccountxyz@gmail.com>
Received: (qmail 17523 invoked by uid 110); 29 Jul 2008 10:13:31 -0500
Delivered-To: 6-localacountxyz@lomasbacano.com
DomainKey-Status: good
Received: (qmail 17511 invoked from network); 29 Jul 2008 10:13:31 -0500
Received: from an-out-0708.google.com (209.85.132.240)
by ip-67-205-92-4.static.privatedns.com with SMTP; 29 Jul 2008 10:13:30 -0500
Received-SPF: pass (ip-67-205-92-4.static.privatedns.com: SPF record at _spf.google.com designates 209.85.132.240 as permitted sender)
Received: by an-out-0708.google.com with SMTP id d17so1059024and.114
for <localacountxyz@lomasbacano.com>; Tue, 29 Jul 2008 08:13:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:sender
:to:subject:mime-version:content-type:x-google-sender-auth;
bh=tC949dBglfDJm5h3G0395Youz6TYsIOUHldcwIDI+Ms=;
b=aKe8GUb657EMStSfzs9p6OtlLGTaXPXz4sgC4B1V4kMS/J3m8DbtXaHAoK3jP1aGYh
tRyFch9AaPevkaVQHVVbe/qAoG0oekr/7gOnSO0pqVYmKAFJHIDC++WMLk458a45hAW6
msYCx4xBKf6z69gYlw8CVp6PlVsHLPufBOMqk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=message-id:date:from:sender:to:subject:mime-version:content-type
:x-google-sender-auth;
b=mo+kyShRnNGpRb4kjIB7U2fk7Bs7ARh3m7GZrmnN3jtHzs0l3p9MyvgX86Uwmrlj6N
E1ETkwGRxUxBR8FL0A0obpCZthX/kMEhhhUL3JE1FfbqKJVV+33SIUZWYCR06/miDc46
XqVrZpfxp77tLkDKq6PipfKb0xkzKgcFT8d4I=
Received: by 10.100.6.13 with SMTP id 13mr10491861anf.83.1217344411853;
Tue, 29 Jul 2008 08:13:31 -0700 (PDT)
Received: by 10.100.163.12 with HTTP; Tue, 29 Jul 2008 08:13:31 -0700 (PDT)
Message-ID: <d33646670807290813g6954c7ebs81babb4d77b7621@mail.gmail.com>
Date: Tue, 29 Jul 2008 10:13:31 -0500
From: "Alejandro Trujillo J." <medios@cadenaporelvalle.com>
Sender: googleaccountxyz@gmail.com
To: andresgarcia@lomasbacano.com, localacountxyz@lomasbacano.com
Subject: Test 2
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_58989_5091150.1217344411779"
X-Google-Sender-Auth: 07f43c391577b453

------=_Part_58989_5091150.1217344411779
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
Alejandro Trujillo J.
Portal & Forum Administrator
www.lomasbacano.com
www.bailesimulado.com
www.catorce6.com
Hi5: http://alejobacano.hi5.com

------=_Part_58989_5091150.1217344411779
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


------=_Part_58989_5091150.1217344411779--
 
same here :(

mail is in the queue and not sent
I just disabled domainkeys to see if it fixes the issue
 
i have the same problem here with plesk 8.6.0

we have many entrys in the log like:

Jul 30 22:39:10 ally qmail-remote-handlers[8050]: domainkeys-handler exited with status 81
Jul 30 22:39:10 ally qmail-remote-handlers[8050]: call_handlers: stop call handlers because handler 'dd51-domainkeys' not PASS (31)
Jul 30 22:39:10 ally qmail: 1217450350.950012 delivery 607: failure: handlers_permanentfail/
 
:( I have same problem

My Plesk 8.6 FC7, have same problem with mail from gmail in accounts with redirect and DK.

Help!!!! I need solution.

Swsoft have a fix, for this problem???
 
Gentlemen,

Thank you for the reports.

Unfortunately we cannot reproduce the issue in our lab.

Could you grand us root access to your problem server? We need to investigate the issue on site.
Please send me PM with server address and credentials.
 
Me too!

Is it possible to subscribe the thread without posting?
 
sergius has solved the problem on one of our server but i don't know what he have done to fix it ...

@sergius please let us know how to fix it...

@hakito just use the link under "Thread tools" on the bottom of the site to subscribe without posting ...
 
I have another problems with the domain-keys option: I deactivated the domain-keys verification for incoming mail in Server->E-mail

But i still get this error Message for incoming Mail:

Aug 18 11:25:03 sg18 qmail-remote-handlers[18314]: domainkeys-handler exited with status 31
Aug 18 11:25:03 sg18 qmail-remote-handlers[18314]: call_handlers: stop call handlers because handler 'dd51-domainkeys' not PASS (31)
 
I give to the admin full access to my server, I hope they can see what is wrong.
 
Gentlemen,

Thank you all for the help. I hope we have collected enough information to resolve the issue permanently. The bugfix will be delivered with the nearest Plesk update that is expected for a week.
 
Hi, glad to help plesk if the access to my server gave you info for the new fix.

Now I will change the root password, tell me if you need other temp access to it.
 
Sergius, Is this fix OS specific? Is it going to take care of this issue on freebsd as well?
 
Hello,

This problem has been solved in Plesk 8.6.1?

Thanks,
 
Nobody has been update to Plesk 8.6.1?

Please, Can somebody confirm if this problem is present in 8.6.1 or has been resolved?

Thanks,
 
dear plesk, in your last message you mentioned update fix will be ready in 1 week. we are now a few weeks further can you please give us an update if it is resolved, and if not when it will be resolved.

kind regards,
Martin
 
Even with 8.6.1 I am STILL seeing domainkeys rejects. This is just unbelievable. I'd be happier if you'd just yank the feature and work on Postfix integration. At least then we could do domainkeys and DKIM on our own.
 
Just stumbled across this one myself on Debian with 8.6.0.

Release notes imply this was fixed in 8.6.0 update-1:

http://download1.sw-soft.com/Plesk/plesk-for-deb-based-os.html
"[-] Mail redirect not working when DomainKeys signing is enabled on server-wide level bug is fixed."

Can others confirm if this is true or not as I'd rather not update and re-enable it to be hit by the same problem.

Cheers,

john
 
Back
Top