| So if I understand you correctly: + Its hard to manipulate things on the RHS + It's more work to auto-generate email addresses + There are benefits to requiring that users submit structure email addresses (e.g. /EVENT) mostly relating to wedding out SPAM Given these 3 things: + Why don't we ix-nay the RHS stuff. I agree it's more elegant, but not a must-have? + That leaves us with a user-defined LHS, which would rule out using the LHS to define the Kind of item you would like to submit (e.g. [EMAIL PROTECTED]) + However, since structured email is more desirable from a security standpoint anyway, let's try out forcing users to have something like: /EVENT, /TASK in the Subject line. (Is that enough structure? or Do we need more?) + Question: If there is no /EVENT or /TASK in the subject line, can we accept the submission just as a Note or Communications item? It would minimize the risk of SPAM since Chandler wouldn't recognize it as an event. + If we require a particular structure in order to recognize email submissions as events and tasks, do you feel we still need to implement quarantining and/or whitelisting right away? :o) Mimi On Jul 26, 2006, at 1:16 PM, Jared Rhine wrote:
|
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
