Upgrade to 9.2.3 Breaks DomainKeys

[deltatech]

Ever since I upgraded to 9.2.3 Domain keys hasn't worked. Many people still have the DNS entry for domain keys yet they are not signing the outgoing messages. This is causing many bounced messages.

The bounce message we keep seeing is

Remote host said: 550 Message does not pass DomainKeys requirements for domain MYDOMAIN.com

 

[IgorG]

Did you tried rebuild mail settings with

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

 

[deltatech]

No, that didn't help at all.

DomainKeys is severely broken in 9.2.3

If you turn on outbound message signing, you get thousands of blank messages each day with empty To:, From: and Subject lines with the top line of the message header being "DomainKey-Status: bad format"

If you turn OFF the outbound message signing, messages bounce with this...

Remote host said: 550 Message does not pass DomainKeys requirements for domain MYDOMAIN.com

The reason they bounce is because the control panel is too stupid to remove the domainKeys DNS record when turning off the signing of outbound email.

So the only workaround for this is to turn off the signing of outbound emails then manually remove ALL domainKeys DNS records.

DomainKeys worked great in 9.2.2 but is severely broken in 9.2.3

 

[technema]

Same problem here ....

Debian 5.0.3 + Plesk 9.2.3

DomainKeys is severely broken, i have a lot of messages which bounce with :
Remote host said: 550 Message does not pass DomainKeys requirements for domain MYDOMAIN.com

Same solution (temporaly) :
Remove all Domainkeys DNS records;

 

[DraganM]

These workarounds worked for me

I applied the workarounds:

Empty "from" field and from=#@[]
http://forum.parallels.com/showpost.php?p=393531&postcount=24

And from here (I did the second recommended option):
enabled global handlers break system aliases in qmail
http://forum.parallels.com/showpost.php?p=393982&postcount=33

And now it seems that this fixes all the domain key issues I was having on centos 5.4 32bit and plesk 9.2.3. (Make sure to apply both workarounds .. if you just apply the first it will likely break all your mail and you will get looping with thousands of bogus emails!).