• Inviting everyone who uses WordPress management tools in Plesk
    The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
    To participate, please use this link .
    Your experience will help shape product decisions and ensure the tools better support real-world use cases.

Google Apps (Authenticating Email)

Sean Duffy

New Pleskian
Google recently changed their domain keys to 2048 bit. This means that they are now over the 255 character limit. Cpanel does not have this issue but apparently Plesk servers do.

This is the full record.

google._domainkey

v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApp7rMIXBZajagSkEU4xRS5Ojzx0Lslz59VoEltbpf43CmVn/FOm7w0p73epZChCLN5i255jrnRlPu+9X0ysqIna1rQYObSxnlX500LyLoQQ0By+QZMWs7ERdaEYhddAs+vc+o36+VUl8oraXl7wad+ITYapw216qbVSOGs5S1DLfp2P44whzdk3x8gnLa0N8x0PsbfO3FfUP7Owf7m5n95pMtutGUmVVMbOs5zbPDNrma9Emk1Huk6FsP7se72VwlhjvwmclTb+0odXRcLbTlnz15Qymm4V9cOYrtrgpw7zgF4kNRcgVPQPqDpsjf4FSasph4NEQ+6CVwdeKRHevwwIDAQAB

I tried splitting it into two parts separated by quotes. My admin says it is resolving but Google is still not validating it. Am I missing something?

How do we get this working?

Thanks


Sean

google._domainkey

"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApp7rMIXBZajagSkEU4xRS5Ojzx0Lslz59VoEltbpf43CmVn/FOm7w0p73epZChCLN5i255jrnRlPu+9X0ysqIna1rQYObSxnlX500LyLoQQ0By+QZMWs7ERdaEYhddAs+vc+o36+VUl8oraXl7"

google._domainkey

"wad+ITYapw216qbVSOGs5S1DLfp2P44whzdk3x8gnLa0N8x0PsbfO3FfUP7Owf7m5n95pMtutGUmVVMbOs5zbPDNrma9Emk1Huk6FsP7se72VwlhjvwmclTb+0odXRcLbTlnz15Qymm4V9cOYrtrgpw7zgF4kNRcgVPQPqDpsjf4FSasph4NEQ+6CVwdeKRHevwwIDAQAB"
 
I have exactly the same problem.
I have been googling for a solution, but could not find any.
 
I have found a workaround, that is not very "Kosher", but for now, it does the job.
  1. Add the TXT record with the first part:

    google._domainkey

    "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApp7rMIXBZajagSkEU4xRS5Ojzx0Lslz59VoEltbpf43CmVn/FOm7w0p73epZChCLN5i255jrnRlPu+9X0ysqIna1rQYObSxnlX500LyLoQQ0By+QZMWs7ERdaEYhddAs+vc+o36+VUl8oraXl7"


  2. In SSH, go to /var/named/run-root/var, and edit the file for your domain (it is simply named exactly like your domain).
    At the end of the TXT record, add a space, and the missing txt.
    In your case, it would look like:

    google._domainkey.YOURDOMAIN "v=DKIM1; k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApp7rMIXBZajagSkEU4xRS5Ojzx0Lslz59VoEltbpf43CmVn/FOm7w0p73epZChCLN5i255jrnRlPu+9X0ysqIna1rQYObSxnlX500LyLoQQ0By+QZMWs7ERdaEYhddAs+vc+o36+VUl8oraXl7" "wad+ITYapw216qbVSOGs5S1DLfp2P44whzdk3x8gnLa0N8x0PsbfO3FfUP7Owf7m5n95pMtutGUmVVMbOs5zbPDNrma9Emk1Huk6FsP7se72VwlhjvwmclTb+0odXRcLbTlnz15Qymm4V9cOYrtrgpw7zgF4kNRcgVPQPqDpsjf4FSasph4NEQ+6CVwdeKRHevwwIDAQAB"

  3. Save the modified file.
  4. In the Plesk GUI, restart the BIND server.
  5. Check your TXT record, it should be OK.
The HUGE caveat is that the Plesk DB does NOT reflect the complete info!!!
Therefore, ANY modification of ANY record of THIS domain would simply ERASE that TXT record, and reduce it to its first part!!!

If anyone has a better idea, please share it!
 
I tested my solution from the office, using WS_Ping ProPack, an "antiquated" program, and I received the correct answer :cool: :

google._domainkey.MYDOMAIN.
TXT: ¤v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAiSR73rEkhN33leVGp/Z/Q/SX/nhLxlcjde+42ugBwe94VZ/YXpUOlPYNUnsanGK17+6HTLJVYM/Cquvbk8jYOhPueLZq0LFI68dkE/ö2MXCr5nZ1NaWqwYO5fHjzrZyHsX+VtXeegUpFcqHHDomiDPK5B1p/Hf1t6gEXa9VG7slS6D2of1ZnMpzSgSKBCEvZXoyu1Hg7pzn+B6SnvqE01hQU/G+9pMfSl8eug363Fbqo7NtGVswJEqysyaEvtBlQnksZbS0SZYIgFKz4BWlFpXqdyf7xUiS5JdM2iHBvIOh19HSlc2W0Eqe3wf0i2pwpOUNguZ6trnqtITIatwm6sTwIDAQABÀ

**complete**
 
Back
Top