Hi there; just stumbled upon what I see as a bug and a source of issues; here's what I noticed
Sometimes, under certain conditions ASSP emits both a reject message (message score over limit), that is a "550 ..." *followed* by another SMTP tempfail "451 retry later" which comes from the graylisting; now, while this in *theory* shouldn't be a problem, since the sending party will just ignore the second message, it IS a problem for blockreport; basically here's what (I think) happens ASSP checks the messages through various filters, the score goes up to the limit so, it emits the "550" to reject the message, at that point, for whatever reason (possibly a bug), the "delaying" (graylisting) code kicks in, finds that the "tuple" isn't listed and decides to ALSO emit the "451" and at the *same time* this causes the rejected message to NOT BE SAVED into the spamfolder so, in effect a user willing to recover it, won't be able to do so. I think that, in case a given SMTP session gets a reject, the filtering should stop there and deal with the message, storing it as needed Note to Thomas: in case you'll need further details/infos, I may send your way some log snippet which shows the above behaviour ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
