Please note this post contains two (2) accompanying screenshots. I went through similar topics but did not find the answer. BABELEXPORT.COM is being hosted by a hosting company, but webmail is not working at all, i.e.: URL webmail page is not opening, no login access, and unable to either send or receive emails. Any email sent to that webmail is returned undelivered. The hosting company asked me to add the following two records in order to unrestrict the emails:
I added the DKIM record as a TXT record and it was accepted smoothly. However, as per screenshot No.1, it was impossible to add the SPF record. Firstly, even if I wrote the record as given to me by the hosting company, the system was displaying a message saying “SPF record must start with v=spf…” [NOTE: The same error message comes up even if I write the record with all letters together without any space in between]. Apart from that, when I clicked on SAVE I got the error message written on the red banner at the bottom of the page saying as follows:
“DNS Validation Error (Code: 1004) The SPF record type was deprecated in RFC 7208 and is no longer supported. Create a TXT record with the same content instead”.
Therefore, I eventually added the SPF record as an SPF record. Screenshot No.2 shows the DNS settings as they are now. The red box refers to the two pieces of text I was asked to add at Cloudflare.
 SUPPORT QUESTIONS:
(1) Is there any reason why the SPF record cannot be added as an SPF record?
Your SPF record needs to use the TXT RR type. It should contain only your apex domain, example.com and you are missing spaces between the individual components of the record.
v=sp1f mx ~all
I dropped the a because it will resolve to Cloudflare proxy IPs which will never be sending mail on your behalf. You could replace the MX with the IP of your server, which will save you one of your permitted ten DNS lookups, but you don’t need both when the are the same.
Thank you epic.network. Yes, the Roundcube was added in the server just immediately after I submitted the post as I thought the problem may have been related to HORDE. I will leave Roundcube as it looks cute and cleaner than HORDE even if it seems less robust in options and settings. I did a test and actually CAN send message successfully (the receiver confirmed receipt), cut CANNOT receive messages. I am going to take action according to your suggestions to see if this is solved. Thank you again.
For the A record I put the mail hostname (mail.babelexport.com) and the server IP as content. However, as per attached screennshot, afterwards I noticed there is a warning message (red square) being shown stating as follows:
This record exposes the IP address used in the A record on babelexport.com. Enable the proxy status to protect your origin server.
I suppose I should disregard this warning because I understand that if this A record is PROXIED then webmail will never work. Am I right on this one?
Wow!! I did a search at Dmarcian and got the report below. No idea what all that stuff means. Just wondering if the “ip4” characters mentioned by the hosting company should have been included. I say this because what has been reported by Dmarcian. The hosting company suggestion was:
Error! Invalid “unknown” mechanism (“unknown”: “188.8.131.52” is unknown mechanism. Valid mechanisms are “all” “include” “a” “mx” “ip4” “ip6” “exists” and “ptr” (“ptr” is deprecated and should not be used).
Done as advised! Thank you very much. By the way, I was going to go back to HORDE but just read a few minutes ago that HORDE is being deprecated, so developers will not make any further updates. Final verdict: I will stay with ROUNDCUBE which has a very nice look. But for business purposes perhaps the best solution would be liaise our webmail to Gmail so that all messages could be send and receive from and by Google as if they belong to our domain name. The only catch is that Google server will keep all our business information in their server, but if we have nothing to hide then we should not be too worry about privacy. There is no such thing like privacy in the internet. Bye