Hi, > I had to add a rule weight for this rule to get it to trigger, so > evidently the latest ML rules weights have disabled this rule. > > Anyway, this is what triggered it: > >> <a href=3D"https://www.google.com/url?q=3Dhttps%= >> 3A%2F%2Fglobal.gotomeetinA.com%2Fjoin%2F726265509&sa=3DD&usd=3D2&am= >> p;usg=3DAFQjCNHlVtBtL2J4tx-l3Ej-YPjED9EKjA" target=3D"_blank">https://globa= >> l.gotomeetinB.com/join/726265509</a> > > (Note that I altered the domains so that I could tell which triggered > the rule.)
Thanks so much for your efforts. > Now I've given a more thorough analysis to that code (I'm not a perl > programmer by any means), I realized what it's actually doing is > comparing the _domain_ of the text to the domain of the anchor. If the > two don't match (e.g. the link text is for gotomeeting.com but the link > goes to google.com), the rule triggers. The http/https is misleading. I thought there were already other rules that perform similar functions, although I can't remember their names right now. Maybe there is a perl programmer with ideas and interest in improving this... > Unfortunately, it's all too common nowadays for emails to include a link > click-through redirect domain hidden in the anchor tag. I personally > hate this, but it can't really be considered a sign of spam anymore > since too many legitimate emails do it. This definitely is a common practice. > I would probably zero-weight this rule. I think the rule still has a use, perhaps in a meta or something.
