2025.Július 5.(Szo) 06:40 időpontban Harold Hallikainen via
squirrelmail-users ezt írta:
> Never mind! It looks like fail2ban already has something for this. I just
> have to figure out how to configure it.
It depends on the IMAP server and the type of authentication. In my case
dovecot performs l
Never mind! It looks like fail2ban already has something for this. I just
have to figure out how to configure it.
Thanks!
Harold
On Fri, July 4, 2025 4:59 pm, Harold Hallikainen via squirrelmail-users
wrote:
> Is this possible? I get several hundered ssh login failures each day that
> I pass to
Is this possible? I get several hundered ssh login failures each day that
I pass to fail2ban to block those IP addresses. It seems like there MIGHT
similarly be SM login failures that would be nice to block.
Harold
--
Not sent from an iPhone.
-
squirrelmail-users mailing list
Posting gu
FYI, all the notices below are fixed in our repository and those fixes
will be available in our next nightly snapshots on our downloads page.
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php
>
>
> > but I'm REALLY hoping you can fix
> > these soon.
>
> Why? These are notices of a future incompatibility. The problem you seem
> to be facing is you have these notices set to display on screen, which is
> your primary problem. You need to turn off display_errors in your PHP
> configuration.
> When composing a new message, I have the following warning/error in the
> compose text box:
>
> Deprecated: explode(): Passing null to parameter #2 ($string) of
> type string is deprecated in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mime.php
> on line 693
This is also fix
Thanks for these reports. The following notices are all fixed in our
repository and will appear in our next nightly snapshots.
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php
> Deprecated: C
> More warnings from Disposition.class.php when viewing different messages.
>
> Deprecated: Creation of dynamic property Disposition::$name is deprecated
> in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/class/mime/Disposition.class.php
> on line 30
> Deprecated: Creation of dynamic propert
> These occur when composing/sending a new message.
> Warning: Undefined array key "" in
> /usr/share/squirrelmail-stable-1.4.23-svn-073024/functions/mailbox_display.php
> on line 76
This appears to indicate your message cache is corrupt. Just above line
76, you can put something like this:
if (
On Thu, September 12, 2024 12:00 am, Harold Hallikainen via
squirrelmail-users wrote:
> According to conf.pl, I have this plugin installed (
> https://www.squirrelmail.org/plugin_view.php?id=205 ), but I do not see
> the download all link after the list of attachments.
>
> Ideas?
Explain how yo
On Thu, January 25, 2024 8:26 pm, James B. Byrne wrote:
> On Thu, January 25, 2024 14:38, Paul Lesniewski wrote:
>>> I have gotten SM to run under php-8.3. However, following
>>> authentication
>>> I now
>>> see this in the message pane:
>>>
>>> ERROR: Bad or malformed request.
>>> Query: FETCH
Correction: Calendar Preferences is where the shared calendar option is set but
none of the settings for shared calendars are displayed. Also, in calendar
administration one cannot add users or calendars.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensiti
On Thu, January 25, 2024 15:40, James B. Byrne via squirrelmail-users wrote:
> How can I debug why the shared calendar plugin does not function? This is
> using SM 20240125 stable.
>
By renaming the calendar plugin directory and adding a soft link from calendar
to shared_calendars I now have the
How can I debug why the shared calendar plugin does not function? This is
using SM 20240125 stable.
--
*** 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
On Thu, January 25, 2024 14:38, Paul Lesniewski wrote:
>> I have gotten SM to run under php-8.3. However, following authentication
>> I now
>> see this in the message pane:
>>
>> ERROR: Bad or malformed request.
>> Query: FETCH 1,3:5,7,10,12,18:19,28,50,119,121:123,125,127:128,132:135,138
>> (FLAG
> I have gotten SM to run under php-8.3. However, following authentication
> I now
> see this in the message pane:
>
> ERROR: Bad or malformed request.
> Query: FETCH 1,3:5,7,10,12,18:19,28,50,119,121:123,125,127:128,132:135,138
> (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date T
Hello,
I have gotten SM to run under php-8.3. However, following authentication I now
see this in the message pane:
ERROR: Bad or malformed request.
Query: FETCH 1,3:5,7,10,12,18:19,28,50,119,121:123,125,127:128,132:135,138
(FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc
On Thu, January 25, 2024 10:16, James B. Byrne via squirrelmail-users wrote:
>
> Fatal error: Uncaught ArgumentCountError: Too few arguments to function
> simpleErrorHandler(), 4 passed in
> /usr/local/www/squirrelmail/plugins/vlogin/functions.php on line 187 and
> exactly 5 expected in
> /usr/loc
On Tue, January 23, 2024 16:26, Paul Lesniewski wrote:
>
> Your PHP isn't logging errors or you aren't looking at the right log file.
> See:
>
> https://www.squirrelmail.org/docs/admin/admin-11.html#ss11.1
>
>
There was an additional php package required (mod_php83) that was not pulled in
by the u
On Tue, January 23, 2024 8:49 pm, James B. Byrne via squirrelmail-users
wrote:
> I have to upgrade our webmail host to FreeBSd-13.2. This necessitates an
> upgrade to php as 7.3 is no longer supported. This in turn requires that
> squirrelmail be updated via freebsd's pkg system. The version o
I have to upgrade our webmail host to FreeBSd-13.2. This necessitates an
upgrade to php as 7.3 is no longer supported. This in turn requires that
squirrelmail be updated via freebsd's pkg system. The version of squirrelmail
is unknow as the package manager reports: Version : 20230207 and the port
On Wed, January 17, 2024 7:03 pm, Alex wrote:
> Hi,
>
> php8.2 on fedora38 when clicking "Day View" from the Calendar
>
> Fatal error: Uncaught Error: Call to undefined function each() in
> /usr/share/squirrelmail/plugins/calendar/day.php:99 Stack trace: #0
> /usr/share/squirrelmail/plugins/cale
Hi,
php8.2 on fedora38 when clicking "Day View" from the Calendar
Fatal error: Uncaught Error: Call to undefined function each() in
/usr/share/squirrelmail/plugins/calendar/day.php:99 Stack trace: #0
/usr/share/squirrelmail/plugins/calendar/day.php(177): display_events() #1
{main} thrown in /usr/
Please don't top-post, thanks.
>>> Ha! That clears up the matter. Thank you so much!
>>
>> FYI, you can see who the mail was sent to in 1.4.x by hovering your
>> mouse
>> over the checkbox.
>
> Yes, that works! Thank you. We needed "To" only on Sent-Mail
> folder. But this is sufficient. Thank
Hi,
Yes, that works! Thank you. We needed "To" only on Sent-Mail
folder. But this is sufficient. Thanks again.
Regards,
Nandagopal
On Thu, December 7, 2023 9:00 am, V. Nandagopal wrote:
Hi,
Ha! That clears up the matter. Thank you so much!
FYI, you
On Thu, December 7, 2023 9:00 am, V. Nandagopal wrote:
> Hi,
>
> Ha! That clears up the matter. Thank you so much!
FYI, you can see who the mail was sent to in 1.4.x by hovering your mouse
over the checkbox.
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by don
Hi,
Ha! That clears up the matter. Thank you so much!
Regards,
Nandagopal
HTML source of the frame shows the elements are present. I have
not modified options_order.php at all and the error logs too
dont show anything. I noticed if I remove the
> HTML source of the frame shows the elements are present. I have
> not modified options_order.php at all and the error logs too
> dont show anything. I noticed if I remove the lines order1=1 to
> order6=6, I do get the dropdown menu and the Add button back,
> but th
Hi,
Many thanks for the quick reply.
HTML source of the frame shows the elements are present. I have
not modified options_order.php at all and the error logs too
dont show anything. I noticed if I remove the lines order1=1 to
order6=6, I do get the dropdow
> Bruce,
>
> First thing to do is install version 1.4.23, which is available as a SVN
> snapshot on our downloads page and should be quite stable and it might fix
> the errors in your log. The expired token seems like it may also be
> related with the PHP session problem in your environment.
>
Bruce,
On Tue, December 5, 2023 10:22 pm, Bruce Gowans wrote:
> I can receive emails just fine, but I cannot reply or compose a new one,
> and I'm trying to within 10 seconds after logging in.
>
> These are screenshots of the errors I receive when replying to an email,
> or composing a new message
I can receive emails just fine, but I cannot reply or compose a new one,
and I'm trying to within 10 seconds after logging in.
These are screenshots of the errors I receive when replying to an email,
or composing a new message.
https://i.postimg.cc/QxX0fQrf/Screen-Shot-1701781435.jpg - reply
h
Nandagopal,
> I installed Squirrelmail version 1.4.23
> (squirrelmail-20230831_0200-SVN.stable.tar.gz) on a Debian
> Buster system with Apache as web server and dove.
>
> It works fine, but in Indexing Order in Options, I am unable to add
> fields I want to be display
Dear All,
I installed Squirrelmail version 1.4.23
(squirrelmail-20230831_0200-SVN.stable.tar.gz) on a Debian
Buster system with Apache as web server and dove.
It works fine, but in Indexing Order in Options, I am unable to add
fields I want to be displayed
Hi,
It is found that the plugin package "tnef_decoder-1.0-1.4.0" contains
incompatibility with PHP 8.
On running "php -l functions.php", it returns
"PHP Fatal error: Array and string offset access syntax with curly
braces is no longer supported in functions.php on line 236".
This prevents the d
Hi,
I'm learning that the SVN version available as a tarball is different than
the "svn checkout" trunk version available on sf.net. I somehow missed that
the SVN development version of 1.4.23 was different than the stable version
of 1.4.23. This is the version that works:
svn checkout https://sv
Hi, this appears to be another issue related to php-8.1 compatibility. I
think this fixes it.
--- functions/file_prefs.php-foreach2023-02-13 19:09:58.956959936 -0500
+++ functions/file_prefs.php2023-02-13 19:10:10.975099888 -0500
@@ -125,7 +125,7 @@
logout_error( sprintf( _("Prefe
Hi, I think this is all that's necessary to fix the problem, but I'm not a
php developer, so I don't know if it's complete:
diff -u squirrelmail.stable/functions/file_prefs.php
squirrelmail-021223/functions/file_prefs.php
--- squirrelmail.stable/functions/file_prefs.php2023-01-02
20:22:36.
Hi, following up with my previous email -
It does look like there's still a problem. After installing the lockout and
compatibility plugin, it produces these deprecated errors:
Deprecated: Automatic conversion of false to array is deprecated in
/usr/share/squirrelmail/functions/file_prefs.php on
Hi, okay, I figured it out, thankfully. While I had a recent svn 1.4.23
snapshot, apparently it wasn't recent enough. The one from today (Feb 12,
2023) works.
What is the proper way to upgrade squirrelmail? I've just been building two
separate trees and manually going through each to identify diff
Hi, I'm using 1.4.22 on fedora36 with php-8.1 and receiving the following
errors. I thought SM supported php-8? Or is it a different problem? This
happens after logging in and redirect.php being loaded.
I shouldn't have done this on a production machine, so I'm really hoping
there's an easy fix :-
I did quite some testing and come up with some interesting results, shown
further down.
On Thu, 26 Jan 2023 23:54:54 -, "Paul Lesniewski"
wrote:
>
>
>
>On Thu, January 26, 2023 7:37 pm, rtc--- via squirrelmail-users wrote:
>> Hello All,
>> I am new here on the list but not new to SM. Using
On Thu, January 26, 2023 7:37 pm, rtc--- via squirrelmail-users wrote:
> Hello All,
> I am new here on the list but not new to SM. Using SM 1.4.4 with php5.4 on
> Win
> with Apache is working just fine. Thought is time for a new install, did
> that
> and ran into one major problem. Working and
Hello All,
I am new here on the list but not new to SM. Using SM 1.4.4 with php5.4 on Win
with Apache is working just fine. Thought is time for a new install, did that
and ran into one major problem. Working and looking into it for a few days,
but can't solve the problem. Config test shows my curr
> Postfix munges all mailbox names to lowercase which probably explains this
> behaviour. Squirrelmail evidently does not. Can SM be configured to do
> so?
The Login Manager (Vlogin) plugin will do that for you. It has a log of
features you won't want to use, but I think you can pare down one
FreeBSD-12.3 & 13.1
SM-1.4.23
We have this situation. Our mailstore is a Cyrus-imapd-3.0.17 installation
sitting behind a Postfix-3.7.2 MTA. Our webmail (Squirrelmail) host connects
over ssl using the imap server host for authentication.
We have encountered a situation where one of our staff log
FreeBSD 12.3-RELEASE-p2
SquirrelMail version 1.4.23 [SVN] (FreeBSD Ports pkg squirrelmail-php73
Version: 20211024)
We are encountering a situation where some messages are arriving with the
following bodystructure:
Bodystructure
Entity Content-TypeNameEncoding
1 text/plain
Hi list,
could you please check this bug report:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265395 ?
Is the fix correct?
Thanks,
Zsolt
-
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@lists.sourcefor
On Fri, April 22, 2022 11:22, James B. Byrne wrote:
>
> Access to SM through the firewall has been accomplished and users and see and
> send email without difficulty.
>
> The problem that has surfaced is that Firefox now gives a
> PR_CONNECT_RESET_ERROR whenever someone attempts to add a file mu
We had an equipment failure last night and I am trying to get various bits and
pieces working. The hardware was the gateway router and the replacement has a
different network stack. Consequently we are forced to finally correct an
addressing error made many, many years ago.
Access to SM through t
> sudo -u www tail
> /usr/local/www/squirrelmail/plugins/shared_calendars/setup.php
> ...
If that worked then I'd say you can start tracing the execution to see
where it fails. The easiest thing to do is just insert some output in the
code. Start with something like:
echo "Hello world";
And pu
On Thu, April 21, 2022 16:08, Paul Lesniewski wrote:
> Also check for things like SELinux context for the files and directories.
> It looks to me like some security/permissioning mechanism on your new
> server is preventing access to the files.
>
This is running a FreeBSD OS, there is no SELIN
On Thu, April 21, 2022 7:38 pm, James B. Byrne wrote:
>
>
> On Thu, April 21, 2022 15:08, Paul Lesniewski wrote:
>>
>>
>> If there are no typos in the config/config.php plugins[] entry for the
>> plugin, then the web server may not be able to load the plugin file(s).
>> Inspect the permissions f
On Thu, April 21, 2022 15:08, Paul Lesniewski wrote:
>
>
> If there are no typos in the config/config.php plugins[] entry for the
> plugin, then the web server may not be able to load the plugin file(s).
> Inspect the permissions for the plugin directory and files or manually
> test with somethi
On Thu, April 21, 2022 4:26 pm, James B. Byrne wrote:
> I have removed SM from the target host and reinstalled it from FreeBSD
> packages
> together with the packaged shared_calendar plugin. After configuring the
> new
> installation the problem remains in that there is no evidence that the
> p
On Tue, April 19, 2022 9:10 pm, James B. Byrne wrote:
>
>
> On Tue, April 19, 2022 16:53, Paul Lesniewski wrote:
>
>>
>> Did you watch for PHP errors?
> There are no PHP entries in /var/log/messages that cannot be accounted
> for.
>
>> Do the calendar administrative options show up for users lis
On Tue, April 19, 2022 16:53, Paul Lesniewski wrote:
>
> Did you watch for PHP errors?
There are no PHP entries in /var/log/messages that cannot be accounted for.
> Do the calendar administrative options show up for users listed in
> $cal_admins in the plugin configuration?
No, they do not.
>
On Tue, April 19, 2022 6:13 pm, James B. Byrne via squirrelmail-users wrote:
> FreeBSD-13.0
> SM 1.4.23
>
> I have SM running from a FreeBSD binary package for PHP81. I likewise
> have
> installed the shared_calendar plugin and its dependencies from FreeBSD
> packages. I have configured SM to l
On Thu, April 14, 2022 3:52 pm, James B. Byrne via squirrelmail-users wrote:
> OS FreeBSD-13.0
>
> I am migrating SM from one host to another. The new host runs php80. The
> old
> runs php73. I am using the FreeBSD port for SM on FreeBSD-13.0.
>
> There is a plugin that I installed many years
FreeBSD-13.0
SM 1.4.23
I have SM running from a FreeBSD binary package for PHP81. I likewise have
installed the shared_calendar plugin and its dependencies from FreeBSD
packages. I have configured SM to load this plugin. I also copied a
data/config.php file from another installation of SM where
I now have the current snapshot running on FreeBSD-13.0 under apache-2.4.53
connecting to cyrus imapd-3.0.17 running on a different host. This required
adjusting the $data_dir and $attachment_dir paths to match those used by the
FreeBSD port.
I can connect and authenticate. The left-hand-side fo
The issue is resolved. The problem was that the incorrect version of mod_php
was installed for Apache. Evidently the php81 pkg install does not check for
this and the Apache24 package was installed prior to php81.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT tra
On Fri, April 15, 2022 04:26, Paul Lesniewski wrote:
>
>
> On Thu, April 14, 2022 8:02 pm, James B. Byrne via squirrelmail-users wrote:
>> FreeBSD-13.0p11
>> php Version: 8.1.4_3
>>
>> I downloaded the most recent stable snapshot given above. I installed and
>> configured it. I enabled src/co
Dear All,
Here is an update. Please refer to the following link.
https://dovecot.org/pipermail/dovecot/2022-April/124504.html
Thank you.
Regards,
Mr. Turritopsis Dohrnii Teo En Ming
Targeted Individual in Singapore
17 April 2022 Sunday
On Sat, 16 Apr 2022 at 03:42, Paul Lesniewski wrote:
>
> Roundcube webmail doesn't show any error. Search results simply don't
> show up after a long time.
>
> However, I got the following error in Squirrelmail webmail (using
> Firefox web browser).
>
> ERROR: Connection dropped by IMAP server.
>
> Query: SEARCH CHARSET ISO-8859-1 ALL SUBJECT "keyword"
Subject: Both Roundcube and Squirrelmail webmail cannot search for
anything because there are more than 200,000 emails in my Inbox
Good day from Singapore,
I am using Virtualmin/Webmin web hosting control panel in my Virtual
Private Servers (VPS) in Germany.
Both Roundcube and Squirrelmail webma
On Thu, April 14, 2022 8:02 pm, James B. Byrne via squirrelmail-users wrote:
> FreeBSD-13.0p11
> php Version: 8.1.4_3
>
> I downloaded the most recent stable snapshot given above. I installed and
> configured it. I enabled src/configtest.php. When I visit this url I
> obtain
> this error:
>
FreeBSD-13.0p11
php Version: 8.1.4_3
I downloaded the most recent stable snapshot given above. I installed and
configured it. I enabled src/configtest.php. When I visit this url I obtain
this error:
[Thu Apr 14 15:55:50.272309 2022] [php:error] [pid 43532] [client
216.185.71.41:40396]
PHP Fat
OS FreeBSD-13.0
I am migrating SM from one host to another. The new host runs php80. The old
runs php73. I am using the FreeBSD port for SM on FreeBSD-13.0.
There is a plugin that I installed many years ago called quicksave. I cannot
find this in the prepackaged SM plugin ports. The version I
Hi Paul,
Ok thank you. I have some more questions but that will come later.
First I want
to see if the svn version gets rid of the bugs I found. You may get a
bug report,
I will see
On 3/16/22 14:05, Paul Lesniewski wrote:
Which php version should I be using? php-5 or
> Which php version should I be using? php-5 or php-7? I have found
> that the latest squirremail--webmail-1.4.22
> seems to work with both. Ah I see both are supported, but which would
> be better?
It makes no difference from SquirrelMail's perspective, but you should
generally always ke
Hi Everyone,
Which php version should I be using? php-5 or php-7? I have found
that the latest squirremail--webmail-1.4.22
seems to work with both. Ah I see both are supported, but which would
be better?
-
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.
Sorry for another email but we're just about there. One of our servers has
this error when clicking the Delete button. Delete & Previous | Delete &
Next work just fine.
session_start() [function.session-start]: Ignoring session_start() because
a session is already active
FILE: /usr/share/squirrel
]On Sun, Jan 30, 2022 at 8:44 PM Paul Lesniewski
wrote:
>
>
> On Sun, January 30, 2022 10:56 pm, Robert Kudyba wrote:
> > [image: white-frame.png]
> >
> > I've seen this in older versions but we have an instance of an email that
> > is very large, i.e., lots of text. It results in a blank/white f
On Sun, January 30, 2022 10:56 pm, Robert Kudyba wrote:
> [image: white-frame.png]
>
> I've seen this in older versions but we have an instance of an email that
> is very large, i.e., lots of text. It results in a blank/white frame and a
> 500 Internal Server Error. I was able to strace the php-
On Wed, January 19, 2022 5:12 am, Robert Kudyba wrote:
>>
>>
>> On Wed, January 19, 2022 1:39 am, Robert Kudyba wrote:
>> > Running squirrelmail-20220115_0200-SVN.devel.tar.gz
>>
>> Remember to make sure to indicate if this is version 1.4.23 or 1.5.2, in
>> this case I believe it is 1.4.23
>>
>
On Wed, January 19, 2022 1:39 am, Robert Kudyba wrote:
> Running squirrelmail-20220115_0200-SVN.devel.tar.gz
Remember to make sure to indicate if this is version 1.4.23 or 1.5.2, in
this case I believe it is 1.4.23
> on Fedora 35, PHP 8,
> the delete_move_next plugin generates this error:
>
>
Running squirrelmail-20220115_0200-SVN.devel.tar.gz on Fedora 35, PHP 8,
the delete_move_next plugin generates this error:
Category: PHP
Message: Trying to access array offset on value of type null
FILE: /usr/share/squirrelmail/plugins/delete_move_next/setup.php
LINE: 187
-
squirrelmail-users
> 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
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
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
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
>
> > 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
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
>> > 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
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.
> 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_
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
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
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
> 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
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
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
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
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 Administrat
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 me
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
> 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
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
On Sat, November 20, 2021 1:23 pm, Jay Hart wrote:
>>
patch -d ../../ -p2 < patches/.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 <
>
1 - 100 of 31411 matches
Mail list logo
