Microsoft Forefront marks 'track' as SPAM
-
This weekend I had to send some mail, but the shared server that I usually use was blacklisted, so I set up an alternative SMTP-server on our dedicated host.
Even from the non-blacklisted IP-address there still was an issue with KNews-mailings ending up in the unwanted e-mail of my Exchange-account when I send them with the scheduler, and not when I send them manually.
The mailheader-difference was:
X-Forefront-Antispam-Report: CIP:?.?.?.?;CTRY:?;IPV:NLI;EFV:NLI;SFV:SPM;SFS:
versus
CIP:?.?.?.?;CTRY:?;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:I found out that the mails sent are sent differently by
/wp-content/plugins/knews/direct/knews_cron_do.php
which puts some tracking URL’s in the final mail.I commented out the foreach on line 97 to make this job send the mail equal to the manual mail, and the SPAM-score lowered to NSPM, so the mail ended up in my inbox again.
As the visit-statistics are not visible in the free version I don’t think we will miss much, so a control to put the tracking off in the final mail would come in handy.
- The topic ‘Microsoft Forefront marks 'track' as SPAM’ is closed to new replies.