>>> Installed Plugins
>>> 1. delete_move_next
>>> 2. squirrelspell
>>> 3. newmail
>>> 4. mpppolicygroup
>>> 5. quota_usage
>>>
>>> Available Plugins:
>>> 6. translate
>>> 7. compatibility
>>> 8. spamcop
>>> 9. sent_subfolders
>>> 10. check_quota
>>
>> Ver
Tomas Kuliavas wrote:
> Tim Hogan wrote:
>
>>
>> Tomas Kuliavas wrote:
>>
>>> Tim Hogan wrote:
>>>
>>>
I have decided to give SquirrelMail a try and I have install v1.4.11
which seems to be working quite well, with the exception of spell
checking. Whether I am go
On 10/9/07, Paul Lesniewski <[EMAIL PROTECTED]> wrote:
> On 10/9/07, Nick Bright <[EMAIL PROTECTED]> wrote:
> > Paul Lesniewski wrote:
> > > Please do NOT top-post and try to use correct reply quoting.
> > >
> > > On 10/9/07, Brent <[EMAIL PROTECTED]> wrote:
> > >> I had this exact issue. It ended
On 10/9/07, Nick Bright <[EMAIL PROTECTED]> wrote:
> Paul Lesniewski wrote:
> > Please do NOT top-post and try to use correct reply quoting.
> >
> > On 10/9/07, Brent <[EMAIL PROTECTED]> wrote:
> >> I had this exact issue. It ended up being one exploited account. The IP
> >> addresses connecting
>>On 10/9/07, Brent <[EMAIL PROTECTED]> wrote:
>> I had this exact issue. It ended up being one exploited account. The IP
>> addresses connecting to the account were from various APNIC blocks. I
would
>> block one IP and it would move to another... suggesting that it was some
>> kind of bot - ho
Paul Lesniewski wrote:
On 10/9/07, Nick Bright <[EMAIL PROTECTED]> wrote:
Paul Lesniewski wrote:
On 10/9/07, Ken A <[EMAIL PROTECTED]> wrote:
Nick Bright wrote:
Ken A wrote:
Nick Bright wrote:
Per some suggestions in the thread I was able to determine that they are
not using "mailto.php",
Paul Lesniewski wrote:
Please do NOT top-post and try to use correct reply quoting.
On 10/9/07, Brent <[EMAIL PROTECTED]> wrote:
I had this exact issue. It ended up being one exploited account. The IP
addresses connecting to the account were from various APNIC blocks. I would
block one IP an
Nick Bright wrote:
> Ken A wrote:
>> Nick Bright wrote:
>>> Tomas Kuliavas wrote:
>>
Have you tried to protect your webmail traffic? Signed SSL certificate
costs less than 20 USD.
>>> I'd expect they support SSL on their end, this probably wouldn't make
>>> any difference.
>>
>> The diff
Brent wrote:
> I had this exact issue. It ended up being one exploited account. The IP
> addresses connecting to the account were from various APNIC blocks. I would
> block one IP and it would move to another... suggesting that it was some
> kind of bot - however, I added the captcha plugin and
Please do NOT top-post and try to use correct reply quoting.
On 10/9/07, Brent <[EMAIL PROTECTED]> wrote:
> I had this exact issue. It ended up being one exploited account. The IP
> addresses connecting to the account were from various APNIC blocks. I would
> block one IP and it would move to a
Ken A wrote:
Nick Bright wrote:
Tomas Kuliavas wrote:
Have you tried to protect your webmail traffic? Signed SSL certificate
costs less than 20 USD.
I'd expect they support SSL on their end, this probably wouldn't make
any difference.
The difference is that fewer passwords could easily be
On 10/9/07, Nick Bright <[EMAIL PROTECTED]> wrote:
> Paul Lesniewski wrote:
> > On 10/9/07, Ken A <[EMAIL PROTECTED]> wrote:
> >> Nick Bright wrote:
> >>> Ken A wrote:
> Nick Bright wrote:
>
> > Per some suggestions in the thread I was able to determine that they are
> > not using
Nick Bright wrote:
> Tomas Kuliavas wrote:
>> Have you tried to protect your webmail traffic? Signed SSL certificate
>> costs less than 20 USD.
>
> I'd expect they support SSL on their end, this probably wouldn't make
> any difference.
The difference is that fewer passwords could easily be stol
I had this exact issue. It ended up being one exploited account. The IP
addresses connecting to the account were from various APNIC blocks. I would
block one IP and it would move to another... suggesting that it was some
kind of bot - however, I added the captcha plugin and they kept logging in!
Paul Lesniewski wrote:
On 10/9/07, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
CentOS 4.5 w/ squirrelmail-1.4.8-4.0.1.el4.centos. Plugins are:
CVE-2006-6142, CVE-2007-1262, CVE-2007-2589. Please note that html
filtering functions must be patched to 1.4.10+ level. Having only 1.4.9a
patches is not
Paul Lesniewski wrote:
On 10/9/07, Ken A <[EMAIL PROTECTED]> wrote:
Nick Bright wrote:
Ken A wrote:
Nick Bright wrote:
Per some suggestions in the thread I was able to determine that they are
not using "mailto.php", but rather compose.php:
/var/log/httpd/access_log:196.1.179.183 - - [07/Oct
Tomas Kuliavas wrote:
CentOS 4.5 w/ squirrelmail-1.4.8-4.0.1.el4.centos. Plugins are:
CVE-2006-6142, CVE-2007-1262, CVE-2007-2589. Please note that html
filtering functions must be patched to 1.4.10+ level. Having only 1.4.9a
patches is not enough. If changelog says that CVE-2006-6142 is fixed,
Ken A wrote:
Nick Bright wrote:
Ken A wrote:
Nick Bright wrote:
Per some suggestions in the thread I was able to determine that they are
not using "mailto.php", but rather compose.php:
/var/log/httpd/access_log:196.1.179.183 - - [07/Oct/2007:21:54:10 -0500]
"GET /webmail/src/compose.php?mail
On 10/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I'm not able to CC or add additional addresses when sending email. It
> gives me a new window. How can I set this back to default?
You are using a very very old version of SquirrelMail. Please upgrade
before trying anything else. If the
On 10/9/07, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
> > CentOS 4.5 w/ squirrelmail-1.4.8-4.0.1.el4.centos. Plugins are:
>
> CVE-2006-6142, CVE-2007-1262, CVE-2007-2589. Please note that html
> filtering functions must be patched to 1.4.10+ level. Having only 1.4.9a
> patches is not enough. If cha
On 10/9/07, Ken A <[EMAIL PROTECTED]> wrote:
> Nick Bright wrote:
> > Ken A wrote:
> >> Nick Bright wrote:
> >>
> >>> Per some suggestions in the thread I was able to determine that they are
> >>> not using "mailto.php", but rather compose.php:
> >>>
> >>> /var/log/httpd/access_log:196.1.179.183 -
> CentOS 4.5 w/ squirrelmail-1.4.8-4.0.1.el4.centos. Plugins are:
CVE-2006-6142, CVE-2007-1262, CVE-2007-2589. Please note that html
filtering functions must be patched to 1.4.10+ level. Having only 1.4.9a
patches is not enough. If changelog says that CVE-2006-6142 is fixed,
check functions/mime.p
Nick Bright wrote:
> Ken A wrote:
>> Nick Bright wrote:
>>
>>> Per some suggestions in the thread I was able to determine that they are
>>> not using "mailto.php", but rather compose.php:
>>>
>>> /var/log/httpd/access_log:196.1.179.183 - - [07/Oct/2007:21:54:10 -0500]
>>> "GET /webmail/src/compose.
Ken A wrote:
Nick Bright wrote:
Per some suggestions in the thread I was able to determine that they are
not using "mailto.php", but rather compose.php:
/var/log/httpd/access_log:196.1.179.183 - - [07/Oct/2007:21:54:10 -0500]
"GET /webmail/src/compose.php?mail_sent=yes HTTP/1.1" 200 37102
"htt
I'm not able to CC or add additional addresses when sending email. It
gives me a new window. How can I set this back to default?
I subscribe to the squirrelmail-users mailing list.
[ ] True - No need to CC me when replying
[ ] False - Please CC me when replying
This bug occurs when I
On Mon, October 8, 2007 20:38, Nuno Parreira wrote:
| Hi Dear Sirs,
| My name is Nuno, i'm writing you regarding a problem that i have with the
| Squirrel Email interface. I really don't know if this is the correct email
| to put this kind of problems (probably not), but i try to find everywhere
|
Sorry to reopen a thread, but I am seeing the same issue as the original
poster in this thread:
http://sourceforge.net/mailarchive/message.php?msg_id=c11d02530709050557ldb78519i4cdecd1ea08dc368%40mail.gmail.com
In that I am seeing spam sent through my SM install, packages are:
CentOS 4.5 w/ squi
Nick Bright wrote:
> Per some suggestions in the thread I was able to determine that they are
> not using "mailto.php", but rather compose.php:
>
> /var/log/httpd/access_log:196.1.179.183 - - [07/Oct/2007:21:54:10 -0500]
> "GET /webmail/src/compose.php?mail_sent=yes HTTP/1.1" 200 37102
> "http://
Fredrik Jervfors wrote:
Matt wrote:
On 9/7/07, Chris Hoogendyk <[EMAIL PROTECTED]> wrote:
Matt wrote:
Do you have any proof of a virus logging in? Couldn't it just be
plain ol' keyboard logging and the the person who gets the logs
(not your intended
users) sends out the spam manually? It's tec
Hi all!
After sending an email with squirrelmail i get a 404. Nevertheless the mail is
sent and when i reload the page i return to the inbox view.
This appears in the apache log:
1.2.3.4 - - [09/Oct/2007:10:02:10 +0200] "GET /etc/squirrelmail//squirrelmail/
src/right_main.php?mailbox=INBOX&sort=0
30 matches
Mail list logo
