While I think this is a good idea, I don't think the script I wrote
is appropriate. Parts of it may be useful, but it is very customized
for our installation. Not everyone uses the large-scale option for
instance. It shouldn't be too hard to write something that will
parse the dspam.conf file to pull DB settings and determine where the
dspam data is stored.
On Nov 20, 2005, at 6:53 AM, Toon van der Pas wrote:
> On Mon, Nov 14, 2005 at 07:01:43AM -0500, Pat Hennessy wrote:
>>
>> Don't forget to remove the user's dpsam data directory as well. I
>> wrote a perl script which takes the username and it determine's the
>> UID to delete the rows from the DSPAM DB. Then it deletes the
>> directories. Finally, it optimizes the tables.
>>
>> I could provide a copy if you want. It's not very complicated.
>>
>> On the same note, I also wrote a perl script to handle the purge. In
>> addition to doing the normal purge stuff, it will also remove the
>> users db and data files if they disable DSPAM (we have an opt-in
>> system). Pretty easy too. It just checks the opt-in preference and
>> deletes the stuff if it is set a certain way.
>
> In my opinion this is stuff of general interest.
> Every now and then the question about deleting users pops up on this
> mailing list. May I suggest that some scipts like yours are added to
> the standard dspam tar ball?
>
> Regards,
> Toon.
>
> Disclaimer: I'm still running dspam-3.4.5 myself and didn't check
> later versions for inclusion of such scripts. In case they are
> already included, please forget I ever wrote this email message.
>
> !DSPAM:438063e246555134674912!
>
-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pat Hennessy, RHCE (path@dtcc.edu) Information Systems Specialist Systems, Stanton/Wilmington Campus Delaware Technical and Community College =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Received on Sun Nov 20 11:08:03 2005
This archive was generated by hypermail 2.1.8 : Mon Nov 21 2005 - 00:00:00 EST