Upon further investigation, this actually appears to be a problem with Outlook. I don't know of a fix for it. I did, however, find a discussion of the problem in another forum: http://www.office-outlook.com/outlook-forum/index.php/m/255091/
So, it might be worth it to consider modifying the Regex (validMsgIDRe) to validate the message-ID format so as not to flunk email clients that don't know what standards are, yet are still popular. Evolution mail is looking better and better all the time... - Phil -----Original Message----- From: Phil Quesinberry [mailto:[email protected]] Subject: RE: Message Scoring Mode Ok, correction on the message id... some further investigation reveals that the problem appears to be on my end, not Verizon's so I'll have to figure that one out. I stand behind the rest of my message though. :) (Message-ID not valid: '004701cb421c$ff9fc790$fedf56...@com') - Phil -----Original Message----- From: Phil Quesinberry Subject: Message Scoring Mode Hi Dale, Under "Message Scoring" MessageScoring Lower Limit (MessageScoringLowerLimit,default=47) (MessageScoring will tag messages with totalscore higher than this limit and not higher than MessageScoringUpperLimit. For example: 47) MessageScoring Upper Limit (MessageScoringUpperLimit) (If MessageScoring is done to block, it will block messages whose totalscore is higher than this threshold. For example: 50) The messages will be tagged with text from the following setting: Warning Tag (MessageScoringWarningTag) (Used if totalscore is higher than MessageScoringLowerLimit and not higher than MessageScoringUpperLimit. For example: [?]) In my case, I set the limits to 39 and 50 and changed the tag text to [Possible SPAM]. This makes it easy for the users to decide manually for themselves or to set up rules in Outlook to move it to a junk suspects folder. Very few messages wind up being tagged this way though. Generally, they either make it or they don't. Based upon the emails you and I have sent back and forth, I think that one of the biggest problems you're having is that your ASSP is still weighting the sorbs list as =>1 or =>50, despite the fact that you changed it to =>2, and sorbs has apparently blacklisted a bunch of Verizon's servers for backscatter. That, combined with the fact that ASSP doesn't seem to like Verizon's message IDs, means that a lot of Verizon mail is potentially going to be tagged or rejected. Phil Quesinberry Q Systems Engineering, Inc. Electronic Controls and Embedded Systems Development http://www.qsystemsengineering.com ---------- Dale wrote: Hi I had to remove blocking in Message Scoring Mode because people were complaining about not receiving emails Now they are complaining too many are being tagged. :) How or what do I set for messages over a certain threshold to be deleted? Thanks Dale ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
