Scott Jibben E-Mail SignatureAs long as all mail sent from that domain can only come from the servers in your MX records, then you’re good.
I would only use SPF in one, SM or Declude, not both. We have it in Declude, which is in control of our weighting system. Personally I would not want to maintain two separate weighting systems. As for the weights, I don’t know what your hold weight is, so I can’t say whether that would be appropriate. On our systems we do not give any credence to passing SPF. We do add weight for SPF fail, just under our hold weight, so SPF fail along with any other fail will result in hold. Our hold weight is set to 100 so it makes it easy to think in percentages for test weights, and also gives granularity for fine tuning tests. Darin. From: Scott Jibben Sent: Thursday, January 16, 2014 6:54 PM To: [email protected] Subject: [MBF]Re: Deleting messages from non-existent local accounts Thanks Darin, I think that I have the SPF record figured out. I came up with: v=spf1 mx -all Only the MX servers should be allowed to send mail. I have -2 for pass and +5 for pass in SmarterMail. In global.cfg it is -1 for pass and +8 for fail. Is my system checking this twice? Should I turn it off in SmarterMail? Are these good weights for pass/fail? sj Scott Jibben [email] [email protected] [web] http://runspot.net [voice] 763.551.2510 [toll free] 866.635.7299 On 1/15/2014 3:28 PM, Darin Cox wrote: SPF is perfect for this. Define your SPF policy in DNS for what servers can send mail for the domains you host, and set the weight for SPF failure appropriately in your Declude config. See www.openspf.org for more info on setting up the DNS records if you are not familiar with it. Note that passing SPF is not a guarantee of good mail, and many organizations fail their own SPF policies, so failure doesn’t always mean bad mail, but for forging mail SPF works great. Darin. From: Scott Jibben Sent: Wednesday, January 15, 2014 3:54 PM To: [email protected] Subject: [MBF]Deleting messages from non-existent local accounts Hello, I'm using SmarterMail 11.7 + declude + MBF. We sometimes get mail from non-existent local accounts. For example, the return email account is fake; like [email protected] and it get sent to valid email accounts on the mail server. Is there a way to detect? 1. That the return email account is local to the mail server 2. The local account does not exist Then just delete these messages because they are probably spam. Thanks, -- sj Scott Jibben [email] [email protected] [web] http://runspot.net [voice] 763.551.2510 [toll free] 866.635.7299
<<RunSpot-signature.png>>
<<image/png>>
