[SM-USERS] Read messages appear as new in 1.4

2003-04-03 Thread Matthew Kiedrowski
Using SM 1.4 Stable PHP 4.3 IMAP server is Eudora Internet Mail Server 3.2 (not my choice) SM hosted on OS X Server 10.2.4 No matter what I've tried all messages display as new. The new message counter in the left pane will display the correct count of new messages however. I've tried altering

Re: [SM-USERS] Fix for Message Highlighting in 1.4.0 (again)

2003-04-03 Thread Jassu Laivuori
Hi ! and sorry about dumb question but is there somekind of patch that works with those Red Hat compiled rpm's that squirrelmail provides on their download-page ? I use RH 7.3 and squirrelmail is installed from rpm-package... -- Jassu - Original Message - From: "Seth Randall" <[EMAIL P

[SM-USERS] New Branch for SquirrelMail 1.4 Stable release

2003-04-03 Thread Erin Schnabel
As is our usual tradition, we've made a new branch for our new stable release. To checkout the latest Stable CVS: cvs -z3 CVSROOT checkout -r SM-1_4-STABLE squirrelmail The development stream has again usurped CVS HEAD. To checkout CVS HEAD (pre-1.5.0) cvs -z3 CVSROOT checkout squirrelmail A

Re: [SM-USERS] (no subject)

2003-04-03 Thread Cyanpeach
Hi, My account is not working, when I tried to sign on at: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users hope you can help ChanyP.

[SM-USERS] (no subject)

2003-04-03 Thread Cyanpeach
Hello, I have a Squirrel Mail account (version 1.2.5) and I was never able to sent any mail..I can compose it and press "sent" and it will take me back to the INBOX and the receiver would never get anything. I read in the SolvingProblems about the same problem and to solve by going into php.ini and

[SM-USERS] Re: Login not accepted (but IMAP works everywhere else)

2003-04-03 Thread Sigmund Gudvangen
I have exactly the same problem as reported by Tim Robinson a while ago. All the symptoms reported by Tim are there, the cookies etc. Today I updated to Squirrelmail 1.4.0, but the problem persists. I though it might be useful to know that I am using Bincimap, which works fine with KMail (over s

Re: [SM-USERS] First problem with new 1.4 sending mail

2003-04-03 Thread Jonathan Angliss
Hello Anjan, On Thursday, April 03, 2003, Anjan Sen wrote... > I've discovered a problem with the new 1.4 that 1.2.11 didn't have. > For reasons of my own I have Apache listening on a non-standard port > purely to do Squirrelmail stuff. The problem is when Squirrelmail > talks to my smtp server to

[SM-USERS] First problem with new 1.4 sending mail

2003-04-03 Thread Anjan Sen
Hi, I've discovered a problem with the new 1.4 that 1.2.11 didn't have. For reasons of my own I have Apache listening on a non-standard port purely to do Squirrelmail stuff. The problem is when Squirrelmail talks to my smtp server to send mail, it says 'HELO hostname:port' which is then rejecte

Re: [SM-USERS] 1.4.0 - error when replying to message

2003-04-03 Thread Caffeinate The World
--- Caffeinate The World <[EMAIL PROTECTED]> wrote: > When replying to a message, I get the following error: > > --- > Body retrieval error. The reason for this is most probably that the > message is malformed. > Command: FETCH 14225 BODY[1] > Response: OK > Message: FETCH completed

Re: [SM-USERS] Any upgrade issues for 1.4.0?

2003-04-03 Thread Jonathan Angliss
Hello Anjan, On Thursday, April 03, 2003, Anjan Sen wrote... > Anyone know if 1.4.0 will work properly with Apache2? Last time I > tried there were problems with relative paths, although that may > have been a php issue rather than a squirrel one. That has been fixed if you use the latest PHP

[SM-USERS] Fix for Message Highlighting in 1.4.0 (again)

2003-04-03 Thread Seth Randall
Would probably help if I attached the patch huh? Attached is a patch to fix message hightlighting in 1.4.0. I'm guessing most the developers either don't have message highlighting turned on or aren't using E_ALL Seth. -- Seth Randall IT Support Specialist Missoula Federal Credit Union [EMAIL

[SM-USERS] Fix for Message Highlighting in 1.4.0

2003-04-03 Thread Seth Randall
Attached is a patch to fix message hightlighting in 1.4.0. I'm guessing most the developers either don't have message highlighting turned on or aren't using E_ALL Seth. -- Seth Randall IT Support Specialist Missoula Federal Credit Union [EMAIL PROTECTED] MSN: [EMAIL PROTECTED]/ICQ: 23164675 -

Re: [SM-USERS] Any upgrade issues for 1.4.0?

2003-04-03 Thread Anjan Sen
I just upgraded and it worked first time. Great job. Anyone know if 1.4.0 will work properly with Apache2? Last time I tried there were problems with relative paths, although that may have been a php issue rather than a squirrel one. -- "Women and cats will do as they please, and men and dogs sh

[SM-USERS] 1.4.0 - error when replying to message

2003-04-03 Thread Caffeinate The World
When replying to a message, I get the following error: --- Body retrieval error. The reason for this is most probably that the message is malformed. Command:FETCH 14225 BODY[1] Response: OK Message:FETCH completed. FETCH line: --- I'm using Courier-IMAP. This problem doesn't

Re: [SM-USERS] Any upgrade issues for 1.4.0?

2003-04-03 Thread Jonathan Angliss
Hello Caffeinate, On Thursday, April 03, 2003, Caffeinate The World wrote... > I have 1.2.11 in production now. Any issues I should be aware of when > going to 1.4? Am currently using PHP-4.3.2 (latest snap), Courier-IMAP. Some plugins are liable to break. You might want to install a copy sid

[SM-USERS] Re: Folder Deletion

2003-04-03 Thread Jess
I spaced including a subject. Subject included as of now. > I noticed in 1.4.0 (and this very well might be in previous versions also, > and it very well might be an issue thats not directly tied into SM), when > you try to delete a folder that allows subfolders you get the standard > error: > >

[SM-USERS] (no subject)

2003-04-03 Thread Jess
I noticed in 1.4.0 (and this very well might be in previous versions also, and it very well might be an issue thats not directly tied into SM), when you try to delete a folder that allows subfolders you get the standard error: ERROR : Could not complete request. Query: DELETE "" Reason Given: DELE