Re: [SM-USERS] locking down squirrel mail

2009-04-24 Thread jm
Thanks, you've been a great help. This worked a treat. Jeff. Paul Lesniewski wrote: > > $edit_identity > $edit_name > > config/conf.pl ==> 4. General Options ==> 9. Allow... > > >> Would still like to remove some option pages as well. eg, >> to remove the settings for "Reply To" and

Re: [SM-USERS] locking down squirrel mail

2009-04-23 Thread Paul Lesniewski
>>>  So far I've added a captcha, but this doesn't seem to help as much as >>> you'd think. >>> >> >> Make sure the backend you've chosen is a good one.  Some of them are >> relatively simple to hack.  Note also you can use it in combination >> with the User Information plugin to restrict the count

Re: [SM-USERS] locking down squirrel mail

2009-04-23 Thread jm
Paul Lesniewski wrote: >> So far I've added a captcha, but this doesn't seem to help as much as >> you'd think. >> > > Make sure the backend you've chosen is a good one. Some of them are > relatively simple to hack. Note also you can use it in combination > with the User Information plugi

Re: [SM-USERS] locking down squirrel mail

2009-04-23 Thread Paul Lesniewski
On Thu, Apr 23, 2009 at 6:25 PM, jm wrote: > In the wake of spam attacks I'm attempting to lock down squirrelmail as > much as possible while remaining usable for our customers (I work for an > ISP). >  So far I've added a captcha, but this doesn't seem to help as much as > you'd think. Make sure

[SM-USERS] locking down squirrel mail

2009-04-23 Thread jm
In the wake of spam attacks I'm attempting to lock down squirrelmail as much as possible while remaining usable for our customers (I work for an ISP). So far I've added a captcha, but this doesn't seem to help as much as you'd think. In order to make it easier to at least track down the source