DKIM is too long to add txt records

[eritest]

I would like to ask the system how to set the problem of sending domain name DKIM too long, 2048 modified to 1024, dns parsing error, can not exceed 255 characters.


img:http://prntscr.com/ku2riq

 

[frm.mwz]

I would like to ask the system how to set the problem of sending domain name DKIM too long, 2048 modified to 1024, dns parsing error, can not exceed 255 characters.


img:http://prntscr.com/ku2riq

All modern DNS admin/registrars are supposed to be able to handle DKIM 2048, what software or registrar is causing this error?
If you absolutely need to use your current DNS (which demands the shorter DKIM 1024), then create the key elsewhere and copy & paste public and private key into the place where mwz created the longer key and then save & verify it.

 

[twisted1919]

https://kb.mailwizz.com/articles/mailwizz-generates-dkim-keys-that-are-too-long-what-can-i-do/

 

[frm.mwz]

https://kb.mailwizz.com/articles/mailwizz-generates-dkim-keys-that-are-too-long-what-can-i-do/

Good KB article and link!

It might be better to allow selecting which size 1024 or 2048 at the creation time where the sending domain is configured, since this would allow to use whatever the DNS/third party supports, since this can differ by each domain/customer. And it is better to have it flexibly as high as possible since some recipient servers mark down when not 2048.

Also, would be good to have a KB article with a complete list of all custom configuration parameters.

 

[eritest]

'email.custom.dkim.key.size'=> 1024，

Is it added like this? Can you help me tell me the example and the location I added？thanks

http://prntscr.com/kue0zh

The top three domain name service providers in China do not support dkim txt over 255 characters.
Domain name service provider: aliyun.com, xinnet, cloud.tencent.com
Dns hosting :dnspod.cn
They can't add more than 255 characters

https://kb.mailwizz.com/articles/mailwizz-generates-dkim-keys-that-are-too-long-what-can-i-do/

Good KB article and link!

It might be better to allow selecting which size 1024 or 2048 at the creation time where the sending domain is configured, since this would allow to use whatever the DNS/third party supports, since this can differ by each domain/customer. And it is better to have it flexibly as high as possible since some recipient servers mark down when not 2048.

Also, would be good to have a KB article with a complete list of all custom configuration parameters.

 

[twisted1919]

It might be better to allow selecting which size 1024 or 2048

We try to push people using the most secure option, thus 2048 as default. People should not be able to play with these settings, unless cases like this one

'email.custom.dkim.key.size'=> 1024，

You forgot the comma, both of your params must have commas at the end, so:
'param1' => 'value 1',
'param2' => 'value 2',

The top three domain name service providers in China do not support dkim txt over 255 characters.

They should. It's customers pressing on them and making them do an effort to support this.

 

[eritest]

thanks for you.

 

[eritest]

'email.custom.dkim.key.size'=> 1024，

Is it added like this? Can you help me tell me the example and the location I added？thanks

http://prntscr.com/kue0zh

The top three domain name service providers in China do not support dkim txt over 255 characters.
Domain name service provider: aliyun.com, xinnet, cloud.tencent.com
Dns hosting :dnspod.cn
They can't add more than 255 characters

• Unable to retrieve the TXT records for your domain name.

I resolved to the bluehost post office, and it will be verified after 30 minutes of setup, but I have not been able to successfully resolve the mailwizz for 2 months. My mailwizz is installed in the bluehost virtual space.

https://prntscr.com/l7tt0t bluehost mail is ok

 

[twisted1919]

@eritest - the dkim selector has to me mailer._domainkey not 20180911._domainkey

 

[eritest]

@eritest - the dkim selector has to me mailer._domainkey not 20180911._domainkey

thank you for your help

The screenshot is a screenshot of the bluehost post I added.

In fact, the analysis of domain name service providers in China has not been effective. Now I try to transfer the domain name to dns.he.net and then parse txt, but it still can't take effect.

IMG: http://prntscr.com/l7zrqs

 

[twisted1919]

@eritest - you are editing the DNS records for pipige.com ( dns okay: https://www.mail-tester.com/spf-dkim-check ) but in mailwizz, i see a domain starting with mw....

 

[eritest]

@eritest - you are editing the DNS records for pipige.com ( dns okay: https://www.mail-tester.com/spf-dkim-check ) but in mailwizz, i see a domain starting with mw....

I am using a second-level domain name.
（mw.pipige.com）
http://i.prntscr.com/eV4Je65fTzuhVy5YaGMzsg.png

 

[twisted1919]

I am not sure how that is going to work, you might need to add the dkim to mailer._domainkey.mw.pipige.com instead of mailer._domainkey.pipige.com
Anyway, you might want to consult with your web hosting for this.

 

[eritest]

I am not sure how that is going to work, you might need to add the dkim to mailer._domainkey.mw.pipige.com instead of mailer._domainkey.pipige.com
Anyway, you might want to consult with your web hosting for this.

Thank you for your help, I tried to change to mailer._domainkey.mw.pipige.com is already working, thank you very much for your help.