Try editing /etc/httpd/conf.d/php.conf and delete the LimitBodyRequest line.
On 4/5/06, Anatoly Alexei Pedemonte Ku <[EMAIL PROTECTED]> wrote: > > > > Hi list: > > had problems trying 2 webmail systems, SquirrelMail and Horde. I dont knows > it is the cause of these problems, PHP, PEAR, APACHE, on CentOS, is updated. > > Somebody can help me, please. Attach screenshots and describe the problems. > > First Problem: Horde Framework, messages size than 2 Mb, in Firefox, shows > here... (php.ini, modified values upload_max, memory_limit, post_size, > greather than 8Mb) It happens When I want to see the message 2034kb size. On > IExplorer, shows the error document "The page cannot be displayed" > > > > > Second problem: After updating Pear components... Viewing done, on Firefos > and IExplorer (mail.kkklld.com, don´t exists, I changed for security > precautions) > > > > > Third problem: On Squirrelmail on Firefox Shows this dialog, when forward > the message (this message attachments is 6Mb size in format document .doc) > On IExplorer, shows the error document "The page cannot be displayed" This > same problem, on RoundCube Webmail > > > > > > > ----------------------------------------------------------- > Anatoly Alexei Pedemonte Ku > RAGE SYSTEMS S.A.C. > http://www.ragesys.net > Av. Juan Pascal Pringles 1225 (ex- La Fontana) - LA MOLINA > LIMA - PERU > Teléfono: 511.7962262 > Móvil: 511.97167435 > ----------------------------------------------------------- > Este correo y su contenido son confidenciales y exclusivos para su > destinatario. Si usted recibe este mensaje por error o no es el destinatario > del mismo, por favor sírvase eliminarlo y notificarle a su originador. Así > mismo, todas las ideas y reflexiones expresadas en esta comunicación > corresponden al originador del correo y NO representa la posición oficial de > su empleador. > -------------------------------------------------------------------------------------------------------------------------------------- > This email is intended only for the addressee(s) and contains information > which may be confidential, legally privileged. If you are not intended > recipient please do not save, forward, disclose or copy the content of this > email. Please delete it completely from your system and notify > originator.Finally, all ideas expressed in this communication are personal > comments and NOT represent official position of his employer. > -------------------------------------------------------------------------------------------------------------------------------------- > > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: GnuPG v1.4.2.1 (MingW32) > > mQGiBEP74n4RBACWbWMwp0mlBGkv+VsER3gvmt2Y7UmiuDRapL6W2fJkRAiZSNyG > GmQlnnC82G0xyQ2raKRaHyXpL5bx6mP6zoM9ws3xQgLSXN9xepHBBMKxktrsOkmt > wU9fO0j969iE48g2U+T0M3VK9M63d8jVplKJPYSX3d8MSPmCNdznf+6RawCgzEqO > 4rtw5qpjsHgpYhfcU67LR1UD/09sgy4NppYkDSIYJhcAJGKOBYT5ap9/u6BbRme2 > XV6fzni7/ZyeA+rLsPL2VR9KLDirGCZR0tbUA07tcY8eWqh1yugGXxFA66XH7/Hw > ULi8yEZCHRtx9VFWuUK72SB5yFD8tWS7v2kNElMQ7PtXitSSvkVKgR6HEVA0m77Y > HmbgA/0WE8QrDKdQM8QxqzsIm+o2IaJ32WHrAZXCyueK29LGDpiQ/+n6xQ+naNo6 > eXxvRLgZgwkf8CABuzPDBNc0vVz7Bgh2Bv2mUevYiVVT7yqqRDtHNM06CztbRz4a > +oHN0UyyW9pLGw9ImvKHIWlmkc2pCvRzecHMqHT/aUasohco0bQ/QW5hdG9seSBB > LiBQZWRlbW9udGUgS3UgKEdOVSBQR1AgQW5hdG9seSkgPGFuYXRvbHlAcmFnZXN5 > cy5uZXQ+iF8EExECACAFAkP74n4CGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAK > CRDl44NRz+awqjn6AJikjCHB8OG2d1hyMzZBpDfJwG9DAJ9pG2mkTsUso3HOAkij > KlnND+5OHbkCDQRD++KXEAgAvR6UmL6ZjGKLd1yUT/C5aR0eKlHEi0yO73fMBxt+ > Lwow28qzBKHrMVGnMRQOl3KgDqVH2OU2fqcLaybqHsE02cwS2IhtzsB/Xi6WyS4q > GYaAGnEbJ7FRIDAAHoc07EWXkzVmNBw/P1Xnj21dAE1VuH28lBwKeuBy19C44wbi > /BzvntzmMTa1PqloubiGauXVbkRmBc6Dn9qHeqoipQvbVyQTimvAH9RaCzehD8WE > W8INRZkPM7R87FGXW2h3+29qVMBxsUU85oLmiUMlR5kqJKcU8h/vhrPq7qa0hudh > wMllE/SOIqa1sVxbIOk5xEV36kbFqXlfb3JXSEngpbre7wADBQf/ZL6o/IpOXOHp > St4aO8NgPrWD+NZLNug9sccqYnlWVGMBH3CjiSUFFNC+hoXjecW4YMh6NUBXbkKX > etDSgrxCc07DSSQ9f5hYB5tP5Sov+j4PJp44iV0uYS7kfugAwWDIkSJJVMv0UIb+ > Elf0Ss0VxjmqIv92wDE+XVCEB342DhuhUt8HUmVYVihC0N7pJCEqPGfWgxBZA5nm > loLIAfl8qb1D/FCPvb9Yfj9qn5hTvtZYjgbh1a8awOiodwaPrUP4bTdY/SRKFKBP > 0txyJn5h345GZ2zpfGYleEYnVPRZm57/WM5SsPhZ1OoO5imMl7qVsosSSVFGcL17 > ZNVqqJOH0IhJBBgRAgAJBQJD++KXAhsMAAoJEOXjg1HP5rCqFOoAnRO+jqkCfn/H > UquknQh/MK9K3+H9AKCciBqvAWaVQ6O5Ek2EEaMlRuGdJw== > =Mnmw > -----END PGP PUBLIC KEY BLOCK----- > > -----Mensaje original----- > De: Johnny Hughes [mailto:[EMAIL PROTECTED] > Enviado el: Sábado, 07 de Enero de 2006 05:10 a.m. > Para: [email protected] > Asunto: Re: [qmailtoaster] horde rpms > > On Fri, 2006-01-06 at 15:25 -0600, Brent Dacus wrote: > > Johnny, > > > > I is my pleasure to speak to you, I love CentOS. > > > > So if I edit Jake or Nick's dependency script and add all the horde > > packs I should be fine? What should I look to configure? > > > > Thanks > > I would just use yum to install them ... > > httpd, mysql and php all need to be up and functioning before installing the > horde apps (those are also required for qmailtoaster to work, so they are > already setup if you have a functional qmailtoaster running). > > The Horde RPMS are in the extras repository (which is enabled by default in > CentOS), so you can install them using yum: > > yum groupinstall Horde-Apps > > BUT, that is just the beginning of the install. > > You would then need to go to the /usr/share/horde/docs and follow the > INSTALL document for the Horde Framework. (The things you need to install > are the extra pear modules and do all the database create scripts and > configure ... you do not need to setup apache or compile/untar anything). > > You would also need to do the same for all the other apps that are included > (gollem, imp, ingo, kronolith, mnemo, nag, and turba). There is a docs > directory under each individual app directory ... for example > /usr/share/horde/gollem/docs/ ... and an INSTALL document in each. > > Once all the databases are created and the pear stuff is right, you need to > make the conf.php file in each app's config directory owned by the user that > runs your web server (usually apache in CentOS, but it could be different if > changed by the user ... look in your /etc/httpd/conf/httpd.conf file for the > User and Group directives and make note of what they are, usually both are > set to apache) > > So each conf.php file in each config directory (ie, > /usr/share/horde/config/conf.php and /usr/share/horde/gollem/config/conf.php > ... and the other modules) need to have the following command done on them > (from within their > directory): > > chown apache:apache conf.php > > (if apache is the User and Group used to run the web server) > > Once all the conf.php files are writable by the web server, you would go > to: > > http://your.servername.here/horde/ > > and set up each app as instructed in the install docs. > > Horde is a very detailed setup, even with the RPMS. > > You would also want to look at /etc/httpd/conf.d/horde.conf and make sure it > is what you want ... it is probably OK. > > If your server is using SELinux, you would need to work with your profiles > and rules to allow the webserver user to update the conf.php files as well. > ------------------------------------------ > I don't like the way the pear modules need to be updated/installed ... > basically you can use the command: > > pear list > > to get your current modules that are installed ... and you can do upgrade > the modules (for each module listed EXCEPT "PEAR"): > > pear upgrade module_name > > If/when PHP is upgraded (actually the rpm named php-pear), you will need to > re-upgrade the base modules (which is a major PITA). Those base pear > modules currently are: > > Installed packages: > =================== > Package Version State > Archive_Tar 1.1 stable > Console_Getopt 1.2 stable > DB 1.6.2 stable > HTTP 1.2.2 stable > Mail 1.1.3 stable > Net_SMTP 1.2.3 stable > Net_Socket 1.0.1 stable > PEAR 1.3.2 stable > XML_Parser 1.0.1 stable > XML_RPC 1.1.0 stable > > Just for the record, Greg Swallow (SME Server project) did some of the > original spec files for the Horde apps (with I used as a template to create > the rest) and he is currently trying to work with RHEL and Fedora to make it > easier to upgrade the pear modules as RPMS. Greg and I have corresponded on > this and I agree with the patch he has submitted ... > hopefully upstream will do something soon. > > Since CentOS is an enterprise distro, we want to wait to see how upstream is > going to handle the pear RPMS issue before we roll something into CentOS ... > as we are committed to maintaining what we do for 7 years. > > --- > Thanks, > Johnny Hughes > > --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
