SRS or not?

dzamanakos

• October 17, 2017 05:57

Hi, i have a question about Enable Sender Rewriting Scheme (SRS) Support. Many customers forward their emails from our servers to other external (like yahoo, google, other etc) Sometimes these emails are delivered to spam folders as they fail spf check. In order to improve deliverability i've changed SRS to on, on tweak settings. Now all emails a local user receives (along with spam emails) and then forwarded to gmail for example, have headers that seems that are originated from my ips. This is a risk as gmail or any other server may think my server send spam. Does the headers that my local spamassassin add and flag the email as spam helps gmail to not add me as a spammer? Or does a changed subject that contains the word SPAM helps? I'm also planning to deploy mailscanner. Does it's headers/subject will help that too? i've noticed that mailscanner's headers are different than spamassassin. Reading about, i didnt find any standard rules (headers/subject) that a remote mailserver will not add me as spammer, by telling: server A (my server) send a spam email to me but it has a header Spam:True so it's not a spammer, it's a forwarded email. Is it better with SRS and this risk, or with SPF and fail check? What's your expirience on that? Thank you in advance,

• 

  cPWilliamL

  • October 17, 2017 14:11

  Hi, This really depends on Google's mail practices when receiving mail, which they don't make all that clear. Really, your users shouldn't be using forwards in this manner. The best method to pass mail along to another provider is to allow it to fetch over POP. This will ensure 100% delivery and prevent any reputation issues with your server. Gmail has the following documentation on this: Check emails from other accounts - Computer - Gmail Help Otherwise, you may consider using the 'Scan outgoing messages for spam...' features at WHM > Service Configuration > Exim Configuration Manager. Exim Configuration Manager - Basic Editor - Version 66 Documentation - cPanel Documentation Thanks,

  0
• 

  dzamanakos

  • October 17, 2017 14:38

  I may consider disabling SRS, as scanning outgoing for spam may not change anything because before forward a message, spamassassin already checked it when received and flagged them (or am i wrong?)

  0
• 

  cPWilliamL

  • October 17, 2017 15:15

  The flag is likely added on inbound checks, then kept when forwarded. The outgoing spam scan will prevent it from being forwarded altogether, should it exceed the specified spam score.

  0
• 

  legalbrr

  • January 21, 2020 13:57

  This really depends on Google's mail practices when receiving mail, which they don't make all that clear.

  
  Not quite true. Google supports mail forwarding, and tells us the right way to do it.

  0
• 

  coursevector

  • April 23, 2020 16:44

  Short answer: As Google Specs, you should use SRS to avoid reputation issues.

  
  That is the exact opposite of what Google Specs recommend: Ownership and Filtering We recommend that you do not change the envelope sender when forwarding email to Gmail. Sometimes, when forwarding email, the envelope sender gets changed to your domain. When this happens, Gmail may learn that your domain is sending spam, and will treat other emails from this domain as spam as well.
  Which says Google does NOT want you to use SRS.

  0

Please sign in to leave a comment.