From: <bil...@gr...> - 2005-07-31 03:58:49
|
At 8:01 PM -0700 7/30/05, Theo Aukerman wrote: > > [mailto:ass...@li...] On Behalf Of >> bil...@gr... >> Sent: Friday, July 29, 2005 10:15 PM >> >> At 10:39 AM -0700 7/29/05, Theo Aukerman wrote: >> >So, to fix this downside, spam that is blocked due to LDAP should to >> >into the spam collection. >> >> But wouldn't that also send any legitimate mail which was directed to >> any no-longer-in-service address to the spam collection? Don't you >> folks experience any user turnover? > >Regardless of user turnover, if the user is not in your LDAP lookup, the >mail won't get delivered. Therefore, it is not legitimate. If the mail >were legitimate, we would have kept the email in our LDAP directory, and >forwarded the mail to someone. You're splitting hairs. No it's not technically legitimate mail to a current user. However it could easily be (and often is) mail which is not spammy in content and should not be considered spam, as other legit users on the system expect mail of this type and expect it to come through (sometimes duplicate copies of the same, as in mailing list email). If I were to leave, for instance, then all email from this list and many others would be funnelled into the spam corpus. Presumably the person who takes over this position would join the list(s), and list messages to them would be rejected as spam. Granted, they should be able to figure out what's up and fix it with a whitelist entry, but what if a similar scenario happens with a "normal" user? > >Anyway, it seems possible that not ALL LDAP users would want failed LDAP >lookups to populate their spam corpus, but if we want to have our cake >and eat it too, having the spambucket check occur PRIOR to the LDAP >lookup would give us a little more flexibility. Maybe it's just been a long day and I'm not getting it, but I don't see how that would solve my scenario above: List mail comes in, checks as good against spam db, fails LDAP on the expired user, and gets added to spam db. Next list mail comes in, fails check against spam db, and the legit mail to legit user gets bounced. Sounds like you'd be messing up your spam db pretty quickly to me. -- Bill Christensen <http://greenbuilder.com/contact/> Green Building Professionals Directory: <http://directory.greenbuilder.com> Sustainable Building Calendar: <http://www.greenbuilder.com/calendar/> Green Real Estate: <http://www.greenbuilder.com/realestate/> Straw Bale Registry: <http://sbregistry.greenbuilder.com/> Books/videos/software: <http://bookstore.greenbuilder.com/> |