The problem: I have some customers at a law firm. Their messages invariably would evaluate as Spam; but usually all is well because they submit authenticated, and their recipients are whitelisted before they reply, but
Occasionally there is a breakdown in an ongoing conversation where a reply is blocked because the correspondent has replied from an unexpected place and, for instance, got a Blackberry generated SRS sender-id, or a new remote person joins the conversation The reply message often does not have an In-Reply -To: header I therefore propose to store hashes of the Subject right of all ':'s catenated with the Reply-To / From / Sender (all 3 if different) to act as a secondary whitelisting mechanism vs any inbound subject and recipient and wonder if anyone can suggest problems with this approach before I do any coding, and whether anyone else finds this a significant problem? Andrew Macpherson and...@oa5.com (Twitter @OA5dotCom) The Red Lion #5. Much Hadham. Herts SG10 6DD. GB Phone +44 1279 843147 GSM +44 78999 61797 ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
