Gmail forward giving error because relay in place (SRS is on)
Hello!
We all know that when setting a forward to @gmail.com, Gmail mistakenly checks the original FROM's domain for SPF of our cPanel server. For this the solution is enabling SRS, hooray :-)
My problem is that I have a selective relay in place, because sometimes I need to switch sending servers because of temporary blocklists or simply because for some reason Gmail does not like my original server's IP (which works great everywhere else and I don't have any idea what to do about it).
The relay in exim.conf looks like this in ROUTERS CONFIGURATION section:
static_route:
driver = manualroute
transport = remote_smtp
route_data = ${lookup{$domain}partial-lsearch{/etc/staticroutes}}
Now this relay thing works great but I have noticed that the enabled SRS does not have an impact on relayed mail and that is causing my problem, since Gmail does not like my original IP.
I tried to put the relay line somewhere after "SRS" stuff that cPanel generates in exim.conf, but then the relay stopped working :-)
So my question is how can I have a proper SRS hack (provided by cPanel WHM) and also have a selective relay like above?
Thanks
-
Hey there! We aren't able to provide this level of customization support, but you likely need to add an ifdef statement as shown in our alternate transport here:
https://support.cpanel.net/hc/en-us/articles/360056322734-How-to-Use-Amazon-SES-as-a-Smarthost
Hopefully that gets you on the right path.
0
Please sign in to leave a comment.
Comments
1 comment