Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-10 Thread Paul Lesniewski
> enabled the debugger Not sure what that is, but all you need is to track down the right PHP configuration > and configured php.ini to log and even put the suggested .htaccess file in > /usr/share/squirrelmail. I'm not getting any logs and the blank frame > continues. I've restarted httpd as wel

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-10 Thread Robert Kudyba
Hi Paul, I was the one that opened that bug report at https://sourceforge.net/p/squirrelmail/bugs/2859/. I enabled the debugger and configured php.ini to log and even put the suggested .htaccess file in /usr/share/squirrelmail. I'm not getting any logs and the blank frame continues. I've restarted

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-06 Thread Paul Lesniewski
On Thu, January 6, 2022 7:55 pm, Robert Kudyba wrote: >> >> > As a follow up I used the D option and chose dovecot and I re-enabled >> > undelete and delete_and_next.but this extra INBOX still exists: >> >> Please first manually check what folders are in the user's mail storage >> on >> the serv

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-06 Thread Tóth Attila
2022.Január 6.(Cs) 20:55 időpontban Robert Kudyba ezt írta: >> >> > As a follow up I used the D option and chose dovecot and I re-enabled >> > undelete and delete_and_next.but this extra INBOX still exists: >> >> Please first manually check what folders are in the user's mail storage >> on >> the s

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-06 Thread Robert Kudyba
> > > As a follow up I used the D option and chose dovecot and I re-enabled > > undelete and delete_and_next.but this extra INBOX still exists: > > Please first manually check what folders are in the user's mail storage on > the server. Looks like additional one(s) may have been accidentally > cre

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-06 Thread Paul Lesniewski
On Thu, January 6, 2022 2:56 pm, Robert Kudyba wrote: > As a follow up I used the D option and chose dovecot and I re-enabled > undelete and delete_and_next.but this extra INBOX still exists: Please first manually check what folders are in the user's mail storage on the server. Looks like addi

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-06 Thread Paul Lesniewski
>> > I also noticed the warning message about >> > using the old config file that mentions there are probably new options >> and >> > to just use conf.pl. >> >> Another thing you can do is re-configure from scratch and use diff to >> see >> if there's anything you missed. >> > > I see delete_move

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-06 Thread Robert Kudyba
On Thu, Jan 6, 2022 at 1:18 AM Paul Lesniewski wrote: > > I ended up backing up the config files and dropped the files in place. > > When > > logging in I did get asked to enter my reply email address so is there a > > preferences file that I missed? > > Possibly your plugin configuration files.

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-05 Thread Paul Lesniewski
> I ended up backing up the config files and dropped the files in place. > When > logging in I did get asked to enter my reply email address so is there a > preferences file that I missed? Possibly your plugin configuration files. If you're using version 1.5.2 then you should also migrate plugin_

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-04 Thread Paul Lesniewski
On Tue, January 4, 2022 10:17 pm, Robert Kudyba wrote: > On Tue, Jan 4, 2022 at 5:02 PM Paul Lesniewski > wrote: > >> >> >> On Tue, January 4, 2022 9:49 pm, Robert Kudyba wrote: >> >> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on >> >> Fedora >> >> > 35. First I don''t see

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-04 Thread Robert Kudyba
On Tue, Jan 4, 2022 at 5:02 PM Paul Lesniewski wrote: > > > On Tue, January 4, 2022 9:49 pm, Robert Kudyba wrote: > >> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on > >> Fedora > >> > 35. First I don''t see a F35 RPM. > >> > >> With PHP 8 you're probably going to need a newe

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-04 Thread Paul Lesniewski
On Tue, January 4, 2022 9:49 pm, Robert Kudyba wrote: >> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on >> Fedora >> > 35. First I don''t see a F35 RPM. >> >> With PHP 8 you're probably going to need a newer version of >> SquirrelMail. > > Does that mean having to compile fr

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-04 Thread Robert Kudyba
> PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on Fedora > > 35. First I don''t see a F35 RPM. > > With PHP 8 you're probably going to need a newer version of SquirrelMail. > Does that mean having to compile from source? > After upgrading Apache works just fine > > for loading

Re: [SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-04 Thread Paul Lesniewski
On Tue, January 4, 2022 9:17 pm, Robert Kudyba wrote: > PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on Fedora > 35. First I don''t see a F35 RPM. With PHP 8 you're probably going to need a newer version of SquirrelMail. > After upgrading Apache works just fine > for loadin

[SM-USERS] Squirrelmail does not load after upgrade for Fedora 35, ISE 500

2022-01-04 Thread Robert Kudyba
PHP 8.0.14, with squirrelmail-1.4.23-6.fc34.20190710.noarch alas on Fedora 35. First I don''t see a F35 RPM. After upgrading Apache works just fine for loading plain HTML pages but webmail gets an internal server error, 500. I enabled debug logging and below is what I see in the SSl error logs wit