If you are getting failure messages in Roundcube, itself–meaning a little popup that says there is a connection error or something of that nature–there may be info in the Roundcube error log. The easiest way to see this is to tail -f the log while reproducing the issue.
After this mail queuq problem, right now even with SPF, DKIM, and DMARC records for my domains. my mail is still sending to SPAM folder. Before this, it doesn’t sent to the spam. is there any advice to make the message sends into Inbox?
Just in case, here’s how my MX or SPF records looks like:
It’s unlikely that anyone would be able to assist without more information. Your DNS records are only half of the equation.
Wild Guess: It’s possible that because you’re proxying the mail subdomain, you’re failing SPF checks because the IP address you’re sending from (162.0.216.162 I presume) doesn’t match the public A record for mail.vdosmartgadget.com. That subdomain returns
[brandon@fedora ~]$ dig a mail.vdosmartgadget.com +short
172.67.200.9
104.21.36.227
It seems possible that mail carriers are seeing that 162.0.216.162 does not equal 172.67.200.9 or 104.21.36.227 and it fails SPF. Looking at the headers of an email that has gone to spam would also be a great first step in understanding what is happening. If you’re not sure how to read email headers, there are many tools online to parse those headers for you, such as: Email Header Analyzer, RFC822 Parser - MxToolbox
The spf must be ended with an all or a redirect to be fully valid
The Dmarc is set to www and shows published but no policies enabled
There is other reasons as well, such as content filtering or some gmail users have added emails sent from server as spam, and as such, gmail now class the server as a spam sender (Microsoft do similar) or even reputation of sending server or domain as poor
As iworx-brandon posted, the header details of the email sent to spam would most likely show the reason
Thank you for your response, and good monring to you John.
I find it strange… How come my SPF pointing different ip address, but then I find out only my DKIM record is the Fail here.
Here’s the Email header analyzer full report:
there’s another two TXT record… one is for the sendblue as my the site smtp for password recovery mail, but the other one I’m not sure where did I get it…
I was just currious. for the DKIM part.
whats that “p” is about? the p at the DKIM record: p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMVIzrCa3T14JsNY0IRv5/2V1/v2itlviLQBwXsa7shBD6TrBkswsFUToPyMRWC9tbR/5ey0nRBH0ZVxp+lsmTxid2Y2z+FApQ6ra2VsXfbJP3HE6wAO0YTVEJt1TmeczhEd2Jiz/fcabIISgXEdSpTYJhb0ct0VJRxcg4c8c7wIDAQAB