Search results

I got it working on pmg 8 using this: --- pmg-smtp-filter.orig.8.0 2023-06-30 05:30:48.958121687 -0400 +++ pmg-smtp-filter 2023-07-06 03:00:52.579596405 -0400 @@ -23,6 +23,7 @@ use PVE::SafeSyslog; use PVE::ProcFSTools; use PVE::INotify; +use PVE::Tools; use Mail::SpamAssassin...

If you had four power outages within five weeks, I would say UPS is what you definitely need. There are drives that have power loss data protection, like these Intel drives but those are expensive enterprise drives. So UPS is a much cheaper solution.

I've ran into this issue as well with latest PVE on both LXC and VM's with latest Debian and 10.8.3-MariaDB. Is the only workaround to switch to stop mode backup or switch to centos for VMs?

I've tried downgrading the host kernel to 5.13, hoping it was the same issue as kernel-bug-cpu-soft-lockup. But it still just happened. So it's not the kernel.

This also happens to me with a Debian VM with 64GB ram and 512GB disk on zfs storage. It doesn't happen on another Debian VM that is 32GB ram and 256GB disk. Host is Epyc AMD EPYC 7443P 24-Core Processor, 512GB ram, 8x Intel SSD DC S4610 drives with a Intel DC P4800X Log device setup as raid10...

Yes, it's a bug in FreeBSD 13 RELEASE including the latest patch. It has only been fixed in STABLE. Not sure when it will make it to RELEASE, maybe with the next version 13.1. So the options are to either turn off journaling or upgrade to STABLE kernel for now...

Hello, Since upgrading from 6.4 to 7.1 we have experienced many issues with FreeBSD vm's. Please keep in mind that we had no issues on 6.4. For example our dovecot FreeBSD 13 (latest patch release) server during busier times would start to deinit dovecot processes, and the load average jumps...

The domain wide blocklist works, but spammers don't always use real From, you need to look at Received-SPF mfrom for the real from. And block that domain. Example Spam: Received-SPF: pass (bitcoin-trading.biz: 95.217.217.211 is authorized to use 'admin@bitcoin-trading.biz' in 'mfrom' identity...

There were number of warnings, but the times didn't exactly match the times of the queue error: grep "queue fi" /var/log/mail.log |grep "Sep 24 07:34" Sep 24 07:34:01 franklin-pmg1 postfix/smtpd[26758]: proxy-reject: END-OF-MESSAGE: 451 4.3.0 Error: queue file write error...

Switching from Redis Bayes and AWL to the default file based store did stop the "451 4.3.0 Error: queue file write error" errors so far. You're right, it's not needed to be installed through cpan, though if you try it, it will say it's already installed. With the default settings, is the file...

No errors from Redis. For Bayes: bayes_store_module Mail::SpamAssassin::BayesStore::Redis bayes_sql_dsn server=127.0.0.1:6379;database=0 use_bayes_rules 1 bayes_auto_learn 1 bayes_learn_to_journal 0 bayes_auto_expire 1 bayes_token_ttl 30d bayes_seen_ttl 14d For AWL...

pmgversion -v proxmox-mailgateway-container: 6.2-1 (API: 6.2-5/05a7829e, running kernel: 5.4.55-1-pve) pmg-api: 6.2-5 pmg-gui: 2.2-2 clamav-daemon: 0.102.4+dfsg-0+deb10u1 libarchive-perl: 3.3.3-1 libjs-extjs: 6.0.1-10 libjs-framework7: 4.4.7-1 libpve-apiclient-perl: 3.0-3 libpve-common-perl...

There are no errors starting pmg-smtp-filter and it is running: ps -ef |grep pmg-smtp-filter root 16109 1 0 05:59 ? 00:00:05 /usr/bin/perl /usr/bin/pmg-smtp-filter root 16145 16109 0 05:59 ? 00:00:01 pmg-smtp-filter child root 16146 16109 0 05:59 ...

Hello, I keep getting a large number of "451 4.3.0 Error: queue file write error" in logs and also mail notification about it. I've received over 700 of them for just past day, this is for about 30,000 total emails received for the day. It always happens with a reject/timeout to proxy: Sep...

Thank you Stoiko, this works well.

How do you do a domain wide blacklist? Not global, but just domain wide. I've tried using "User Blacklist" and used *@domain1.com and added *@baddomain.com, but emails from baddomain.com still arrive to domain1.com accounts.

I've figured it's something easy like deleting few keys (like on PBS.) Cause I did make some modifications (Redis bayes.) But I guess I could recreate those changes.

Hello, I've cloned a well running PMG, and wanted the clone to get a new Server ID. As currently, it has the same one as the one cloned from. Is this possible?

Yes that was the culprit! mx.domain1.com was indeed removing the header. Thank you for your help.

Thank you for the response, however, I added a second domain and for the second domain the header is modified even if the score is 0: X-SPAM-LEVEL: Spam detection results: 0 DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID...