> Hi all,
> I've just installed squirrelmail 1.4.4 (debian package). It's accessed
> through apache 1.3.33 via HTTPS. Everything works wonderfully, but some
> folders can't be accessed (they are quite big: ~3k - 30k messages each).
> When I click on one of these folders on the folder menu on the le
>> A security flaw has been identified in the (local) vacation plugin
>>(currently version 0.15,
>>http://www.squirrelmail.org/plugin_view.php?id=51), not to mention the
>>fact that it is sorely out of date and contains some very dirty code. I
>>am currently working through a thorough
Hi all,
I've just installed squirrelmail 1.4.4 (debian package). It's accessed
through apache 1.3.33 via HTTPS. Everything works wonderfully, but some
folders can't be accessed (they are quite big: ~3k - 30k messages each).
When I click on one of these folders on the folder menu on the left, the
p dont think wrote:
That particular plugin will sort the mail when you log in. One of the
"that particular..."?? He didn't even mention a plugin name. More
importantly, please don't confuse people here: there is in fact a plugin
called "Server Side Filter" that will allow you to manage procmail
Howdy,
I've just got a quick and most likly very easy question, i'm looking at
forwarding all mail marked as Spam to a IMAP Folder.
What i need to figure out is how to setup SM configuration to create a
Spam folder by Default when a user account is created.
Regards,
Michael
--
> I am accessing with regular http
> Here is the properties of the page where I got the action cancelled.
>
> res://C:\WINNT\system32\shdoclc.dll/navcancl.htm#https://www.ptera.net:80/we
> bmail/src/right_main.php?mailbox=INBOX&sort=0&startMessage=1
Tada ;) Notice the https:// bit, and then the p
I am accessing with regular http
Here is the properties of the page where I got the action cancelled.
res://C:\WINNT\system32\shdoclc.dll/navcancl.htm#https://www.ptera.net:80/we
bmail/src/right_main.php?mailbox=INBOX&sort=0&startMessage=1
- Original Message -
From: "Jonathan Angliss" <[
> Thank you! Is there information about this i18n version that I can view
> online? Like what languages it supports. And exactly what this means in
> relation to the Squirrelmail interface?
You are welcome. I suggest you start reading about it on the squirellmail
website (listed at the bottom o
Jonathan Angliss wrote:
[Wed Jan 26 09:33:25 2005] [error] [client 69.28.32.138] Invalid method
in request \x80L\x01\x03
[Wed Jan 26 09:33:25 2005] [error] [client 69.28.32.138] Invalid method
in request \x80L\x01\x03
The other server I have (same os) which I have not upgraded does not do
this.
I
On Feb 1, 2005, at 6:04 AM, p dont think wrote:
You only need to post your message once, thanks.
Sorry about that. The second message to arrive was actually sent a
couple of hours earlier than the other. I assumed it was blocked
because it was sent from an account other than the one I signed up
[Wed Jan 26 09:33:25 2005] [error] [client 69.28.32.138] Invalid method
in request \x80L\x01\x03
[Wed Jan 26 09:33:25 2005] [error] [client 69.28.32.138] Invalid method
in request \x80L\x01\x03
The other server I have (same os) which I have not upgraded does not do
this.
>>>
Thank you! Is there information about this i18n version that I can view
online? Like what languages it supports. And exactly what this means in
relation to the Squirrelmail interface?
Also, are there any caveats I should be aware of if I decide to go with
the i18n version of the RPM if my previo
Please reply to the list, not me. Also, please do not top-post. Thanks,
I recently upgraded squirrelmail using yum to version 1.4.3a-6.FC3
Sometimes when signing in they get the Folders View in both frames.
And when customers send emails instead of returning to their INBOX they
get
Action cancel
Well, then you solve the problem. It's not as easy as you think. Just
ask Jonathan. ;) It's not a matter of PHP "just handling it" for you.
The browser is too dumb to know that each window/tab you have open
should be using a different session cookie. The problem has been known
for a couple ye
>> Well, then you solve the problem. It's not as easy as you think. Just
>> ask Jonathan. ;) It's not a matter of PHP "just handling it" for you.
>> The browser is too dumb to know that each window/tab you have open
>> should be using a different session cookie. The problem has been known
>> f
p dont think wrote:
Trying to move from 1.4.2 to 1.4.4 the following plugins have
problems with either setpref() or getpref() being undefined - seems
an include_once or require_once of functions/prefs.php is missing or
they are no longer compatible.
show_user_and_ip 2.2.3
timeout_user
> A quick question. I'm about to upgrade to 1.4.4 from 1.4.3a. I plan to
> use the RPMs. But when I went to download there were two versions of the
> 1.4.4 RPM:
>
> squirrelmail-1.4.4-1.noarch.rpm
> and
> squirrelmail-i18n-1.4.4-1.noarch.rpm
>
> Can someone tell me what the difference, besides t
A quick question. I'm about to upgrade to 1.4.4 from 1.4.3a. I plan to
use the RPMs. But when I went to download there were two versions of the
1.4.4 RPM:
squirrelmail-1.4.4-1.noarch.rpm
and
squirrelmail-i18n-1.4.4-1.noarch.rpm
Can someone tell me what the difference, besides the 3MB, between t
>
> CentOS 3.4 (think RHEL 3), with Apache 2.0.52, SquirrelMail 1.4.4, PHP
> 4.3.10 compiled from source using qmailrocks.org instructions.
>
> All seems to work except that I have to enter "http:///webmail/"
> (with a trailing slash) into the browser's address bar to get the
> SquirrelMail login s
> Well, then you solve the problem. It's not as easy as you think. Just
> ask Jonathan. ;) It's not a matter of PHP "just handling it" for you.
> The browser is too dumb to know that each window/tab you have open
> should be using a different session cookie. The problem has been known
> for
John Madden wrote:
One other possibility is that you had more than one SM session open at
once in the same browser (to two or more different users); SM does not
yet support such use of the software.
Well of course, this happens ALL the time
eh?
-- load-balanced web servers
tend to do that. With
> One other possibility is that you had more than one SM session open at
> once in the same browser (to two or more different users); SM does not
> yet support such use of the software.
Well of course, this happens ALL the time -- load-balanced web servers
tend to do that. With three browser fram
I upgraded to v1.4.4 last night and while I'm quite impressed with its
performance improvements over previous versions (last used v1.2.8), I've had
one shockingly bad thing happen *twice* today: While working in the
application, my pref's file has been wiped out. Emptied. Lost.
To explain our set
Below is a complete copy of the error messages I receive whenever I try
to access my webmail using Squirrel Mail.
Can you please reply to me at this email address & let me know what
these error messages mean exactly & what I have to do in order to fix
them so that I can access my emails again.
I recently upgraded squirrelmail using yum to version 1.4.3a-6.FC3
Sometimes when signing in they get the Folders View in both frames.
And when customers send emails instead of returning to their INBOX they get
Action canceled
Internet Explorer was unable to link to the Web page you requested.
I change my question: is gpg plugin is supporting php version
4.3.10: it
seems that this version of php does not accept global definition
variable.
I can't recover. I tried this kind of solulution: adding to
/etc/httpd/conf.d/ssl.conf:
php_admin_value register_globals 1
change the following in /et
You only need to post your message once, thanks.
We've been using SquirrelMail at work for a couple of years now with no
issues. A couple of weeks ago I started getting complaints about weird
warning messages showing up in the left hand mailbox list or on the
right above the message list.
Your r
p dont think wrote:
>All,
>
> A security flaw has been identified in the (local) vacation plugin
>(currently version 0.15,
>http://www.squirrelmail.org/plugin_view.php?id=51), not to mention the
>fact that it is sorely out of date and contains some very dirty code. I
>am
First off, this appears to be a problem that others have experienced before:
http://sourceforge.net/mailarchive/forum.php?thread_id=3384077&forum_id=2995
http://article.gmane.org/gmane.mail.squirrelmail.devel/5217
But no solutions posted in any threads I found besides "check the SM
requirements".
CentOS 3.4 (think RHEL 3), with Apache 2.0.52, SquirrelMail 1.4.4, PHP
4.3.10 compiled from source using qmailrocks.org instructions.
All seems to work except that I have to enter "http:///webmail/"
(with a trailing slash) into the browser's address bar to get the
SquirrelMail login screen to app
30 matches
Mail list logo
