Caspios emails are being delivered as unauthenticated emails to recipient host (gmail in particular).
reconfigure your email servers (spf, dkim, A & MX Records) and associate the tcp/ip port (usually 25) with the domains ip address. You will also need to configure reverse dns to authenticate the email sender to the receiver host. It's not at all difficult to do.
Thank you for your idea. Caspio Bridge emails are now TLS encrypted with DKIM/SPF/TXT.
George P commented
It would be really useful to have this - bit of a weak area otherwise. Many of our apps rely on auto email.
Edwin Jeffords commented
I would highly encourage this adoption by caspio. Since sending emails on behalf of your clients is more than likely integral into most of your projects, one would think that modernizing to take advantage of DMARC and DKIM would be a high priority. Currently, anything to google and some to yahoo are failing this authentication because of the lack of a simple DNS /Key setup on the caspio side.
My hotmail as well
sign (DKIM) for data page email sending address
ability to sign data page send email address with DKIM records that capio generate
often email being delivered to gmail classified as unauthenticated.
Could you provide some links that has more details of how to do those steps? when you mention domain's IP address...is that for your site or caspio?