On Tue, 2015-05-19 at 14:38 -0400, Alex Regan wrote:
> I've got more than a dozen now. It's a regular thing. I was just trying
> to somehow gain support for somehow being more proactive with these.
>
Here are a couple of ideas that may help. Both use lists of alternate
patterns, i.e. body RULE /
Hi,
On 05/19/2015 11:40 AM, Reindl Harald wrote:
Am 19.05.2015 um 17:11 schrieb Alex Regan:
I'm wondering if anyone is interested in helping to develop a set of
rules to catch SEO spam? Here's one such example:
http://pastebin.com/S6Jeappj
It's those emails that talk about how they can impro
Am 19.05.2015 um 17:11 schrieb Alex Regan:
I'm wondering if anyone is interested in helping to develop a set of
rules to catch SEO spam? Here's one such example:
http://pastebin.com/S6Jeappj
It's those emails that talk about how they can improve your SEO such as:
..."diverse projects consisti
On 19.05.2015 17:11, Alex Regan wrote:
Hi,
I'm wondering if anyone is interested in helping to develop a set of
rules to catch SEO spam? Here's one such example:
http://pastebin.com/S6Jeappj
It's those emails that talk about how they can improve your SEO such as:
..."diverse projects consisti
Hi,
I'm wondering if anyone is interested in helping to develop a set of
rules to catch SEO spam? Here's one such example:
http://pastebin.com/S6Jeappj
It's those emails that talk about how they can improve your SEO such as:
..."diverse projects consisting of SEO, PPC, SMM, Affiliate
Marketi
Meta rules on not spf pass or not dkim valid
Whitelist_auth *@example.org
meta forged_sender_not_pass ((!spf_pass || !dkim_valid_au) && (!user_in_*)
Will be unneeded when dmarc is a spamassassin plugin, until then only
something like above is possible, just exspand it to specific domain, above
