james789Q: How does ProxiedMail handle SPF, DKIM, DMARC and Shared Reputation?
I’m considering using ProxiedMail but I wanted to get clarity on how your service manages technical email authentication for deliverability. Specifically:
How does ProxiedMail handle SPF, DKIM, and DMARC for emails proxied through your domains?
Are there any potential deliverability issues when using your default proxy domains (like pxdmail.net) due to authentication or shared reputation?
If I use a custom domain, what is the process for setting up the appropriate SPF, DKIM, and DMARC records?
Have you seen any cases where recipient services or sites block or flag emails sent via proxy/temporary domains for security or anti-abuse reasons?
Are there any recommendations for maximizing deliverability and avoiding getting flagged as spam?
Thanks for any insight you can provide.
apps68
Oct 26, 2025A: Hi,
It's Alex, the founder of ProxiedMail.
Regarding the SPF, DKIM and DMARC - we simply ask you to place the txt/cname records to your domain in order to follow those protocols.
Default domains - possible deliverability issues as any other email provider. Depends on the content of your email. By default our deliverability is obviously lower than Gmail.
" I use a custom domain, what is the process ..." - Simply mount needed TXT, CNAME to your domain.
> Have you seen any cases where recipient services or sites block or flag emails sent via proxy/temporary domains for security or anti-abuse reasons
Yes, but still I wouldn't say it's really common.
> Are there any recommendations for maximizing deliverability and avoiding getting flagged as spam?
Nope. Our priority is receiving emails - not sending. Sending is the side-feature. If you want to mainly send emails with great delivery - I suggest looking for another tool.