Menu
▾
▴
squirrelmail-users — SquirrelMail Users Mailing List
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(323) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(886) |
Feb
(712) |
Mar
(808) |
Apr
(522) |
May
(798) |
Jun
(462) |
Jul
(718) |
Aug
(765) |
Sep
(680) |
Oct
(610) |
Nov
(763) |
Dec
(805) |
| 2003 |
Jan
(907) |
Feb
(960) |
Mar
(757) |
Apr
(1072) |
May
(1084) |
Jun
(934) |
Jul
(839) |
Aug
(587) |
Sep
(644) |
Oct
(824) |
Nov
(653) |
Dec
(611) |
| 2004 |
Jan
(556) |
Feb
(405) |
Mar
(619) |
Apr
(557) |
May
(630) |
Jun
(577) |
Jul
(535) |
Aug
(460) |
Sep
(446) |
Oct
(597) |
Nov
(517) |
Dec
(471) |
| 2005 |
Jan
(474) |
Feb
(573) |
Mar
(438) |
Apr
(508) |
May
(355) |
Jun
(455) |
Jul
(389) |
Aug
(412) |
Sep
(382) |
Oct
(345) |
Nov
(448) |
Dec
(368) |
| 2006 |
Jan
(433) |
Feb
(378) |
Mar
(379) |
Apr
(356) |
May
(265) |
Jun
(334) |
Jul
(305) |
Aug
(273) |
Sep
(292) |
Oct
(192) |
Nov
(240) |
Dec
(263) |
| 2007 |
Jan
(279) |
Feb
(222) |
Mar
(185) |
Apr
(175) |
May
(313) |
Jun
(218) |
Jul
(157) |
Aug
(236) |
Sep
(277) |
Oct
(274) |
Nov
(198) |
Dec
(285) |
| 2008 |
Jan
(251) |
Feb
(188) |
Mar
(185) |
Apr
(152) |
May
(203) |
Jun
(152) |
Jul
(198) |
Aug
(135) |
Sep
(178) |
Oct
(160) |
Nov
(94) |
Dec
(175) |
| 2009 |
Jan
(101) |
Feb
(89) |
Mar
(117) |
Apr
(79) |
May
(130) |
Jun
(148) |
Jul
(157) |
Aug
(98) |
Sep
(117) |
Oct
(96) |
Nov
(112) |
Dec
(129) |
| 2010 |
Jan
(126) |
Feb
(158) |
Mar
(149) |
Apr
(60) |
May
(87) |
Jun
(149) |
Jul
(128) |
Aug
(66) |
Sep
(78) |
Oct
(42) |
Nov
(40) |
Dec
(62) |
| 2011 |
Jan
(53) |
Feb
(68) |
Mar
(39) |
Apr
(66) |
May
(25) |
Jun
(51) |
Jul
(34) |
Aug
(45) |
Sep
(39) |
Oct
(45) |
Nov
(51) |
Dec
(45) |
| 2012 |
Jan
(59) |
Feb
(38) |
Mar
(72) |
Apr
(24) |
May
(36) |
Jun
(44) |
Jul
(55) |
Aug
(48) |
Sep
(25) |
Oct
(39) |
Nov
(27) |
Dec
(21) |
| 2013 |
Jan
(16) |
Feb
(29) |
Mar
(31) |
Apr
(42) |
May
(24) |
Jun
(15) |
Jul
(31) |
Aug
(28) |
Sep
(5) |
Oct
(8) |
Nov
(15) |
Dec
(3) |
| 2014 |
Jan
(5) |
Feb
(14) |
Mar
(22) |
Apr
(32) |
May
(32) |
Jun
(11) |
Jul
(6) |
Aug
(23) |
Sep
(16) |
Oct
(4) |
Nov
(13) |
Dec
(12) |
| 2015 |
Jan
(30) |
Feb
(17) |
Mar
(24) |
Apr
(11) |
May
(3) |
Jun
(25) |
Jul
|
Aug
(8) |
Sep
(45) |
Oct
(4) |
Nov
(5) |
Dec
(8) |
| 2016 |
Jan
(22) |
Feb
(17) |
Mar
(8) |
Apr
(11) |
May
(26) |
Jun
(4) |
Jul
(18) |
Aug
(11) |
Sep
(6) |
Oct
(10) |
Nov
(17) |
Dec
(15) |
| 2017 |
Jan
(33) |
Feb
(1) |
Mar
(4) |
Apr
(2) |
May
(9) |
Jun
(9) |
Jul
(5) |
Aug
(7) |
Sep
(4) |
Oct
(7) |
Nov
|
Dec
(2) |
| 2018 |
Jan
(2) |
Feb
|
Mar
(10) |
Apr
(29) |
May
(13) |
Jun
(4) |
Jul
(3) |
Aug
|
Sep
|
Oct
(14) |
Nov
(6) |
Dec
(2) |
| 2019 |
Jan
(3) |
Feb
|
Mar
(5) |
Apr
(13) |
May
(5) |
Jun
|
Jul
(6) |
Aug
(25) |
Sep
(1) |
Oct
|
Nov
|
Dec
(6) |
| 2020 |
Jan
(10) |
Feb
(8) |
Mar
|
Apr
|
May
(4) |
Jun
(26) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(13) |
| 2021 |
Jan
(12) |
Feb
|
Mar
(10) |
Apr
(2) |
May
(21) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
(14) |
Dec
(6) |
| 2022 |
Jan
(20) |
Feb
(1) |
Mar
(3) |
Apr
(21) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(3) |
Oct
|
Nov
(13) |
Dec
(4) |
| 2023 |
Jan
(3) |
Feb
(15) |
Mar
|
Apr
(4) |
May
(5) |
Jun
|
Jul
(11) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
(11) |
| 2024 |
Jan
(20) |
Feb
|
Mar
(5) |
Apr
|
May
(3) |
Jun
|
Jul
(5) |
Aug
(8) |
Sep
(8) |
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
(11) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Paul L. <pa...@sq...> - 2022-01-11 05:46:19
|
> 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 well as php-fpm.service and dovecot. All that means is you haven't found the right configuration yet. Blank screen means PHP errors, nothing else. > Also: > php -i | grep php.ini Running php on the CLI is not the same as php-fpm. There are sometimes different ini files used for each. Look more closely and you'll find other PHP configuration files on your system. They may or may not be called exactly "php.ini" > Configuration File (php.ini) Path => /etc > Loaded Configuration File => /etc/php.ini > > In the php.ini file: > error_log = /var/log/php_errors.log > html_errors = On > log_errors = On > display_errors = on > error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED > > all php-fpm error log has is: > [10-Jan-2022 20:40:10] NOTICE: fpm is running, pid 2811116 > [10-Jan-2022 20:40:10] NOTICE: ready to handle connections > [10-Jan-2022 20:40:10] NOTICE: systemd monitor interval set to 10000ms > (END) > > What am I missing? You can insert a call to phpinfo() into something like the configtest.php file to get a better idea. Or use locate, find, or grep for things like "display_errors" in /etc/php or similar. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Robert K. <rk...@fo...> - 2022-01-11 01:43:27
|
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 httpd as well as php-fpm.service and dovecot. Also: php -i | grep php.ini Configuration File (php.ini) Path => /etc Loaded Configuration File => /etc/php.ini In the php.ini file: error_log = /var/log/php_errors.log html_errors = On log_errors = On display_errors = on error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED all php-fpm error log has is: [10-Jan-2022 20:40:10] NOTICE: fpm is running, pid 2811116 [10-Jan-2022 20:40:10] NOTICE: ready to handle connections [10-Jan-2022 20:40:10] NOTICE: systemd monitor interval set to 10000ms (END) What am I missing? On Thu, Jan 6, 2022 at 6:45 PM Paul Lesniewski <pa...@sq...> wrote: > > > 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 server. Looks like additional one(s) may have been accidentally > >> created. > > > > > > OK so I see these that are the correct ones, which I believe point to > > /var/spool/mail/me: > > > > ls -lta /home/me/mail/.imap/ > > This looks like a mess of different INBOX types caused by changing your > Dovecot and/or client mailbox settings. You might want to look at your > Dovecot mail_location (unless you have good reason, leave it as default) > and if you have no important mail, I'd suggest deleting the entire mail > store and start again with better-synchronized settings. Get rid of the > superfluous INBOXes and whatnot. > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > > https://urldefense.proofpoint.com/v2/url?u=http-3A__squirrelmail.org_donate-5Fpaul-5Flesniewski.php&d=DwICAg&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=i74xaDjEkhtlfi09MIN4gIZqTScM5CgmQSNcfW7pIa5Sag-OXjJ_F2cBOeLSxJle&s=IC9n_iRQRqFuL_kIb_g9FINd7IrcLGBkxacG1jeAues&e= > > > > > ----- > squirrelmail-users mailing list > Posting guidelines: > https://urldefense.proofpoint.com/v2/url?u=http-3A__squirrelmail.org_postingguidelines&d=DwICAg&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=i74xaDjEkhtlfi09MIN4gIZqTScM5CgmQSNcfW7pIa5Sag-OXjJ_F2cBOeLSxJle&s=u_Ig5P-0vCP3vHoAcAfblRd5GA12TKIPeSjHjpeNEHs&e= > List address: squ...@li... > List archives: > https://urldefense.proofpoint.com/v2/url?u=http-3A__news.gmane.org_gmane.mail.squirrelmail.user&d=DwICAg&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=i74xaDjEkhtlfi09MIN4gIZqTScM5CgmQSNcfW7pIa5Sag-OXjJ_F2cBOeLSxJle&s=Ae7KPndRnKW8-GPCrA_OFrxvqEPy6GPuIuOjU11JvZM&e= > List info (subscribe/unsubscribe/change options): > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_squirrelmail-2Dusers&d=DwICAg&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=i74xaDjEkhtlfi09MIN4gIZqTScM5CgmQSNcfW7pIa5Sag-OXjJ_F2cBOeLSxJle&s=MQHHUrrkYexIPChfpf8ouLt8C8CM52p5K3Wb7GM1zGA&e= > |
|
From: Paul L. <pa...@sq...> - 2022-01-06 23:44:50
|
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 server. Looks like additional one(s) may have been accidentally >> created. > > > OK so I see these that are the correct ones, which I believe point to > /var/spool/mail/me: > > ls -lta /home/me/mail/.imap/ This looks like a mess of different INBOX types caused by changing your Dovecot and/or client mailbox settings. You might want to look at your Dovecot mail_location (unless you have good reason, leave it as default) and if you have no important mail, I'd suggest deleting the entire mail store and start again with better-synchronized settings. Get rid of the superfluous INBOXes and whatnot. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Tóth A. <at...@at...> - 2022-01-06 20:57:35
|
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 server. Looks like additional one(s) may have been accidentally >> created. > > > OK so I see these that are the correct ones, which I believe point to > /var/spool/mail/me: I'm curious what you see, if you enter the Folders menu? There is a section down there that gives the possibility to subscribe and unsubscribe to specific folders. Assuming that the imap server's settings are OK. BR: Dw. -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057 > > ls -lta /home/me/mail/.imap/ > -rw------- 1 me me 5972 Jan 6 09:49 dovecot.list.index.log > drwx------. 2 me me 158 Jan 6 03:47 INBOX > -rw-------. 1 me me 696 Jan 5 16:21 dovecot.mailbox.log > -rw-------. 1 me me 8 Jan 5 16:21 dovecot-uidvalidity > drwx------ 2 me me 58 Jan 5 16:21 INBOX.Drafts > drwx------ 2 me me 58 Jan 5 16:21 INBOX.Trash > drwx------ 2 me me 58 Jan 5 16:21 INBOX.Sent > drwx------. 2 me me 95 Jan 5 12:04 Trash > -rw------- 1 me me 1176 Dec 14 09:52 dovecot.list.index > drwx------. 2 me me 95 Dec 6 09:20 Sent > drwx------. 2 me me 107 Jun 12 2021 Caughtspam > drwx------. 2 me me 95 Mar 7 2019 Drafts > drwx------. 2 me me 95 Sep 29 2017 ham > -r--r--r--. 1 me me 0 Oct 11 2016 dovecot-uidvalidity.57fd5727 > > ls -lta /home/me/mail/.imap/INBOX > -rw------- 1 me me 1708 Jan 6 09:49 dovecot.index.log > -rw------- 1 me me 1056776 Jan 6 09:49 dovecot.index.cache > drwx------. 2 me me 158 Jan 6 03:47 . > -rw------- 1 me me 113112 Jan 6 03:47 dovecot.index > -rw------- 1 me me 32768 Jan 6 03:47 dovecot.index.log.2 > drwx------. 11 me me 4096 Jan 5 16:21 .. > -rw-------. 1 me me 5080 Oct 12 2016 dovecot.index.thread > > The "extra" folders are shown here: > ls -lta /home/me/mail/ > drwxr-xr-x. 49 me me 8192 Jan 6 14:22 .. > -rw------- 1 me me 251876 Jan 6 09:49 Trash > -rw------- 1 me me 102 Jan 5 16:21 .subscriptions > drwx------. 11 me me 4096 Jan 5 16:21 .imap > -rw------- 1 me me 0 Jan 5 16:21 INBOX.Drafts > -rw------- 1 me me 0 Jan 5 16:21 INBOX.Sent > -rw------- 1 me me 0 Jan 5 16:21 INBOX.Trash > -rw-------. 1 me me 36722502 Dec 10 17:25 Sent > -rw-------. 1 me me 452104 Jul 11 21:40 Caughtspam > -rw-------. 1 me me 562 Mar 2 2019 Drafts > -rw-------. 1 me me 81370815 Sep 14 2017 ham > drwx------. 2 me me 6 Oct 12 2016 INBOX > drwx------. 3 me me 78 Oct 11 2016 mail > > The .subscriptions files contains this: > cat /home/me/mail/.subscriptions > mail/Sent > mail/Trash > mail/Drafts > Sent > Trash > Drafts > Caughtspam > ham > INBOX.Sent > INBOX.Trash > INBOX.Drafts > > What's the easiest way to rectify this? Delete the undesired folders in > Squirrelmail? > > ----- > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squ...@li... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > |
|
From: Robert K. <rk...@fo...> - 2022-01-06 19:55:35
|
> > > 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 > created. OK so I see these that are the correct ones, which I believe point to /var/spool/mail/me: ls -lta /home/me/mail/.imap/ -rw------- 1 me me 5972 Jan 6 09:49 dovecot.list.index.log drwx------. 2 me me 158 Jan 6 03:47 INBOX -rw-------. 1 me me 696 Jan 5 16:21 dovecot.mailbox.log -rw-------. 1 me me 8 Jan 5 16:21 dovecot-uidvalidity drwx------ 2 me me 58 Jan 5 16:21 INBOX.Drafts drwx------ 2 me me 58 Jan 5 16:21 INBOX.Trash drwx------ 2 me me 58 Jan 5 16:21 INBOX.Sent drwx------. 2 me me 95 Jan 5 12:04 Trash -rw------- 1 me me 1176 Dec 14 09:52 dovecot.list.index drwx------. 2 me me 95 Dec 6 09:20 Sent drwx------. 2 me me 107 Jun 12 2021 Caughtspam drwx------. 2 me me 95 Mar 7 2019 Drafts drwx------. 2 me me 95 Sep 29 2017 ham -r--r--r--. 1 me me 0 Oct 11 2016 dovecot-uidvalidity.57fd5727 ls -lta /home/me/mail/.imap/INBOX -rw------- 1 me me 1708 Jan 6 09:49 dovecot.index.log -rw------- 1 me me 1056776 Jan 6 09:49 dovecot.index.cache drwx------. 2 me me 158 Jan 6 03:47 . -rw------- 1 me me 113112 Jan 6 03:47 dovecot.index -rw------- 1 me me 32768 Jan 6 03:47 dovecot.index.log.2 drwx------. 11 me me 4096 Jan 5 16:21 .. -rw-------. 1 me me 5080 Oct 12 2016 dovecot.index.thread The "extra" folders are shown here: ls -lta /home/me/mail/ drwxr-xr-x. 49 me me 8192 Jan 6 14:22 .. -rw------- 1 me me 251876 Jan 6 09:49 Trash -rw------- 1 me me 102 Jan 5 16:21 .subscriptions drwx------. 11 me me 4096 Jan 5 16:21 .imap -rw------- 1 me me 0 Jan 5 16:21 INBOX.Drafts -rw------- 1 me me 0 Jan 5 16:21 INBOX.Sent -rw------- 1 me me 0 Jan 5 16:21 INBOX.Trash -rw-------. 1 me me 36722502 Dec 10 17:25 Sent -rw-------. 1 me me 452104 Jul 11 21:40 Caughtspam -rw-------. 1 me me 562 Mar 2 2019 Drafts -rw-------. 1 me me 81370815 Sep 14 2017 ham drwx------. 2 me me 6 Oct 12 2016 INBOX drwx------. 3 me me 78 Oct 11 2016 mail The .subscriptions files contains this: cat /home/me/mail/.subscriptions mail/Sent mail/Trash mail/Drafts Sent Trash Drafts Caughtspam ham INBOX.Sent INBOX.Trash INBOX.Drafts What's the easiest way to rectify this? Delete the undesired folders in Squirrelmail? |
|
From: Paul L. <pa...@sq...> - 2022-01-06 19:05:27
|
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 additional one(s) may have been accidentally created. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Paul L. <pa...@sq...> - 2022-01-06 19:02:51
|
>> > 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_next plugin is not working. That is a vague statement that needs detail (maybe in its own thread) if you need help with it. > I also had the undelete plugin. Will those no longer work? Unless you moved from 1.4.x to 1.5.x then plugins should move over without any issues. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Robert K. <rk...@fo...> - 2022-01-06 14:34:02
|
On Thu, Jan 6, 2022 at 1:18 AM Paul Lesniewski <pa...@sq...>
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. If you're using version 1.5.2
> then you should also migrate plugin_hooks.php as well as the plugins you
> installed manually.
>
I believe I did that:
cat /usr/share/squirrelmail/config/plugin_hooks.php
<?php
/**
* SquirrelMail Plugin Hook Registration File
* Auto-generated using the configure script, conf.pl
*/
global $squirrelmail_plugin_hooks;
$squirrelmail_plugin_hooks['subject_link']['preview_pane']
= 'preview_pane_change_message_target';
$squirrelmail_plugin_hooks['optpage_loadhook_display']['preview_pane']
= 'preview_pane_show_options';
$squirrelmail_plugin_hooks['template_construct_message_list.tpl']['preview_pane']
= 'preview_pane_message_list';
$squirrelmail_plugin_hooks['template_construct_page_header.tpl']['preview_pane']
= 'preview_pane_open_close_buttons';
$squirrelmail_plugin_hooks['template_construct_page_header.tpl']['calendar']
= 'calendar';
$squirrelmail_plugin_hooks['read_body_header_right']['message_details']
= 'show_message_details';
>
> > 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_next plugin is not working. I also had the undelete
plugin. Will those no longer work?
>
> > I do see now that there is a subfolder called 'mail'
> > that has an additional Drafts, Sent and Trash folder
>
> Best way to fix this is to run conf.pl and use option D to select your
> IMAP server
>
I did end up running it but I'll try again using option D.
|
|
From: Paul L. <pa...@sq...> - 2022-01-06 06:18:35
|
> 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_hooks.php as well as the plugins you installed manually. > 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 do see now that there is a subfolder called 'mail' > that has an additional Drafts, Sent and Trash folder Best way to fix this is to run conf.pl and use option D to select your IMAP server -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Paul L. <pa...@sq...> - 2022-01-04 22:26:11
|
On Tue, January 4, 2022 10:17 pm, Robert Kudyba wrote: > On Tue, Jan 4, 2022 at 5:02 PM Paul Lesniewski <pa...@sq...> > 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 newer version of >> >> SquirrelMail. >> > >> > Does that mean having to compile from source? >> >> PHP is not a compiled language. It's just a matter of putting the >> source >> code on your server. It is possible that you could grab a tarball of >> 1.4.23-svn from our website and unpack that right on top of what you >> have, >> but that could get messy depending what the RPM author did or did not do >> with the source or configuration. Try placing the new tarball in a >> parallel directory, copy over the configuration and plugins, and see how >> that goes. >> > > Right, duh of course. So putting them in a place like > /usr/share/squirrelmail2 would be ok. Do I just re-run conf.pl? Which > files > hold the settings? Yes, you can re-run conf.pl or just copy over config.php from your other installation and most things will probably work fine assuming the RPM isn't heavily modified. Sometimes there can be custom configuration changes in config_local.php as well. Once copied over, you can still run conf.pl to make changes from there. >> >> > I enabled logging in /etc/php.ini now I see *Fatal error*: Array and >> > string >> > offset access syntax with curly braces is no longer supported in >> > */usr/share/squirrelmail/functions/strings.php* on line *634* >> >> That error indicates that in fact you need a newer version of >> SquirrelMail > > Will the new version you mentioned fix these? Yes -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Robert K. <rk...@fo...> - 2022-01-04 22:17:31
|
On Tue, Jan 4, 2022 at 5:02 PM Paul Lesniewski <pa...@sq...> 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 newer version of > >> SquirrelMail. > > > > Does that mean having to compile from source? > > PHP is not a compiled language. It's just a matter of putting the source > code on your server. It is possible that you could grab a tarball of > 1.4.23-svn from our website and unpack that right on top of what you have, > but that could get messy depending what the RPM author did or did not do > with the source or configuration. Try placing the new tarball in a > parallel directory, copy over the configuration and plugins, and see how > that goes. > Right, duh of course. So putting them in a place like /usr/share/squirrelmail2 would be ok. Do I just re-run conf.pl? Which files hold the settings? > > > I enabled logging in /etc/php.ini now I see *Fatal error*: Array and > > string > > offset access syntax with curly braces is no longer supported in > > */usr/share/squirrelmail/functions/strings.php* on line *634* > > That error indicates that in fact you need a newer version of SquirrelMail Will the new version you mentioned fix these? |
|
From: Paul L. <pa...@sq...> - 2022-01-04 22:02:21
|
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 from source? PHP is not a compiled language. It's just a matter of putting the source code on your server. It is possible that you could grab a tarball of 1.4.23-svn from our website and unpack that right on top of what you have, but that could get messy depending what the RPM author did or did not do with the source or configuration. Try placing the new tarball in a parallel directory, copy over the configuration and plugins, and see how that goes. > I enabled logging in /etc/php.ini now I see *Fatal error*: Array and > string > offset access syntax with curly braces is no longer supported in > */usr/share/squirrelmail/functions/strings.php* on line *634* That error indicates that in fact you need a newer version of SquirrelMail. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Robert K. <rk...@fo...> - 2022-01-04 21:50:16
|
> 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 plain HTML pages but webmail gets an internal server error, > > 500. > > More than likely the SSL connection problem is happening at a layer above > SquirrelMail. I'd first try to get a static page to load using that same > certificate/domain and then try SquirrelMail, also keeping an eye on the > PHP logs as well. > I enabled logging in /etc/php.ini now I see *Fatal error*: Array and string offset access syntax with curly braces is no longer supported in */usr/share/squirrelmail/functions/strings.php* on line *634* ssl error logs now show this: [Tue Jan 04 16:47:38.970635 2022] [ssl:info] [pid 138303:tid 138340] [client 108.54.237.13:4417] AH01964: Connection to child 201 established (server OURDOMAIN:443) [Tue Jan 04 16:47:38.970943 2022] [ssl:debug] [pid 138303:tid 138340] ssl_engine_kernel.c(2395): [client 108.54.237.13:4417] AH02043: SSL virtual host for servername OURDOMAIN found [Tue Jan 04 16:47:38.971163 2022] [core:debug] [pid 138303:tid 138340] protocol.c(2449): [client 108.54.237.13:4417] AH03155: select protocol from , choices=h2,http/1.1 for server OURDOMAIN [Tue Jan 04 16:47:38.982151 2022] [ssl:debug] [pid 138303:tid 138340] ssl_engine_kernel.c(2254): [client 108.54.237.13:4417] AH02041: Protocol: TLSv1.3, Cipher: TLS_AES_256_GCM_SHA384 (256/256 bits) [Tue Jan 04 16:47:38.982295 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(508): AH00831: socache_shmcb_store (0x7b -> subcache 27) [Tue Jan 04 16:47:38.982312 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(745): AH00842: expiring 1 and reclaiming 0 removed socache entries [Tue Jan 04 16:47:38.982323 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(765): AH00843: we now have 0 socache entries [Tue Jan 04 16:47:38.982338 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(862): AH00847: insert happened at idx=0, data=(0:32) [Tue Jan 04 16:47:38.982347 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(865): AH00848: finished insert, subcache: idx_pos/idx_used=0/1, data_pos/data_used=0/225 [Tue Jan 04 16:47:38.982356 2022] [socache_shmcb:debug] [pid 138303:tid 138340] mod_socache_shmcb.c(530): AH00834: leaving socache_shmcb_store successfully [Tue Jan 04 16:47:38.982614 2022] [ssl:debug] [pid 138303:tid 138340] ssl_engine_kernel.c(415): [client 108.54.237.13:4417] AH02034: Initial (No.1) HTTPS request received for child 201 (server OURDOMAIN:443) [Tue Jan 04 16:47:38.982818 2022] [authz_core:debug] [pid 138303:tid 138340] mod_authz_core.c(815): [client 108.54.237.13:4417] AH01626: authorization result of Require all granted: granted [Tue Jan 04 16:47:38.982835 2022] [authz_core:debug] [pid 138303:tid 138340] mod_authz_core.c(815): [client 108.54.237.13:4417] AH01626: authorization result of <RequireAny>: granted [Tue Jan 04 16:47:38.983049 2022] [proxy:debug] [pid 138303:tid 138340] mod_proxy.c(1503): [client 108.54.237.13:4417] AH01143: Running scheme unix handler (attempt 0) [Tue Jan 04 16:47:38.983068 2022] [proxy_ajp:debug] [pid 138303:tid 138340] mod_proxy_ajp.c(755): [client 108.54.237.13:4417] AH00894: declining URL fcgi://localhost/usr/share/squirrelmail/src/login.php [Tue Jan 04 16:47:38.983080 2022] [proxy_fcgi:debug] [pid 138303:tid 138340] mod_proxy_fcgi.c(1054): [client 108.54.237.13:4417] AH01076: url: fcgi://localhost/usr/share/squirrelmail/src/login.php proxyname: (null) proxyport: 0 [Tue Jan 04 16:47:38.983130 2022] [proxy_fcgi:debug] [pid 138303:tid 138340] mod_proxy_fcgi.c(1063): [client 108.54.237.13:4417] AH01078: serving URL fcgi://localhost/usr/share/squirrelmail/src/login.php [Tue Jan 04 16:47:38.983152 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(2531): AH00942: FCGI: has acquired connection for (*) [Tue Jan 04 16:47:38.983166 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(2587): [client 108.54.237.13:4417] AH00944: connecting fcgi://localhost/usr/share/squirrelmail/src/login.php to localhost:8000 [Tue Jan 04 16:47:38.983178 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(2623): [client 108.54.237.13:4417] AH02545: fcgi: has determined UDS as /run/php-fpm/www.sock [Tue Jan 04 16:47:38.983273 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(2810): [client 108.54.237.13:4417] AH00947: connected /usr/share/squirrelmail/src/login.php to httpd-UDS:0 [Tue Jan 04 16:47:38.983340 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(3177): AH02823: FCGI: connection established with Unix domain socket /run/php-fpm/www.sock (*) [Tue Jan 04 16:47:38.985967 2022] [proxy:debug] [pid 138303:tid 138340] proxy_util.c(2546): AH00943: FCGI: has released connection for (*) [Tue Jan 04 16:47:39.905828 2022] [ssl:debug] [pid 138303:tid 138339] ssl_engine_kernel.c(415): [client 108.54.237.13:4417] AH02034: Subsequent (No.2) HTTPS request received for child 200 (server OURDOMAIN:443), referer: https://OURDOMAIN/webmail/src/login.php [Tue Jan 04 16:47:39.906059 2022] [authz_core:debug] [pid 138303:tid 138339] mod_authz_core.c(815): [client 108.54.237.13:4417] AH01626: authorization result of Require all granted: granted, referer: https://OURDOMAIN/webmail/src/login.php [Tue Jan 04 16:47:39.906082 2022] [authz_core:debug] [pid 138303:tid 138339] mod_authz_core.c(815): [client 108.54.237.13:4417] AH01626: authorization result of <RequireAny>: granted, referer: https://OURDOMAIN/webmail/src/login.php |
|
From: Paul L. <pa...@sq...> - 2022-01-04 21:36:11
|
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 loading plain HTML pages but webmail gets an internal server error, > 500. More than likely the SSL connection problem is happening at a layer above SquirrelMail. I'd first try to get a static page to load using that same certificate/domain and then try SquirrelMail, also keeping an eye on the PHP logs as well. > I enabled debug logging and below is what I see in the SSl error logs with > these 2 lines having errors: > AH02008: SSL library error 1 in handshake (server OURDOMAIN:443) > SSL Library Error: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert > certificate unknown (SSL alert number 46) -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Robert K. <rk...@fo...> - 2022-01-04 21:18:05
|
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 with these 2 lines having errors: AH02008: SSL library error 1 in handshake (server OURDOMAIN:443) SSL Library Error: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown (SSL alert number 46) In context: [Tue Jan 04 16:13:33.661487 2022] [ssl:info] [pid 77902:tid 77948] [client 108.54.237.13:1092] AH01964: Connection to child 210 established (server OURDOMAIN:443) [Tue Jan 04 16:13:33.661714 2022] [ssl:debug] [pid 77902:tid 77948] ssl_engine_kernel.c(2425): [client 108.54.237.13:1092] AH02645: Server name not provided via TLS extension (using default/first virtual host) [Tue Jan 04 16:13:33.661869 2022] [core:debug] [pid 77902:tid 77948] protocol.c(2449): [client 108.54.237.13:1092] AH03155: select protocol from , choices=h2,http/1.1 for server OURDOMAIN [Tue Jan 04 16:13:33.672615 2022] [socache_shmcb:debug] [pid 77902:tid 77948] mod_socache_shmcb.c(570): AH00837: socache_shmcb_remove (0x3c -> subcache 28) [Tue Jan 04 16:13:33.672649 2022] [socache_shmcb:debug] [pid 77902:tid 77948] mod_socache_shmcb.c(954): AH00852: possible match at idx=2, data=438 [Tue Jan 04 16:13:33.672659 2022] [socache_shmcb:debug] [pid 77902:tid 77948] mod_socache_shmcb.c(959): AH00853: shmcb_subcache_remove removing matching entry [Tue Jan 04 16:13:33.672669 2022] [socache_shmcb:debug] [pid 77902:tid 77948] mod_socache_shmcb.c(585): AH00839: leaving socache_shmcb_remove successfully [Tue Jan 04 16:13:33.672683 2022] [ssl:info] [pid 77902:tid 77948] [client 108.54.237.13:1092] AH02008: SSL library error 1 in handshake (server OURDOMAIN:443) [Tue Jan 04 16:13:33.672715 2022] [ssl:info] [pid 77902:tid 77948] SSL Library Error: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown (SSL alert number 46) [Tue Jan 04 16:13:33.672731 2022] [ssl:info] [pid 77902:tid 77948] [client 108.54.237.13:1092] AH01998: Connection closed to child 210 with abortive shutdown (server OURDOMAIN:443) [Tue Jan 04 16:13:33.683683 2022] [ssl:info] [pid 77902:tid 77937] [client 108.54.237.13:1095] AH01964: Connection to child 199 established (server OURDOMAIN:443) [Tue Jan 04 16:13:33.683823 2022] [ssl:debug] [pid 77902:tid 77937] ssl_engine_kernel.c(2425): [client 108.54.237.13:1095] AH02645: Server name not provided via TLS extension (using default/first virtual host) [Tue Jan 04 16:13:33.683876 2022] [core:debug] [pid 77902:tid 77937] protocol.c(2449): [client 108.54.237.13:1095] AH03155: select protocol from , choices=h2,http/1.1 for server OURDOMAIN [Tue Jan 04 16:13:33.701176 2022] [ssl:debug] [pid 77902:tid 77937] ssl_engine_kernel.c(2254): [client 108.54.237.13:1095] AH02041: Protocol: TLSv1.3, Cipher: TLS_AES_256_GCM_SHA384 (256/256 bits) [Tue Jan 04 16:13:33.701312 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(508): AH00831: socache_shmcb_store (0xe3 -> subcache 3) [Tue Jan 04 16:13:33.701329 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(745): AH00842: expiring 1 and reclaiming 0 removed socache entries [Tue Jan 04 16:13:33.701338 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(765): AH00843: we now have 0 socache entries [Tue Jan 04 16:13:33.701350 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(862): AH00847: insert happened at idx=3, data=(677:709) [Tue Jan 04 16:13:33.701360 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(865): AH00848: finished insert, subcache: idx_pos/idx_used=3/1, data_pos/data_used=677/201 [Tue Jan 04 16:13:33.701370 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(530): AH00834: leaving socache_shmcb_store successfully [Tue Jan 04 16:13:33.701494 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(508): AH00831: socache_shmcb_store (0x43 -> subcache 3) [Tue Jan 04 16:13:33.701511 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(862): AH00847: insert happened at idx=4, data=(878:910) [Tue Jan 04 16:13:33.701519 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(865): AH00848: finished insert, subcache: idx_pos/idx_used=3/2, data_pos/data_used=677/402 [Tue Jan 04 16:13:33.701528 2022] [socache_shmcb:debug] [pid 77902:tid 77937] mod_socache_shmcb.c(530): AH00834: leaving socache_shmcb_store successfully [Tue Jan 04 16:13:33.701713 2022] [ssl:debug] [pid 77902:tid 77937] ssl_engine_kernel.c(415): [client 108.54.237.13:1095] AH02034: Initial (No.1) HTTPS request received for child 199 (server OURDOMAIN:443) [Tue Jan 04 16:13:33.701903 2022] [authz_core:debug] [pid 77902:tid 77937] mod_authz_core.c(815): [client 108.54.237.13:1095] AH01626: authorization result of Require all granted: granted [Tue Jan 04 16:13:33.701921 2022] [authz_core:debug] [pid 77902:tid 77937] mod_authz_core.c(815): [client 108.54.237.13:1095] AH01626: authorization result of <RequireAny>: granted [Tue Jan 04 16:13:33.702127 2022] [proxy:debug] [pid 77902:tid 77937] mod_proxy.c(1503): [client 108.54.237.13:1095] AH01143: Running scheme unix handler (attempt 0) [Tue Jan 04 16:13:33.702153 2022] [proxy_ajp:debug] [pid 77902:tid 77937] mod_proxy_ajp.c(755): [client 108.54.237.13:1095] AH00894: declining URL fcgi://localhost/usr/share/squirrelmail/src/login.php [Tue Jan 04 16:13:33.702167 2022] [proxy_fcgi:debug] [pid 77902:tid 77937] mod_proxy_fcgi.c(1054): [client 108.54.237.13:1095] AH01076: url: fcgi://localhost/usr/share/squirrelmail/src/login.php proxyname: (null) proxyport: 0 [Tue Jan 04 16:13:33.702179 2022] [proxy_fcgi:debug] [pid 77902:tid 77937] mod_proxy_fcgi.c(1063): [client 108.54.237.13:1095] AH01078: serving URL fcgi://localhost/usr/share/squirrelmail/src/login.php [Tue Jan 04 16:13:33.702191 2022] [proxy:debug] [pid 77902:tid 77937] proxy_util.c(2531): AH00942: FCGI: has acquired connection for (*) [Tue Jan 04 16:13:33.702205 2022] [proxy:debug] [pid 77902:tid 77937] proxy_util.c(2587): [client 108.54.237.13:1095] AH00944: connecting fcgi://localhost/usr/share/squirrelmail/src/login.php to localhost:8000 [Tue Jan 04 16:13:33.702217 2022] [proxy:debug] [pid 77902:tid 77937] proxy_util.c(2623): [client 108.54.237.13:1095] AH02545: fcgi: has determined UDS as /run/php-fpm/www.sock [Tue Jan 04 16:13:33.702317 2022] [proxy:debug] [pid 77902:tid 77937] proxy_util.c(2810): [client 108.54.237.13:1095] AH00947: connected /usr/share/squirrelmail/src/login.php to httpd-UDS:0 [Tue Jan 04 16:13:33.702378 2022] [proxy:debug] [pid 77902:tid 77937] proxy_util.c(3177): AH02823: FCGI: connection established with Unix domain socket /run/php-fpm/www.sock (*) [Tue Jan 04 16:13:33.704872 2022] [proxy:debug] [pid 77902:tid 77937] proxy_util.c(2546): AH00943: FCGI: has released connection for (*) [Tue Jan 04 16:13:33.705352 2022] [ssl:debug] [pid 77902:tid 77937] ssl_engine_io.c(1147): [client 108.54.237.13:1095] AH02001: Connection closed to child 199 with standard shutdown (server OURDOMAIN:443) [Tue Jan 04 16:13:33.751263 2022] [ssl:info] [pid 77902:tid 77943] [client 31.205.216.198:58085] AH01964: Connection to child 205 established (server OURDOMAIN:443) [Tue Jan 04 16:13:33.751443 2022] [ssl:debug] [pid 77902:tid 77943] ssl_engine_kernel.c(2395): [client 31.205.216.198:58085] AH02043: SSL virtual host for servername OURDOMAIN found [Tue Jan 04 16:13:33.751493 2022] [ssl:info] [pid 77902:tid 77945] [client 31.205.216.198:58086] AH01964: Connection to child 207 established (server OURDOMAIN:443) [Tue Jan 04 16:13:33.751592 2022] [core:debug] [pid 77902:tid 77943] protocol.c(2449): [client 31.205.216.198:58085] AH03155: select protocol from , choices=h2,http/1.1 for server OURDOMAIN [Tue Jan 04 16:13:33.751653 2022] [ssl:debug] [pid 77902:tid 77945] ssl_engine_kernel.c(2395): [client 31.205.216.198:58086] AH02043: SSL virtual host for servername OURDOMAIN found [Tue Jan 04 16:13:33.751795 2022] [core:debug] [pid 77902:tid 77945] protocol.c(2449): [client 31.205.216.198:58086] AH03155: select protocol from , choices=h2,http/1.1 for server OURDOMAIN [Tue Jan 04 16:13:33.913997 2022] [ssl:debug] [pid 77902:tid 77943] ssl_engine_kernel.c(2254): [client 31.205.216.198:58085] AH02041: Protocol: TLSv1.3, Cipher: TLS_AES_256_GCM_SHA384 (256/256 bits) [Tue Jan 04 16:13:33.914150 2022] [socache_shmcb:debug] [pid 77902:tid 77943] mod_socache_shmcb.c(508): AH00831: socache_shmcb_store (0x74 -> subcache 20) [Tue Jan 04 16:13:33.914174 2022] [socache_shmcb:debug] [pid 77902:tid 77943] mod_socache_shmcb.c(862): AH00847: insert happened at idx=7, data=(1554:1586) [Tue Jan 04 16:13:33.914184 2022] [socache_shmcb:debug] [pid 77902:tid 77943] mod_socache_shmcb.c(865): AH00848: finished insert, subcache: idx_pos/idx_used=5/3, data_pos/data_used=1116/664 [Tue Jan 04 16:13:33.914195 2022] [socache_shmcb:debug] [pid 77902:tid 77943] mod_socache_shmcb.c(530): AH00834: leaving socache_shmcb_store successfully [Tue Jan 04 16:13:33.915172 2022] [ssl:debug] [pid 77902:tid 77945] ssl_engine_kernel.c(2254): [client 31.205.216.198:58086] AH02041: Protocol: TLSv1.3, Cipher: TLS_AES_256_GCM_SHA384 (256/256 bits) [Tue Jan 04 16:13:33.915309 2022] [socache_shmcb:debug] [pid 77902:tid 77945] mod_socache_shmcb.c(508): AH00831: socache_shmcb_store (0x4f -> subcache 15) [Tue Jan 04 16:13:33.915327 2022] [socache_shmcb:debug] [pid 77902:tid 77945] mod_socache_shmcb.c(862): AH00847: insert happened at idx=3, data=(653:685) [Tue Jan 04 16:13:33.915337 2022] [socache_shmcb:debug] [pid 77902:tid 77945] mod_socache_shmcb.c(865): AH00848: finished insert, subcache: idx_pos/idx_used=2/2, data_pos/data_used=439/439 [Tue Jan 04 16:13:33.915348 2022] [socache_shmcb:debug] [pid 77902:tid 77945] mod_socache_shmcb.c(530): AH00834: leaving socache_shmcb_store successfully We do use certbot/Let's Encrypt. Is there a setting that needs changing? Thanks and Happy New Year! Rob |
|
From: Jay H. <jh...@ke...> - 2021-12-07 01:15:14
|
Hey, I want to thank Paul for creating a plugin that allows a user to change the "From" and "To" fields in folders. I've now got 15 years of stored email that I see whom I sent it to. Thank you Paul, for making this happen!!! Jay > Good Morning. > > I save off my email via years. I created a folder called "old-email", and as sub-folders to this, I create two folders for each year; 1) > 'email-year', and 2) 'sent-email-year'. > > The structure looks like this (using 2005 as the 'year'): > > - old-email > - email-2005 > - email-2006 > - sent-email-2005 > - etc, etc, etc > > > Problem/Issue: The 'received' email folder (ie email-2005) has the From field displayed, so I know the sender. The 'sent-email-2005' > folder is also displaying the 'From' field, but I need it to show the "To" field, so I know who the recipient is. > > How can I change this??? > > My assumption is this is more a postfix/dovecot issue, but I'm hoping someone can steer me to the file needed to modify... > > Thanks, > > Jay > |
|
From: James B. B. <by...@ha...> - 2021-12-06 22:29:30
|
On Mon, December 6, 2021 16:14, Paul Lesniewski wrote:
>
>
> On Mon, December 6, 2021 4:00 pm, James B. Byrne via squirrelmail-users
> wrote:
>> Can someone please tell me where I can find the share calendar
>> administrative interface?
>
> If it's been configured already, "Calendar Administration" will show on
> the "Options" page. If you don't find that item listed, then you need to
> set your username in the config.php file, under $cal_admins
>
Thank you.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Unencrypted messages have no legal claim to privacy
Do NOT open attachments nor follow links sent by e-Mail
James B. Byrne mailto:By...@Ha...
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
|
|
From: Paul L. <pa...@sq...> - 2021-12-06 21:14:38
|
On Mon, December 6, 2021 4:00 pm, James B. Byrne via squirrelmail-users wrote: > This is due to a failing memory, and compounded by a somewhat obscure SM > configuration interface. How does one add and remove users from shared > calendars? I have done this in the past. And I recall the the method was > located in some out of the way place. But I cannot recall where that is. > > Can someone please tell me where I can find the share calendar > administrative interface? If it's been configured already, "Calendar Administration" will show on the "Options" page. If you don't find that item listed, then you need to set your username in the config.php file, under $cal_admins -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: James B. B. <by...@ha...> - 2021-12-06 16:15:57
|
This is due to a failing memory, and compounded by a somewhat obscure SM
configuration interface. How does one add and remove users from shared
calendars? I have done this in the past. And I recall the the method was
located in some out of the way place. But I cannot recall where that is.
Can someone please tell me where I can find the share calendar administrative
interface?
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Unencrypted messages have no legal claim to privacy
Do NOT open attachments nor follow links sent by e-Mail
James B. Byrne mailto:By...@Ha...
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
|
|
From: Paul L. <pa...@sq...> - 2021-12-04 21:09:22
|
> Problem/Issue: The 'received' email folder (ie email-2005) has the From > field displayed, so I know the sender. The 'sent-email-2005' > folder is also displaying the 'From' field, but I need it to show the "To" > field, so I know who the recipient is. > > How can I change this??? There isn't, but should be, a plugin that can handle that for you. The primary hook you want for that is called "check_handleAsSent_result" If you aren't up for doing that yourself and you'd like to encourage me to write that plugin for you and beta test it, please contact me offlist. Cheers, -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Jay H. <jh...@ke...> - 2021-12-03 14:05:02
|
Good Morning. I save off my email via years. I created a folder called "old-email", and as sub-folders to this, I create two folders for each year; 1) 'email-year', and 2) 'sent-email-year'. The structure looks like this (using 2005 as the 'year'): - old-email - email-2005 - email-2006 - sent-email-2005 - etc, etc, etc Problem/Issue: The 'received' email folder (ie email-2005) has the From field displayed, so I know the sender. The 'sent-email-2005' folder is also displaying the 'From' field, but I need it to show the "To" field, so I know who the recipient is. How can I change this??? My assumption is this is more a postfix/dovecot issue, but I'm hoping someone can steer me to the file needed to modify... Thanks, Jay |
|
From: Paul L. <pa...@sq...> - 2021-11-20 20:11:31
|
On Sat, November 20, 2021 1:23 pm, Jay Hart wrote: >> >>>> patch -d ../../ -p2 < patches/xxxx.diff >>>> >>>> You may need to fiddle with the options until you get it right. >>>> >>> >>> This appeared to run better, but I ended up with this: >>> >>> [root@dream msg_flags]# patch -d ../../ -p2 < >>> patches/msg_flags-squirrelmail-1.4.20.diff >>> patching file functions/mailbox_display.php >>> Reversed (or previously applied) patch detected! Assume -R? [n] >>> >>> What do I want to do here??? >> >> Select 'no', or if you want to be sure you applied everything correctly, >> select 'yes' and see if it "unpatches" itself correctly. If not, you'll >> want to start from scratch. Otherwise, re-apply the patch and you're >> good. >> > > Ok, here is how things went: > [root@dream msg_flags]# patch -d ../../ -p2 < I don't recommend you work as root, especially if you are unsure about the commands you're running; even typos can end up being disastrous. > patches/msg_flags-squirrelmail-1.4.20.diff > patching file functions/mailbox_display.php > Reversed (or previously applied) patch detected! Assume -R? [n] n > Apply anyway? [n] n > Skipping patch. > 2 out of 2 hunks ignored -- saving rejects to file > functions/mailbox_display.php.rej > patching file src/move_messages.php > Hunk #1 succeeded at 150 with fuzz 2 (offset 13 lines). > Hunk #2 succeeded at 224 (offset 21 lines). > patching file src/left_main.php > Hunk #1 succeeded at 78 (offset 2 lines). > Hunk #2 succeeded at 192 (offset 2 lines). Yuck, one file was patched, the others not... although it looks like you applied everything, I'd personally start with a fresh codebase and apply the patches, making sure they all go in the first time. > 2. This plugin has other patches, do I apply just the 1.4.20 patch, or > others as well? > > msg_flags-squirrelmail-1.4.10.diff > msg_flags-squirrelmail-1.4.13.diff > msg_flags-squirrelmail-1.4.15.diff > msg_flags-squirrelmail-1.4.20.diff > msg_flags-squirrelmail-1.4.3a.diff > > I assume the 1.4.20 diff contains all the other patches, correct? This is > hinted at in the instructions. Yes, ignore all but the newest version. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Jay H. <jh...@ke...> - 2021-11-20 13:24:16
|
> >>> patch -d ../../ -p2 < patches/xxxx.diff >>> >>> You may need to fiddle with the options until you get it right. >>> >> >> This appeared to run better, but I ended up with this: >> >> [root@dream msg_flags]# patch -d ../../ -p2 < >> patches/msg_flags-squirrelmail-1.4.20.diff >> patching file functions/mailbox_display.php >> Reversed (or previously applied) patch detected! Assume -R? [n] >> >> What do I want to do here??? > > Select 'no', or if you want to be sure you applied everything correctly, > select 'yes' and see if it "unpatches" itself correctly. If not, you'll > want to start from scratch. Otherwise, re-apply the patch and you're > good. > Ok, here is how things went: [root@dream msg_flags]# patch -d ../../ -p2 < patches/msg_flags-squirrelmail-1.4.20.diff patching file functions/mailbox_display.php Reversed (or previously applied) patch detected! Assume -R? [n] n Apply anyway? [n] n Skipping patch. 2 out of 2 hunks ignored -- saving rejects to file functions/mailbox_display.php.rej patching file src/move_messages.php Hunk #1 succeeded at 150 with fuzz 2 (offset 13 lines). Hunk #2 succeeded at 224 (offset 21 lines). patching file src/left_main.php Hunk #1 succeeded at 78 (offset 2 lines). Hunk #2 succeeded at 192 (offset 2 lines). Questions: 1. Reapply or leave as-is? 2. This plugin has other patches, do I apply just the 1.4.20 patch, or others as well? msg_flags-squirrelmail-1.4.10.diff msg_flags-squirrelmail-1.4.13.diff msg_flags-squirrelmail-1.4.15.diff msg_flags-squirrelmail-1.4.20.diff msg_flags-squirrelmail-1.4.3a.diff I assume the 1.4.20 diff contains all the other patches, correct? This is hinted at in the instructions. Thanks for the support so far. And earlier, when I said I "can't patch", it was because of the issue we just worked through. Thanks for the help again. Jay >> This was the version of the msg_flags plugin I downloaded: >> msg_flags-1.4.20-1.4.3.tar.gz >> >> Sounds like I don't 'need' to patch? Should select 'n'?? > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php > > > > > > ----- > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squ...@li... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > |
|
From: Paul L. <pa...@sq...> - 2021-11-20 03:35:23
|
>> patch -d ../../ -p2 < patches/xxxx.diff >> >> You may need to fiddle with the options until you get it right. >> > > This appeared to run better, but I ended up with this: > > [root@dream msg_flags]# patch -d ../../ -p2 < > patches/msg_flags-squirrelmail-1.4.20.diff > patching file functions/mailbox_display.php > Reversed (or previously applied) patch detected! Assume -R? [n] > > What do I want to do here??? Select 'no', or if you want to be sure you applied everything correctly, select 'yes' and see if it "unpatches" itself correctly. If not, you'll want to start from scratch. Otherwise, re-apply the patch and you're good. > This was the version of the msg_flags plugin I downloaded: > msg_flags-1.4.20-1.4.3.tar.gz > > Sounds like I don't 'need' to patch? Should select 'n'?? -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Jay H. <jh...@ke...> - 2021-11-20 03:29:01
|
> > > On Sat, November 20, 2021 1:39 am, Jay Hart wrote: >> A few notes below on the first issues I noted with the interface. I >> disabled the 'preview-pane' plugin and resolved most of the issues. >> I'll show which ones below. I don't use 'preview-pane' view, so it >> appears this plugin was still having some effect on the interface just >> by being loaded/enabled in the ./conf.pl config, with no options checked >> in the display settings.. > > It comes with patches for full installation, that could easily be the > problem. An updated version of this is also available offlist. > >> The problem with patching is it appears the fact these plugins have >> 'newer' file stamps, is causing patch to say the files don't exist. > > Nothing to do with date stamps. It's a file path problem. You can just > copy/type in the file path that is given just above and it should work or > IIRC run the patch command like so (from the directory of whatever plugin > it is that you are patching for): > > patch -d ../../ -p2 < patches/xxxx.diff > > You may need to fiddle with the options until you get it right. > This appeared to run better, but I ended up with this: [root@dream msg_flags]# patch -d ../../ -p2 < patches/msg_flags-squirrelmail-1.4.20.diff patching file functions/mailbox_display.php Reversed (or previously applied) patch detected! Assume -R? [n] What do I want to do here??? This was the version of the msg_flags plugin I downloaded: msg_flags-1.4.20-1.4.3.tar.gz Sounds like I don't 'need' to patch? Should select 'n'?? Jay >> Here is what I see when trying to patch msg_flags: >> >> [root@dream msg_flags]# patch -p0 < >> patches/msg_flags-squirrelmail-1.4.20.diff >> can't find file to patch at input line 3 >> Perhaps you used the wrong -p or --strip option? >> The text leading up to this was: >> -------------------------- >> |--- ../../functions/mailbox_display.php.orig 2008-02-10 >> 08:49:47.000000000 -0800 >> |+++ ../../functions/mailbox_display.php 2008-06-11 >> 06:41:00.000000000 -0700 >> -------------------------- >> File to patch: >> >> I am NO EXPERT here, looking for assistance on how to resolve, if I need >> too! > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php > > > > > ----- > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squ...@li... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > |
238 messages has been excluded from this view by a project administrator.
