timeout, email is not filteret

[linhu]

Hi, is there a timeout in the filter for email filtering, some of the mails are not filtered and send directly to the host.
I can see this in the email sourcecode when the email goes through the filter.
So the question is how to chnage the config/timeout when the pmg is bussy.
when we have a large email indbound the server is very bussy, and the issue is the mails are send forward to the host without filtering

 

[Stoiko Ivanov]

Hi, is there a timeout in the filter for email filtering, some of the mails are not filtered and send directly to the host.
I can see this in the email sourcecode when the email goes through the filter.
So the question is how to chnage the config/timeout when the pmg is bussy.
when we have a large email indbound the server is very bussy, and the issue is the mails are send forward to the host without filtering

That should not be the case - please provide the logs of such a situation - mails are always processed by the smtp-filter in the default configuration

 

[linhu]

ok i found this:
2024-01-24T00:12:08.361324+01:00 mailsec pmg-smtp-filter[102745]: WARNING: razor2: razor2 check failed: Operation already in progress razor2: razor2 had unknown error during get_server_info at /usr/share/perl5/Mail/SpamAssassin/Plugin/Razor2.pm line 207. at /usr/share/perl5/Mail/SpamAssassin/Plugin/Razor2.pm line 350.

we can not send the logfile there are many emails from the customers in the log.
I will read the log and send the errors and issues here

 

[Stoiko Ivanov]

disable the razor plugin (GUI->Configuration->Spam Detector->Options) - and if this helps - read the reference documentation on the necessary firewall-settings for PMG...
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#firewall_settings

 

[linhu]

Jan 25 11:07:19 mailsec pmgconfig[1075]: Use of uninitialized value $domain in concatenation (.) or string at /usr/share/perl5/PMG/Utils.pm line 677.
Jan 25 11:07:21 mailsec pmgconfig[1076]: Use of uninitialized value $domain in concatenation (.) or string at /usr/share/perl5/PMG/Utils.pm line 677.
Jan 25 11:07:25 mailsec pmgconfig[1076]: reloading pmg-smtp-filter: can't open '/run/pmg-smtp-filter.cfg' - No such file or directory

 

[Stoiko Ivanov]

Use of uninitialized value $domain in concatenation (.) or string at /usr/share/perl5/PMG/Utils.pm line 677.

I guess you don't have set your domain name as first entry of the searchdomains in /etc/resolv.conf - see :
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#_configuration_files_overview

 

[linhu]

ok thanks for the info we have added the razor port to the firewall config and added the host domain to the search config.

 

[linhu]

Jan 31 09:02:32 mailsec pmg-smtp-filter[49255]: WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE @163.com$/ at /usr/share/perl5/PMG/RuleDB/WhoRegex.pm line 103.
Jan 31 09:02:32 mailsec pmg-smtp-filter[49255]: WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE leat.or.tz$/ at /usr/share/perl5/PMG/RuleDB/WhoRegex.pm line 103.
Jan 31 09:02:32 mailsec pmg-smtp-filter[49255]: WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE @tiscali.it$/ at /usr/share/perl5/PMG/RuleDB/WhoRegex.pm line 103.

and the emails from this hosts are not blocked

 

[Stoiko Ivanov]

Jan 31 09:02:32 mailsec pmg-smtp-filter[49255]: WARNING: ^* matches null string many times in regex; marked by <-- HERE in m/^* <-- HERE @163.com$/ at /usr/share/perl5/PMG/RuleDB/WhoRegex.pm line 103.

This question comes up quite a few times in the forum - check the forum search
put shortly - your regex is wrong - a wildcard in regex is '.*' not '*'
...

 

[linhu]

ahhh ok yes sure its corect, omg, thanks haha

 

[linhu]

but is the user blacklist also with regex? when yes the description is not correct

 

[Stoiko Ivanov]

but is the user blacklist also with regex? when yes the description is not correct

yes - the user-lists are globs - the rationale behind this is that they are edited by users, who might not be familiar with regular expressions (while admins are quite often)