Hello Charles J Bujold,
On Sunday, May 29, 2005, you wrote:
> Further update on the issue. The problem only occurs if an e-mail bigger
> than 30K is present in the inbox. If all e-mails are less than 30K the
> problem does not exist. Is there a place where I have to set what is the
> size allow
Bujold
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Charles J BujoldSent: May 29, 2005 12:51 PMTo:
squirrelmail-users@lists.sourceforge.netSubject: [SM-USERS]
Squirrelmail 1.4.4. error when opening Inbox - Error 10 processing FETCH
command.
I' have been running Squirre
I' have been running Squirrelmail
version 1.4.4, windows 2003, IIS6, Mercury 4.01b for some time. I got a
hardware problem and fixed it and now Squirrelmail does not want to work
properly. All other aspects of Squirrelmail work properly except when you
try to access the Inbox. it shows th
>>> >> can you test 'host' => 'ldaps://ldap.antagonism.org' setting?
>>> I tried this setting and received the same error message. I even tried
> this setting with port 389 and protocol 3 to see if TLS would start and
> still received the same error.
>>
>> TLS on 389 is not SSL on 636. The fact th
> man, 18.04.2005 kl. 12.39 skrev marlowe:
>
> [...]
>
> You *HAVE* to reply to the list.You have *NOT* to reply to me
> personally.
My apologies. I did not verify that the reply to was set to the
squirrelmail list. That was my fault.
>
>> >> can you test 'host' => 'ldaps://ldap.antagonism.org'
> man, 18.04.2005 kl. 12.39 skrev marlowe:
>
> [...]
>
> You *HAVE* to reply to the list.You have *NOT* to reply to me
> personally.
My apologies. I did not verify that the reply to was set to the
squirrelmail list. That was my fault.
>
>> >> can you test 'host' => 'ldaps://ldap.antagonism.org'
man, 18.04.2005 kl. 12.39 skrev marlowe:
[...]
You *HAVE* to reply to the list.You have *NOT* to reply to me
personally.
> >> can you test 'host' => 'ldaps://ldap.antagonism.org' setting?
>
> I tried this setting and received the same error message. I even tried
> this setting with port 389 an
man, 18.04.2005 kl. 10.31 skrev Tomas Kuliavas:
> > I am attempting to connect to an openldap addressbook over SSL from
> > Squirrelmail. When I connect over the traditional port 389, I am able to
> > make a connection and search the addressbook fine. When I attempt to
> > connect over port 636
> I am attempting to connect to an openldap addressbook over SSL from
> Squirrelmail. When I connect over the traditional port 389, I am able to
> make a connection and search the addressbook fine. When I attempt to
> connect over port 636 (ldaps), I receive the following error:
>
> Error initia
I am attempting to connect to an openldap addressbook over SSL from
Squirrelmail. When I connect over the traditional port 389, I am able to
make a connection and search the addressbook fine. When I attempt to
connect over port 636 (ldaps), I receive the following error:
Error initializing LDAP
me lmiddle wrote:
verify with:
http://www.squirrelmail.org/plugin_view.php?id=235
Make sure PHP error dispalys are turned on or check apache logs and
check your session support in your PHP build.
Below is the exact error I get from SM 1.4.4
Unknown user or password incorrect.
This comes from one
> verify with:
>
> http://www.squirrelmail.org/plugin_view.php?id=235
>
> Make sure PHP error dispalys are turned on or check apache logs and
> check your session support in your PHP build.
Below is the exact error I get from SM 1.4.4
Unknown user or password incorrect.
This comes from one of
søn, 10.04.2005 kl. 00.51 skrev me lmiddle:
[...]
> The squirrelmail version has always been in the Subject line. That
> immediately after
> data.. anyways..
> I already said I could authenticate. using LOGIN so it is not a server
> problem.
So you configured SM wrong. I wouldn't know how yo
>> I have been trying to get Squirrelmail working with Courier-Imap
>> and have hit a wall. If I manually test access to the imap server
>> with a,
>>
>> telnet myimapserver 143
>> a001 LOGIN username password
>>
>> (everything works just fine.)
>>
>> H
Please reply *on list* so others can benefit.
I have been trying to get Squirrelmail working with Courier-Imap
and
have hit a wall. If I manually test access to the imap server with a,
telnet myimapserver 143
a001 LOGIN username password
(everything works just fine.)
However when I try the same
- Original Message -
From: "Tony Earnshaw" <[EMAIL PROTECTED]>
To: squirrelmail-users@lists.sourceforge.net
Subject: Re: [SM-USERS] Squirrelmail 1.4.4 and Courier-Imap authenticationhelp?
Date: Sun, 10 Apr 2005 00:00:36 +0200
>
> lør, 09.04.2005 kl. 21.23 skrev me
I have been trying to get Squirrelmail working with Courier-Imap
and
have hit a wall. If I manually test access to the imap server with a,
telnet myimapserver 143
a001 LOGIN username password
(everything works just fine.)
However when I try the same thing with Squirrelmail 1.4.4 I get a
error o
lør, 09.04.2005 kl. 22.36 skrev Marc Powell:
[...]
> Try enabling debug in courier. It'll log the username and password
> that's passed to it. I'll bet that will point you to what you've
> misconfigured.
This only applies to the very latest (6 months?) Courier IMAP c.q.
Courier authlib libraries
lør, 09.04.2005 kl. 21.23 skrev me lmiddle:
> I have been trying to get Squirrelmail
What SquirrelMail?
> working with Courier-Imap
What Courier IMAP?
> and
> have hit a wall. If I manually test access to the imap server with a,
>
> telnet myimapserver 143
> a001 LOGIN username passwo
- Original Message -
From: "Marc Powell" <[EMAIL PROTECTED]>
To: squirrelmail-users@lists.sourceforge.net
Subject: RE: [SM-USERS] Squirrelmail 1.4.4 and Courier-Imap authentication help?
Date: Sat, 9 Apr 2005 15:36:14 -0500
>
>
>
> > -Origina
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:squirrelmail-
> [EMAIL PROTECTED] On Behalf Of me lmiddle
> Sent: Saturday, April 09, 2005 2:24 PM
> To: squirrelmail-users@lists.sourceforge.net
> Subject: [SM-USERS] Squirrelmail 1.4.4 and Courier-Imap aut
I have been trying to get Squirrelmail working with Courier-Imap and
have hit a wall. If I manually test access to the imap server with a,
telnet myimapserver 143
a001 LOGIN username password
(everything works just fine.)
However when I try the same thing with Squirrelmail 1.4.4 I get a
erro
Hello,
I have been trying to get Squirrelmail working with Courier-Imap and
have hit a wall. If I manually test access to the imap server with a,
telnet myimapserver 143
a001 LOGIN username password
(everything works just fine.)
However when I try the same thing with Squirrelmail 1.4.4 I g
The quicksave plugin was causing the error to be displayed. Thank You.
-Lorene
> Im sorry I didnt realize that I didnt do my reply back to the list. I
> did see the error message from double clicking on the yellow icon. Here
> is what it showed me:
> Line 222
> Char: 29
> Error: Syntax error
>
Im sorry I didnt realize that I didnt do my reply back to the list. I
did see the error message from double clicking on the yellow icon. Here
is what it showed me:
Line 222
Char: 29
Error: Syntax error
Code: 0
URL:
https://jakester.cc.binghamton.edu/src/compose.php?mailbox=INBOX&startMessage=1
Please reply on-list so others may benefit.
Lorene Evans wrote:
Nothing happens when I click on the yellow icon.
You usually have to double-click.
My option under
IE/Internet Options/Advanced for Disable script debugging was checked
and I have tried to toggle it to either make the message go aw
Lorene Evans wrote:
I have just installed squirrelmail version 1.4.4. I have php version
4.3.0 and apache 1.3.26. I am getting a "Done, but errors on page"
message in Internet Explorer 6 while using any of the "compose" features
(for example, compose, forward). I did also load version 1.5.0
I have just installed squirrelmail version 1.4.4. I have php version
4.3.0 and apache 1.3.26. I am getting a "Done, but errors on page"
message in Internet Explorer 6 while using any of the "compose" features
(for example, compose, forward). I did also load version 1.5.0 and
have the same m
> 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
On Wed, February 2, 2005 8:56, Fredrik Jervfors said:
>> 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).
>> Do y
> 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
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
32 matches
Mail list logo
