mailwatch-users Mailing List for MailWatch for MailScanner

While searching for a solution, I found this thread:
https://github.com/mailwatch/MailWatch/issues/1152.
I was able to apply a fix to my system similar to the one mentioned in this
comment
(https://github.com/mailwatch/MailWatch/issues/1152#issuecomment-558151037).
However, I had to modify the line for quarantine_release() slightly since my
actual MIME type is 'text/plain; charset=us-ascii'. Now this is, how it
looks: "preg_match('/^(message\/rfc822|text\/plain|text\/x-mail)/',
$list[$val]['type'])" in functions.php.

Is there a permanent solution to this issue? Also, is this problem related
to /usr/bin/file, MailScanner, or MailWatch?

Regards,
Jens

-----Original Message-----
From: Jens Potthast <jen...@in...> 
Sent: Montag, 26. August 2024 11:28
To: mai...@li...
Subject: Re: [Mailwatch-users] Troubleshooting Needed: Unable to Release
Blocked Emails

I can add some information to my last email that might be helpful in
troubleshooting the problem:

The function quarantine_release() in functions.php from line 3570 never
executes the command to release the email, because the regular expression on
line 3634 (preg_match('/message\/rfc822/', $list[$val]['type'])) never
matches.

In the quarantine folder, I have two files: 
1.) the blocked file (Office document) and
2.) a file named 'message'.

The types are: 
1.)
"application/vnd.openxmlformats-officedocument.wordprocessingml.document"
and
2.) "text/plain".

Why is 'message' of the wrong type?


Regards,
Jens


-----Original Message-----
From: Jens Potthast <jen...@in...>
Sent: Montag, 26. August 2024 10:31
To: Mai...@li...
Subject: [Mailwatch-users] Troubleshooting Needed: Unable to Release Blocked
Emails

Dear list,

I have been using MailWatch for many years without any issues, but I
recently encountered a problem (most likely) after upgrading Debian from
Bullseye to Bookworm. I am unable to release blocked emails from quarantine,
although SPAM emails can still be released successfully.

Here are the details of the issue:

    All checkboxes on /details.php are selected, and after clicking the
"Submit" button, the "Quarantine Command Result" shows no "Result Messages"
or "Error Messages".
    On /status.php, the email is not marked as released, indicating it has
not been released from quarantine.

Could you please assist me in debugging this issue or provide guidance on
what might be causing it? Any help you can offer would be greatly
appreciated.

Thank you for your support.

Best regards,
Jens 

I can add some information to my last email that might be helpful in
troubleshooting the problem:

The function quarantine_release() in functions.php from line 3570 never
executes the command to release the email, because the regular expression on
line 3634 (preg_match('/message\/rfc822/', $list[$val]['type'])) never
matches.

In the quarantine folder, I have two files: 
1.) the blocked file (Office document) and 
2.) a file named 'message'.

The types are: 
1.)
"application/vnd.openxmlformats-officedocument.wordprocessingml.document"
and 
2.) "text/plain".

Why is 'message' of the wrong type?


Regards,
Jens


-----Original Message-----
From: Jens Potthast <jen...@in...> 
Sent: Montag, 26. August 2024 10:31
To: Mai...@li...
Subject: [Mailwatch-users] Troubleshooting Needed: Unable to Release Blocked
Emails

Dear list,

I have been using MailWatch for many years without any issues, but I
recently encountered a problem (most likely) after upgrading Debian from
Bullseye to Bookworm. I am unable to release blocked emails from quarantine,
although SPAM emails can still be released successfully.

Here are the details of the issue:

    All checkboxes on /details.php are selected, and after clicking the
"Submit" button, the "Quarantine Command Result" shows no "Result Messages"
or "Error Messages".
    On /status.php, the email is not marked as released, indicating it has
not been released from quarantine.

Could you please assist me in debugging this issue or provide guidance on
what might be causing it? Any help you can offer would be greatly
appreciated.

Thank you for your support.

Best regards,
Jens 

Dear list,

I have been using MailWatch for many years without any issues, but I
recently encountered a problem (most likely) after upgrading Debian from
Bullseye to Bookworm. I am unable to release blocked emails from quarantine,
although SPAM emails can still be released successfully.

Here are the details of the issue:

    All checkboxes on /details.php are selected, and after clicking the
"Submit" button, the "Quarantine Command Result" shows no "Result Messages"
or "Error Messages".
    On /status.php, the email is not marked as released, indicating it has
not been released from quarantine.

Could you please assist me in debugging this issue or provide guidance on
what might be causing it? Any help you can offer would be greatly
appreciated.

Thank you for your support.

Best regards,
Jens 

Hello everyone,

I am looking for an experienced developer to customize
MailWatch/MailScanner with custom filters and additional features. This is
a paid opportunity, and I am open to discussing the specifics and your
rates.

If you are interested, please get in touch with me directly at [your email
address].

Thank you!

Best regards,

Raviv G

Hello,
I applied the patches to geoip_update.php and to Requests.php and now it works!
I also realized that in conf.php 'mylicensekey' must have been changed
with the one given by MaxMind...
Thank you very much,
my best greetings


On 1/26/24, Manuel Dalla Lana <end...@ar...> wrote:
> Il 24/01/24 20:17, P B ha scritto:
>> Thanks,
>> I applied the patch but still get an error.
>> "Downloading file, please wait...
>> Error occurred while downloading GeoIP data file"
>
>
> Do you get the error even after the last commit on GitHub
> (https://github.com/mailwatch/MailWatch/commit/03829bd22fdf464053fbc3f90a7f196969c45852)?
>
> That should fix the "internal corruption of phar" error.
>
>
>> I see that apache2 is using php7.2 while my system is using php8.3.
>> Can this be the problem?
>
>
> It's better to run MailWatch interface and cron jobs with the same
> version of php.
>
> Personally I haven't tested yet MailWatch with PHP 8.3, I'm still
> running it in production with 8.1, as I still have to deal with
> utf8_encode() and utf8_decode() deprecation on PHP 8.2
>
>
>> Is it possible to install manually the geoip database? I downloaded
>> manually the  GeoLite2-Country.tar.gz file but do not know what to do
>> with it...
>
> Yes, just copy the mmdb file to "mailscanner/temp/GeoLite2-Country.mmdb"
>
>
> Manuel
>

Il 24/01/24 20:17, P B ha scritto:
> Thanks,
> I applied the patch but still get an error.
> "Downloading file, please wait...
> Error occurred while downloading GeoIP data file"


Do you get the error even after the last commit on GitHub 
(https://github.com/mailwatch/MailWatch/commit/03829bd22fdf464053fbc3f90a7f196969c45852)?

That should fix the "internal corruption of phar" error.


> I see that apache2 is using php7.2 while my system is using php8.3.
> Can this be the problem?


It's better to run MailWatch interface and cron jobs with the same 
version of php.

Personally I haven't tested yet MailWatch with PHP 8.3, I'm still 
running it in production with 8.1, as I still have to deal with 
utf8_encode() and utf8_decode() deprecation on PHP 8.2


> Is it possible to install manually the geoip database? I downloaded
> manually the  GeoLite2-Country.tar.gz file but do not know what to do
> with it...

Yes, just copy the mmdb file to "mailscanner/temp/GeoLite2-Country.mmdb"


Manuel

Thanks,
I applied the patch but still get an error.
"Downloading file, please wait...
Error occurred while downloading GeoIP data file"

>From the apache2 error.log I got:
[Wed Jan 24 21:36:41.600754 2024] [php7:error] [pid 16301] [client
192.168.122.1:38548] PHP Fatal error:  Uncaught
UnexpectedValueException: internal corruption of phar
"/opt/mailwatch/mailscanner/temp/GeoLite2-Country.tar.gz" (truncated
entry) in /opt/mailwatch/mailscanner/geoip_update.php:159\nStack
trace:\n#0 /opt/mailwatch/mailscanner/geoip_update.php(159):
PharData->__construct('/opt/mailwatch/...')\n#1 {main}\n  thrown in
/opt/mailwatch/mailscanner/geoip_update.php on line 159, referer:
http://mailwatch.example.org/geoip_update.php

I see that apache2 is using php7.2 while my system is using php8.3.
Can this be the problem?

Is it possible to install manually the geoip database? I downloaded
manually the  GeoLite2-Country.tar.gz file but do not know what to do
with it...

with regards,
Paolo





On 1/24/24, Jesper Sivertsen via Mailwatch-users
<mai...@li...> wrote:
> Hi
>
> 'wget ' . $proxyString . ' -N "' . $files_base_url . $file['path'] . '" -O
> ‘
>
> The two red “
>
>
> Med venlig hilsen
> Jesper Sivertsen
>
> Tlf: 40 38 15 20
> je...@si...
> https://www.linkedin.com/in/unixkonsulent/
>
>
>
>
>
>
>
> Den 23. jan. 2024 kl. 21.08 skrev Jesper Sivertsen via Mailwatch-users
> <mai...@li...>:
>
> 'wget ' . $proxyString . ' -N "' . $files_base_url . $file['path'] . '" -O
> '
>
>
> --
> Denne meddelelse er blevet skannet for virus og farligt indhold
> af MailScanner, og er fundet ufarlig.
>
>

Hi

'wget ' . $proxyString . ' -N "' . $files_base_url . $file['path'] . '" -O ‘

The two red “


Med venlig hilsen
Jesper Sivertsen

Tlf: 40 38 15 20
je...@si...
https://www.linkedin.com/in/unixkonsulent/







Den 23. jan. 2024 kl. 21.08 skrev Jesper Sivertsen via Mailwatch-users <mai...@li...>:

'wget ' . $proxyString . ' -N "' . $files_base_url . $file['path'] . '" -O '


-- 
Denne meddelelse er blevet skannet for virus og farligt indhold
af MailScanner, og er fundet ufarlig.

Hi Jesper,
I am a newbee in programing and don't understand where are the " " in the
line:
 'wget ' . $proxyString . ' -N "' . $files_base_url . $file['path'] . '" -O
' . $file['destination'],
is it -N ' " or -N " ' ?
thank you for your patience...

On Tue, Jan 23, 2024 at 11:09 PM Jesper Sivertsen via Mailwatch-users <
mai...@li...> wrote:

> Hi
>
> If i bypass curl and use wget with a small change, then it works for me.
> You need to enclose the URL in “” since you have & inside.
>
> Her are the diff after my change on geoip_update.php
>
> [root@mail mailscanner]# diff geoip_update.php geoip_update.php.org
>
> 82,83c82
>
> <             // if (function_exists('fsockopen') ||
> extension_loaded('curl')) {
>
> <             if ( false ) {
>
> ---
>
> >             if (function_exists('fsockopen') ||
> extension_loaded('curl')) {
>
> 142c141
>
> <                     'wget ' . $proxyString . ' -N "' . $files_base_url .
> $file['path'] . '" -O ' . $file['destination'],
>
> ---
>
> >                     'wget ' . $proxyString . ' -N ' . $files_base_url .
> $file['path'] . ' -O ' . $file['destination’],
>
>
> Hope this helps others.
>
>
> I guess that curl is not able to redirect in this configuration, but wget
> are.
>
>
> Regards Jesper
>
> Den 23. jan. 2024 kl. 16.26 skrev Manuel Dalla Lana <end...@ar...>:
>
> MaxMind changed the delivery method for the database file, for reference
> see this GitHub issue: https://github.com/mailwatch/MailWatch/issues/1297
>
> Actually there is no check on the download request for redirects on the
> download logic, PR are welcome, as always.
>
>
> Manuel
>
>
> Il 23/01/24 15:31, Jesper Sivertsen via Mailwatch-users ha scritto:
>
> Hi P B
>
> It seems it is not the new URL that is the problem, but something in the
> php code.
> I am working on it, and i will let you know if i find a solution.
>
> Regards Jesper
>
>
> Den 23. jan. 2024 kl. 15.19 skrev P B <pb...@gm...>
> <pb...@gm...>:
>
> I have exactly the same issue with the same error message. The download is
> interrupted.
> Ubuntu 20.04
> mailwatch 1.2.21
>
>
> On Fri, Jan 19, 2024 at 5:21 PM David While via Mailwatch-users <
> mai...@li...> wrote:
>
>> Hi
>>
>> Works OK for me - just updated the database no problem.
>> On 19/01/2024 13:22, Jesper Sivertsen via Mailwatch-users wrote:
>>
>> Hi all
>>
>> Maxmind have changed the way you download GeoIP from start 2024, so now
>> it is not possible to import the GeoIP data into MailWatch directly.
>> Does anyone have any workaround for this ?
>> Any help is appreciated.
>>
>> I am on MailWatch 1.2.21
>>
>> I get this error:
>>
>> *Fatal error*: Uncaught UnexpectedValueException: internal corruption of
>> phar "/opt/mailwatch/mailscanner/temp/GeoLite2-Country.tar.gz" (truncated
>> entry) in /opt/mailwatch/mailscanner/geoip_update.php:158 Stack trace: #0
>> /opt/mailwatch/mailscanner/geoip_update.php(158): PharData->__construct()
>> #1 {main} thrown in */opt/mailwatch/mailscanner/geoip_update.php* on
>> line *158*
>>
>> Thanks in advance.
>>
>> Regards Jesper
>>
>>
>>
>> --
>> Denne meddelelse er blevet skannet for virus og farligt indhold
>> af *MailScanner* <http://www.mailscanner.info/>, og er fundet ufarlig.
>>
>> _______________________________________________
>> Mailwatch-users mailing lis...@li...://lists.sourceforge.net/lists/listinfo/mailwatch-users
>>
>> _______________________________________________
>> Mailwatch-users mailing list
>> Mai...@li...
>> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
>>
>
> --
> Denne meddelelse er blevet skannet for virus og farligt indhold
> af *MailScanner* <http://www.mailscanner.info/>, og er fundet ufarlig.
> _______________________________________________
> Mailwatch-users mailing list
> Mai...@li...
> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
>
>
> --
> Denne meddelelse er blevet skannet for virus og farligt indhold
> af *MailScanner* <http://www.mailscanner.info/>, og er fundet ufarlig.
>
> _______________________________________________
> Mailwatch-users mailing lis...@li...://lists.sourceforge.net/lists/listinfo/mailwatch-users
>
>
> --
> Denne meddelelse er blevet skannet for virus og farligt indhold
> af *MailScanner* <http://www.mailscanner.info/>, og er fundet ufarlig.
> _______________________________________________
> Mailwatch-users mailing list
> Mai...@li...
> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
>
>
> --
> Denne meddelelse er blevet skannet for virus og farligt indhold
> af *MailScanner* <http://www.mailscanner.info/>, og er fundet ufarlig.
> _______________________________________________
> Mailwatch-users mailing list
> Mai...@li...
> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
>

Il 23/01/24 21:08, Jesper Sivertsen via Mailwatch-users ha scritto:
> Hi
>
> If i bypass curl and use wget with a small change, then it works for me.
> You need to enclose the URL in “” since you have & inside.


On my test environment and production servers the download with curl 
extension works fine, with both old and new keys: it follows the 
Cloudflare R2 redirect just fine.


I've escaped the wget command on my last GitHub commit 
(https://github.com/mailwatch/MailWatch/commit/97aa05c0c265031a78834bd91b125bd0413b5089), 
and I was able to download the MaxMind database using both new and old 
keys: I think it's a better solution for the problem.


Manuel

What I don't understand yet is why the curl/requests library can't handle
the redirect. By default the bundled requests library follows redirects up
to 10 deep before giving up.

Adding quotes to the wget method is definitely needed and should be part of
this work to fix.

On Tue, Jan 23, 2024 at 3:09 PM Jesper Sivertsen via Mailwatch-users <
mai...@li...> wrote:

> Hi
>
> If i bypass curl and use wget with a small change, then it works for me.
> You need to enclose the URL in “” since you have & inside.
>
> Her are the diff after my change on geoip_update.php
>
> [root@mail mailscanner]# diff geoip_update.php geoip_update.php.org
>
> 82,83c82
>
> <             // if (function_exists('fsockopen') ||
> extension_loaded('curl')) {
>
> <             if ( false ) {
>
> ---
>
> >             if (function_exists('fsockopen') ||
> extension_loaded('curl')) {
>
> 142c141
>
> <                     'wget ' . $proxyString . ' -N "' . $files_base_url .
> $file['path'] . '" -O ' . $file['destination'],
>
> ---
>
> >                     'wget ' . $proxyString . ' -N ' . $files_base_url .
> $file['path'] . ' -O ' . $file['destination’],
>
>
> Hope this helps others.
>
>
> I guess that curl is not able to redirect in this configuration, but wget
> are.
>
>
> Regards Jesper
>
> Den 23. jan. 2024 kl. 16.26 skrev Manuel Dalla Lana <end...@ar...>:
>
> MaxMind changed the delivery method for the database file, for reference
> see this GitHub issue: https://github.com/mailwatch/MailWatch/issues/1297
>
> Actually there is no check on the download request for redirects on the
> download logic, PR are welcome, as always.
>
>
> Manuel
>
>
>
>
>

Hi

If i bypass curl and use wget with a small change, then it works for me.
You need to enclose the URL in “” since you have & inside.

Her are the diff after my change on geoip_update.php

[root@mail mailscanner]# diff geoip_update.php geoip_update.php.org
82,83c82
<             // if (function_exists('fsockopen') || extension_loaded('curl')) {
<             if ( false ) {
---
>             if (function_exists('fsockopen') || extension_loaded('curl')) {
142c141
<                     'wget ' . $proxyString . ' -N "' . $files_base_url . $file['path'] . '" -O ' . $file['destination'],
---
>                     'wget ' . $proxyString . ' -N ' . $files_base_url . $file['path'] . ' -O ' . $file['destination’],

Hope this helps others.

I guess that curl is not able to redirect in this configuration, but wget are.

Regards Jesper

Den 23. jan. 2024 kl. 16.26 skrev Manuel Dalla Lana <end...@ar...>:

MaxMind changed the delivery method for the database file, for reference see this GitHub issue: https://github.com/mailwatch/MailWatch/issues/1297

Actually there is no check on the download request for redirects on the download logic, PR are welcome, as always.



Manuel



Il 23/01/24 15:31, Jesper Sivertsen via Mailwatch-users ha scritto:
> Hi P B
> 
> It seems it is not the new URL that is the problem, but something in the php code.
> I am working on it, and i will let you know if i find a solution.
> 
> Regards Jesper
> 
> 
> Den 23. jan. 2024 kl. 15.19 skrev P B <pb...@gm...> <mailto:pb...@gm...>:
> 
> I have exactly the same issue with the same error message. The download is interrupted.
> Ubuntu 20.04
> mailwatch 1.2.21
> 
> 
> On Fri, Jan 19, 2024 at 5:21 PM David While via Mailwatch-users <mai...@li... <mailto:mai...@li...>> wrote:
>> Hi
>> 
>> Works OK for me - just updated the database no problem.
>> 
>> On 19/01/2024 13:22, Jesper Sivertsen via Mailwatch-users wrote:
>>> Hi all
>>> 
>>> Maxmind have changed the way you download GeoIP from start 2024, so now it is not possible to import the GeoIP data into MailWatch directly.
>>> Does anyone have any workaround for this ?
>>> Any help is appreciated.
>>> 
>>> I am on MailWatch 1.2.21
>>> 
>>> I get this error:
>>> 
>>> Fatal error: Uncaught UnexpectedValueException: internal corruption of phar "/opt/mailwatch/mailscanner/temp/GeoLite2-Country.tar.gz" (truncated entry) in /opt/mailwatch/mailscanner/geoip_update.php:158 Stack trace: #0 /opt/mailwatch/mailscanner/geoip_update.php(158): PharData->__construct() #1 {main} thrown in /opt/mailwatch/mailscanner/geoip_update.php on line 158
>>> 
>>> Thanks in advance.
>>> 
>>> Regards Jesper
>>> 
>>>  
>>> 
>>> -- 
>>> Denne meddelelse er blevet skannet for virus og farligt indhold 
>>> af MailScanner <http://www.mailscanner.info/>, og er fundet ufarlig.
>>> 
>>> 
>>> _______________________________________________
>>> Mailwatch-users mailing list
>>> Mai...@li... <mailto:Mai...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
>> _______________________________________________
>> Mailwatch-users mailing list
>> Mai...@li... <mailto:Mai...@li...>
>> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
> 
> -- 
> Denne meddelelse er blevet skannet for virus og farligt indhold 
> af MailScanner <http://www.mailscanner.info/>, og er fundet ufarlig. _______________________________________________
> Mailwatch-users mailing list
> Mai...@li... <mailto:Mai...@li...>
> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
> 
> 
> -- 
> Denne meddelelse er blevet skannet for virus og farligt indhold 
> af MailScanner <http://www.mailscanner.info/>, og er fundet ufarlig.
> 
> 
> _______________________________________________
> Mailwatch-users mailing list
> Mai...@li... <mailto:Mai...@li...>
> https://lists.sourceforge.net/lists/listinfo/mailwatch-users

-- 
Denne meddelelse er blevet skannet for virus og farligt indhold 
af MailScanner <http://www.mailscanner.info/>, og er fundet ufarlig.
_______________________________________________
Mailwatch-users mailing list
Mai...@li...
https://lists.sourceforge.net/lists/listinfo/mailwatch-users


-- 
Denne meddelelse er blevet skannet for virus og farligt indhold
af MailScanner, og er fundet ufarlig.

MaxMind changed the delivery method for the database file, for reference 
see this GitHub issue: https://github.com/mailwatch/MailWatch/issues/1297

Actually there is no check on the download request for redirects on the 
download logic, PR are welcome, as always.


Manuel


Il 23/01/24 15:31, Jesper Sivertsen via Mailwatch-users ha scritto:
> Hi P B
>
> It seems it is not the new URL that is the problem, but something in 
> the php code.
> I am working on it, and i will let you know if i find a solution.
>
> Regards Jesper
>
>
> Den 23. jan. 2024 kl. 15.19 skrev P B <pb...@gm...>:
>
> I have exactly the same issue with the same error message. The 
> download is interrupted.
> Ubuntu 20.04
> mailwatch 1.2.21
>
>
> On Fri, Jan 19, 2024 at 5:21 PM David While via Mailwatch-users 
> <mai...@li...> wrote:
>
>     Hi
>
>     Works OK for me - just updated the database no problem.
>
>     On 19/01/2024 13:22, Jesper Sivertsen via Mailwatch-users wrote:
>>     Hi all
>>
>>     Maxmind have changed the way you download GeoIP from start 2024,
>>     so now it is not possible to import the GeoIP data into MailWatch
>>     directly.
>>     Does anyone have any workaround for this ?
>>     Any help is appreciated.
>>
>>     I am on MailWatch 1.2.21
>>
>>     I get this error:
>>
>>     *Fatal error*: Uncaught UnexpectedValueException: internal
>>     corruption of phar
>>     "/opt/mailwatch/mailscanner/temp/GeoLite2-Country.tar.gz"
>>     (truncated entry) in
>>     /opt/mailwatch/mailscanner/geoip_update.php:158 Stack trace: #0
>>     /opt/mailwatch/mailscanner/geoip_update.php(158):
>>     PharData->__construct() #1 {main} thrown in
>>     */opt/mailwatch/mailscanner/geoip_update.php* on line *158*
>>
>>     Thanks in advance.
>>
>>     Regards Jesper
>>
>>
>>     -- 
>>     Denne meddelelse er blevet skannet for virus og farligt indhold
>>     af *MailScanner* <http://www.mailscanner.info/>, og er fundet
>>     ufarlig.
>>
>>
>>     _______________________________________________
>>     Mailwatch-users mailing list
>>     Mai...@li...
>>     https://lists.sourceforge.net/lists/listinfo/mailwatch-users
>     _______________________________________________
>     Mailwatch-users mailing list
>     Mai...@li...
>     https://lists.sourceforge.net/lists/listinfo/mailwatch-users
>
>
> -- 
> Denne meddelelse er blevet skannet for virus og farligt indhold
> af *MailScanner* <http://www.mailscanner.info/>, og er fundet ufarlig. 
> _______________________________________________
> Mailwatch-users mailing list
> Mai...@li...
> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
>
>
> -- 
> Denne meddelelse er blevet skannet for virus og farligt indhold
> af *MailScanner* <http://www.mailscanner.info/>, og er fundet ufarlig.
>
>
> _______________________________________________
> Mailwatch-users mailing list
> Mai...@li...
> https://lists.sourceforge.net/lists/listinfo/mailwatch-users

Hi P B

It seems it is not the new URL that is the problem, but something in the php code.
I am working on it, and i will let you know if i find a solution.

Regards Jesper


Den 23. jan. 2024 kl. 15.19 skrev P B <pb...@gm...>:

I have exactly the same issue with the same error message. The download is interrupted.
Ubuntu 20.04
mailwatch 1.2.21


On Fri, Jan 19, 2024 at 5:21 PM David While via Mailwatch-users <mai...@li... <mailto:mai...@li...>> wrote:
> Hi
> 
> Works OK for me - just updated the database no problem.
> 
> On 19/01/2024 13:22, Jesper Sivertsen via Mailwatch-users wrote:
>> Hi all
>> 
>> Maxmind have changed the way you download GeoIP from start 2024, so now it is not possible to import the GeoIP data into MailWatch directly.
>> Does anyone have any workaround for this ?
>> Any help is appreciated.
>> 
>> I am on MailWatch 1.2.21
>> 
>> I get this error:
>> 
>> Fatal error: Uncaught UnexpectedValueException: internal corruption of phar "/opt/mailwatch/mailscanner/temp/GeoLite2-Country.tar.gz" (truncated entry) in /opt/mailwatch/mailscanner/geoip_update.php:158 Stack trace: #0 /opt/mailwatch/mailscanner/geoip_update.php(158): PharData->__construct() #1 {main} thrown in /opt/mailwatch/mailscanner/geoip_update.php on line 158
>> 
>> Thanks in advance.
>> 
>> Regards Jesper
>> 
>>  
>> 
>> -- 
>> Denne meddelelse er blevet skannet for virus og farligt indhold 
>> af MailScanner <http://www.mailscanner.info/>, og er fundet ufarlig.
>> 
>> 
>> _______________________________________________
>> Mailwatch-users mailing list
>> Mai...@li... <mailto:Mai...@li...>
>> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
> _______________________________________________
> Mailwatch-users mailing list
> Mai...@li... <mailto:Mai...@li...>
> https://lists.sourceforge.net/lists/listinfo/mailwatch-users

-- 
Denne meddelelse er blevet skannet for virus og farligt indhold 
af MailScanner <http://www.mailscanner.info/>, og er fundet ufarlig. _______________________________________________
Mailwatch-users mailing list
Mai...@li...
https://lists.sourceforge.net/lists/listinfo/mailwatch-users


-- 
Denne meddelelse er blevet skannet for virus og farligt indhold
af MailScanner, og er fundet ufarlig.

I have exactly the same issue with the same error message. The download is
interrupted.
Ubuntu 20.04
mailwatch 1.2.21


On Fri, Jan 19, 2024 at 5:21 PM David While via Mailwatch-users <
mai...@li...> wrote:

> Hi
>
> Works OK for me - just updated the database no problem.
> On 19/01/2024 13:22, Jesper Sivertsen via Mailwatch-users wrote:
>
> Hi all
>
> Maxmind have changed the way you download GeoIP from start 2024, so now it
> is not possible to import the GeoIP data into MailWatch directly.
> Does anyone have any workaround for this ?
> Any help is appreciated.
>
> I am on MailWatch 1.2.21
>
> I get this error:
>
> *Fatal error*: Uncaught UnexpectedValueException: internal corruption of
> phar "/opt/mailwatch/mailscanner/temp/GeoLite2-Country.tar.gz" (truncated
> entry) in /opt/mailwatch/mailscanner/geoip_update.php:158 Stack trace: #0
> /opt/mailwatch/mailscanner/geoip_update.php(158): PharData->__construct()
> #1 {main} thrown in */opt/mailwatch/mailscanner/geoip_update.php* on line
> *158*
>
> Thanks in advance.
>
> Regards Jesper
>
>
>
> --
> Denne meddelelse er blevet skannet for virus og farligt indhold
> af *MailScanner* <http://www.mailscanner.info/>, og er fundet ufarlig.
>
> _______________________________________________
> Mailwatch-users mailing lis...@li...://lists.sourceforge.net/lists/listinfo/mailwatch-users
>
> _______________________________________________
> Mailwatch-users mailing list
> Mai...@li...
> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
>

I have checked. It looks correct:
drwxr-x---  2 postfix        mtagroup 28672 gen 22 11:31 hold
drwxr-x---  2 postfix        mtagroup 24576 gen 22 11:31 incoming


On 1/22/24, Simon Wood via Mailwatch-users
<mai...@li...> wrote:
> I've seen that before. Check the permissions on the postfix queues
> /var/spool/postfix/*
>
> Regards
>
> Simon Wood
>
> -----Original Message-----
> From: P B <pb...@gm...>
> Sent: 22 January 2024 07:53
> To: mai...@li...
> Subject: [Mailwatch-users] Problems after updating
>
> I have a problem after upgrading from ubuntu 18.04 to 20.04.
> Also mailscanner updated.
> I updated manually from mailwatch from 1.2.16 to 1.2.21 I can login to my
> mailwatch site but I only see very little information, no information about
> my emails... (see attachment).
> I went through the installing guide of Mailwatch many times but without
> result.
> How can I get support?
> My best greetings,
> Thank you
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
>
> ________________________
> This email was scanned by Bitdefender
>
> _______________________________________________
> Mailwatch-users mailing list
> Mai...@li...
> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
>

I've seen that before. Check the permissions on the postfix queues /var/spool/postfix/*

Regards

Simon Wood

-----Original Message-----
From: P B <pb...@gm...> 
Sent: 22 January 2024 07:53
To: mai...@li...
Subject: [Mailwatch-users] Problems after updating

I have a problem after upgrading from ubuntu 18.04 to 20.04.
Also mailscanner updated.
I updated manually from mailwatch from 1.2.16 to 1.2.21 I can login to my mailwatch site but I only see very little information, no information about my emails... (see attachment).
I went through the installing guide of Mailwatch many times but without result.
How can I get support?
My best greetings,
Thank you

--
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.


________________________
This email was scanned by Bitdefender

I have a problem after upgrading from ubuntu 18.04 to 20.04.
Also mailscanner updated.
I updated manually from mailwatch from 1.2.16 to 1.2.21
I can login to my mailwatch site but I only see very little
information, no information about my emails... (see attachment).
I went through the installing guide of Mailwatch many times but without result.
How can I get support?
My best greetings,
Thank you

Hi

Works OK for me - just updated the database no problem.

On 19/01/2024 13:22, Jesper Sivertsen via Mailwatch-users wrote:
> Hi all
>
> Maxmind have changed the way you download GeoIP from start 2024, so 
> now it is not possible to import the GeoIP data into MailWatch directly.
> Does anyone have any workaround for this ?
> Any help is appreciated.
>
> I am on MailWatch 1.2.21
>
> I get this error:
>
> *Fatal error*: Uncaught UnexpectedValueException: internal corruption 
> of phar "/opt/mailwatch/mailscanner/temp/GeoLite2-Country.tar.gz" 
> (truncated entry) in /opt/mailwatch/mailscanner/geoip_update.php:158 
> Stack trace: #0 /opt/mailwatch/mailscanner/geoip_update.php(158): 
> PharData->__construct() #1 {main} thrown in 
> */opt/mailwatch/mailscanner/geoip_update.php* on line *158*
>
> Thanks in advance.
>
> Regards Jesper
>
>
> -- 
> Denne meddelelse er blevet skannet for virus og farligt indhold
> af *MailScanner* <http://www.mailscanner.info/>, og er fundet ufarlig.
>
>
> _______________________________________________
> Mailwatch-users mailing list
> Mai...@li...
> https://lists.sourceforge.net/lists/listinfo/mailwatch-users

Hi all

Maxmind have changed the way you download GeoIP from start 2024, so now it is not possible to import the GeoIP data into MailWatch directly.
Does anyone have any workaround for this ?
Any help is appreciated.

I am on MailWatch 1.2.21

I get this error:

Fatal error: Uncaught UnexpectedValueException: internal corruption of phar "/opt/mailwatch/mailscanner/temp/GeoLite2-Country.tar.gz" (truncated entry) in /opt/mailwatch/mailscanner/geoip_update.php:158 Stack trace: #0 /opt/mailwatch/mailscanner/geoip_update.php(158): PharData->__construct() #1 {main} thrown in /opt/mailwatch/mailscanner/geoip_update.php on line 158

Thanks in advance.

Regards Jesper

 
-- 
Denne meddelelse er blevet skannet for virus og farligt indhold
af MailScanner, og er fundet ufarlig.

MailWatch Version: 1.2.18

 

[php7:notice] [pid 278688] [client 172.16.50.2:54289] Could not find regex
for virus scanner avastd, referer:
https://mail.UNDISCLOSED.com/mailscanner/status.php

 

I'm not seeing anything in the release notes for the updates where this has
been addressed.

 

Any change of getting that regex updated for AvastD ???

 

Thanks,

Tracy

 

For your coments normally this indicate that something is wrong with SQL Connection 

 

Best Regards

Jorge A. Arenas Quezada

 

From: PenguinWhispererThe <th3...@gm...> 
Sent: viernes, 18 de agosto de 2023 05:43 a. m.
To: mai...@li...
Subject: [Mailwatch-users] Enabling SQLWhitelist SQLBlackList: MailScanner: Message attempted to kill MailScanner

 

Hi

 

I had just enabled the SQLWhiteList and SQLBlackList in the Mailscanner configuration.

Right now it seems it just keeps on "processing" the same items.

 

The only useful info I get is :


MailScanner: Message attempted to kill MailScanner

	

 

The messages are not removed from the queue.

 

Once reverted the messages are handled properly again.

 

I don't see high CPU usage so it might be some kind of timeout?

 

Another question: is it possible to use wildcards in those lists? (Mailscanner 5.3.4.3)

 

Thanks in advance.

Hi

I had just enabled the SQLWhiteList and SQLBlackList in the Mailscanner
configuration.
Right now it seems it just keeps on "processing" the same items.

The only useful info I get is :
MailScanner: Message attempted to kill MailScanner

The messages are not removed from the queue.

Once reverted the messages are handled properly again.

I don't see high CPU usage so it might be some kind of timeout?

Another question: is it possible to use wildcards in those lists?
(Mailscanner 5.3.4.3)

Thanks in advance.

I just did that change and it seems to work !
Thank you very much, that seems to have fixed my issue !

On 11/03/2023 16:36, Shawn Iverson wrote:
> Well, maybe not, I looked at your error and compared to mine, not the 
> same, but worth a try anyway.
>
> On Sat, Mar 11, 2023 at 10:35 AM Shawn Iverson 
> <sha...@gm...> wrote:
>
>     I think this is your issue
>     https://github.com/mailwatch/MailWatch/issues/1275
>
>     The formatting for the delay must have changed in sendmail in
>     recent versions.  Going to need to code a fix, but to fix it now
>     in your instance...
>
>     On line ~124 in mtalogprocessor.inc.php in your mailwatch web
>     directory remove SEC_TO_TIME around the '$_delay' variable so that
>     it looks like this:
>     dbquery(
>                     "REPLACE INTO mtalog
>     (`timestamp`,`host`,`type`,`msg_id`,`relay`,`dsn`,`status`,`delay`,`to_address`)
>     VALUES
>
>     (FROM_UNIXTIME('$_timestamp'),'$_host','$_type','$_msg_id','$_relay','$_dsn','$_status','$_delay',
>     '$_to')"
>

-- 
(°-	Bernard Lheureux
//\     Linux System Administrator
v_/_MailTo:be...@lh...

Well, maybe not, I looked at your error and compared to mine, not the same,
but worth a try anyway.

On Sat, Mar 11, 2023 at 10:35 AM Shawn Iverson <sha...@gm...>
wrote:

> I think this is your issue
> https://github.com/mailwatch/MailWatch/issues/1275
>
> The formatting for the delay must have changed in sendmail in recent
> versions.  Going to need to code a fix, but to fix it now in your
> instance...
>
> On line ~124 in mtalogprocessor.inc.php in your mailwatch web directory
> remove SEC_TO_TIME around the '$_delay' variable so that it looks like this:
> dbquery(
>                 "REPLACE INTO mtalog
> (`timestamp`,`host`,`type`,`msg_id`,`relay`,`dsn`,`status`,`delay`,`to_address`)
> VALUES
> (FROM_UNIXTIME('$_timestamp'),'$_host','$_type','$_msg_id','$_relay','$_dsn','$_status','$_delay',
> '$_to')"
>
> On Sat, Mar 11, 2023 at 8:31 AM Bernard Lheureux via Mailwatch-users <
> mai...@li...> wrote:
>
>> Mar 11 14:17:18 bluewall systemd: Started Sendmail relay service for
>> MailWatch.
>> Mar 11 14:17:18 bluewall php: PHP Notice:  Undefined index: status in
>> /usr/local/bin/mailwatch_sendmail_relay.php on line 78
>> Mar 11 14:17:18 bluewall php: Notice: Undefined index: status in
>> /usr/local/bin/mailwatch_sendmail_relay.php on line 78
>> Mar 11 14:17:18 bluewall php: PHP Fatal error:  Uncaught
>> mysqli_sql_exception: Truncated incorrect DECIMAL value: '' in
>> /var/www/html/mailscanner/functions.php:1052
>> Mar 11 14:17:18 bluewall php: Fatal error: Uncaught
>> mysqli_sql_exception: Truncated incorrect DECIMAL value: '' in
>> /var/www/html/mailscanner/functions.php:1052
>> Mar 11 14:17:18 bluewall php: Stack trace:
>> Mar 11 14:17:18 bluewall php: #0
>> /var/www/html/mailscanner/functions.php(1052): mysqli->query()
>> Mar 11 14:17:18 bluewall php: #1
>> /var/www/html/mailscanner/mtalogprocessor.inc.php(137): dbquery()
>> Mar 11 14:17:18 bluewall php: #2
>> /var/www/html/mailscanner/mtalogprocessor.inc.php(181):
>> MtaLogProcessor->processLine()
>> Mar 11 14:17:18 bluewall php: #3
>> /usr/local/bin/mailwatch_sendmail_relay.php(112): MtaLogProcessor->doit()
>> Mar 11 14:17:18 bluewall php: #4 {main}
>> Mar 11 14:17:18 bluewall php: thrown in
>> /var/www/html/mailscanner/functions.php on line 1052
>> Mar 11 14:17:18 bluewall php: Stack trace:
>> Mar 11 14:17:18 bluewall php: cat: write error: Broken pipe
>> Mar 11 14:17:18 bluewall php: #0
>> /var/www/html/mailscanner/functions.php(1052): mysqli->query()
>> Mar 11 14:17:18 bluewall php: #1
>> /var/www/html/mailscanner/mtalogprocessor.inc.php(137): dbquery()
>> Mar 11 14:17:18 bluewall php: #2
>> /var/www/html/mailscanner/mtalogprocessor.inc.php(181):
>> MtaLogProcessor->processLine()
>> Mar 11 14:17:18 bluewall php: #3
>> /usr/local/bin/mailwatch_sendmail_relay.php(112): MtaLogProcessor->doit()
>> Mar 11 14:17:18 bluewall php: #4 {main}
>> Mar 11 14:17:18 bluewall php:  thrown in
>> /var/www/html/mailscanner/functions.php on line 1052
>> Mar 11 14:17:18 bluewall systemd: mailwatch-sendmail-relay.service: main
>> process exited, code=exited, status=255/n/a
>> Mar 11 14:17:18 bluewall systemd: Unit mailwatch-sendmail-relay.service
>> entered failed state.
>> Mar 11 14:17:18 bluewall systemd: mailwatch-sendmail-relay.service failed.
>> Mar 11 14:17:18 bluewall systemd: mailwatch-sendmail-relay.service
>> holdoff time over, scheduling restart.
>> Mar 11 14:17:18 bluewall systemd: Stopped Sendmail relay service for
>> MailWatch.
>> Mar 11 14:17:18 bluewall systemd: start request repeated too quickly for
>> mailwatch-sendmail-relay.service
>> Mar 11 14:17:18 bluewall systemd: Failed to start Sendmail relay service
>> for MailWatch.
>> Mar 11 14:17:18 bluewall systemd: Unit mailwatch-sendmail-relay.service
>> entered failed state.
>> Mar 11 14:17:18 bluewall systemd: mailwatch-sendmail-relay.service failed.
>>
>> I tried everything I could, but it refuses to work anyway...
>> Seems to be MySQL related
>> CentOS Linux release 7.9.2009 (Core)
>> MailWatch Version: 1.2.19
>> Sendmail Version: 8.14.7
>> MailScanner Version: 5.4.5
>> ClamAV Version: 1.0.1
>> SpamAssassin Version: 3.4.0
>> PHP Version: 7.4.33
>> MySQL Version: 5.7.41-log
>>
>> What could be wrong ?
>>
>> --
>> (°-     Bernard Lheureux
>> //\     Linux System Administrator
>> v_/_    MailTo:be...@lh...
>>
>>
>>
>> _______________________________________________
>> Mailwatch-users mailing list
>> Mai...@li...
>> https://lists.sourceforge.net/lists/listinfo/mailwatch-users
>>
>