[...] > I'll revert my currently done code changes. ASSP should not allow any > SMTP misbehave - how ever, this check could be disabled in the next > release by setting 'etValencePB' to zero.
I agree with you; it sounds like the issue is due to a ThunderBird bug and, changing the ASSP code to let it deal with such a bug doesn't seem a good idea to me; it would be a better idea to report the bug to the TB developers so that they may investigate it and issue a fix; the only other way to "safely" apply a workaround to such a bug (but again, I don't think it's needed) would have been to postpone the "early talker" check/reject at a later stage, that is, record it at beginning, wait to see if the client will authenticate and, if not, reject the connection as an "earlytalker"; this would allow an auth (but buggy) client to work but, again, I don't think ASSP is here to fix bugs in other software :D ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
