Hello,
Sorry, I am not very much familiar with Squirrelmail yet.
I am testing the restrict_senders plugin. An user has just been banned. I go
to the file where the user preferences are stored for the web mail, and I
open the file:
user.pref
There is :
USER_IS_POSSIBLE_SPAMMER=1
I deleted that
eva-8 wrote:
>
> Hello,
>
> Sorry, I am not very much familiar with Squirrelmail yet.
>
> I am testing the restrict_senders plugin. An user has just been banned. I
> go
> to the file where the user preferences are stored for the web mail, and I
> open the file:
>
> user.pref
>
> There is :
>
Hi Guys,
This is probably a simple question - but I'm not sure if there is a
simple answer :)
Basically I have a RedHat box running Squirrelmail with one primary
network interface (eth0)
and multiple logical interfaces (eth0:1, eth0:2, etc.) with separate IP
addresses assigned to each
of them.
On Fri, Mar 4, 2011 at 2:49 PM, Andrew Daviel wrote:
>
> For some odd reason we had a couple of accounts that had no password, but
> had the shell set to /sbin/nologin on Linux. So you can't shell
> in.
>
> However, Squirrelmail can login using any random password. (leaving the
> password field em
one possible solution -
http://blog.nachtarbeiter.net/2008/08/21/binding-phps-fsockopen-to-a-specific-ip-address/
So, you'd need to make some changes in: functions/imap_general.php and
test to see if it worked..
Or, if you don't mind all of your outgoing traffic to your imap server
going out th
Thanks! That was it :)
On 7 March 2011 17:59, Tomas Kuliavas wrote:
>
>
> eva-8 wrote:
> >
> > Hello,
> >
> > Sorry, I am not very much familiar with Squirrelmail yet.
> >
> > I am testing the restrict_senders plugin. An user has just been banned. I
> > go
> > to the file where the user preferen
