Sean Mahrt wrote: > Can I use an auto whitelist with a decay feature? What I want to do is > allow auto whitelist with the automatically added entries to have a > date code behind them and if it has been past x > days/weeks/years/decades they need to reauthenticate.
If you have your whitelist in an SQL database and use to-sql/from-sql, I'd imagine that this would be fairly straightforward to set up. Assuming you use the regular flat file list, you could set something up that approximated this functionality. Flat file list lines can have inline comments: if you add " #" to a line, that token and everything after it are stripped before the email address is extracted (note that it must be space-pound, *not* tab-pound). You could have a process that read your whitelist once a day, adding expiration date comments to lines that don't have one, and removing lines that have expired date comments. You'd have to be careful: TMDA could receive a message and add an address while your script was also changing the file. Also note that there's a bug in the current release version of TMDA relating to comments and append lists: the comments aren't stripped before the lines are compared to decide whether the new email address already exists on the list. The bug has been fixed in CVS, and barring technical objections from Jason, the fix will be in the next release version. If you want to use comments in an append list, use the CVS version of the code, or email me for the patch. > It'd be great if every time I received a message it reassigned the > date, but I imagine that would be a ton of server load. That would require code changes (though possibly not if you use to-sql/from-sql). TMDA is in feature freeze right now, so even if there's interest in such a feature, it wouldn't be added until after 1.0 is out. Ed _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
