Search results

Ok, thank you for asking the right questions... error resolved! :) This is the only VM on this host, which is connected to the DMZ interface (vmbr1). And it looks that with the update of the host from buster to bullseye the hardware ID of the network interface changed. (from ens3 to enp179s0)...

Here is the config of the container: root@pve1:~# pct config 115 arch: amd64 cores: 2 features: nesting=1 hostname: pmg memory: 4096 nameserver: 192.168.2.4 net0: name=eth0,bridge=vmbr1,gw=192.168.2.4,hwaddr=CA:78:42:E1:E0:9D,ip=192.168.2.5/24,type=veth onboot: 0 ostype: debian rootfs...

I invstigated the journal, the only suspicious entry I found is on line 23? Is this correct? Aug 16 08:15:29 pmg mv[63]: /bin/mv: cannot stat '/etc/network/interfaces.new': No such file or directory Do you see any error here?? Thank you for help. Ingo Please find the journal here: Aug 16...

No, ping of the gateway does not work. :-( I also tried to enable nesting and restarted the container but the network does not still not work... Any other idea, what I can try? I also wanted to install a fresh PMG 7.0 as a container for testing, but I can not find it in the repository. Is it...

Hi! I just did the update from Proxmox 6.4 to 7.0. Everything worked fine, Proxmox 7.0 and all my VMs is running. Except the LXC container of PMG 6.4: I do not have any network connection! I have another LXC container (Dokuwiki) which is also running fine after the update, nor problems at all...

We have an external web shop running, which sends orders to us, with the order person as sender. Of course our shop is not a designated mailserver for all these domains. However I set the IP address of this shop on the Global Whitelist in the Rules section. But it simply does not work. Any idea...

Ok, the new rule works and the spammer is still active. Once again, here are 2 examples. First one delivered: Return-Path: <judithzpewawjwiesinger@isikradyo.com> Received-SPF: pass (isikradyo.com: 63.81.90.130 is authorized to use 'judithzpewawjwiesinger@isikradyo.com' in 'mfrom' identity...

Until now, my rules were all on Factory Defaults. However I just setup a new rule with prio 99 "Modify Spam Level". See attached screenshot. Ok like this?

This was copied from the source of the mail recipient. As there is also a SpamAssassin running on the Mail-Server (Zimbra) itself... could it be, that the second SpamAssassin deletes the entries of the first one? Here is the rest of the header: Return-Path: <carstenbpehknt@isikradyo.com>...

Here is the raw content of the quarantined mail. Delivered-To: ddd@xxx.de Return-Path: karintfxnayfkries@isikradyo.com Received-SPF: pass (isikradyo.com: 63.81.90.114 is authorized to use 'karintfxnayfkries@isikradyo.com' in 'mfrom' identity (mechanism 'ip4:63.81.90.0/24' matched))...

While analyzing through coming spam, I just realized that there are mails coming from one domain, that has different SPAM results in PMG, although it has almost the same content. Any idea how to tune this in PMG settings? What can I do, that mail 1 and mail 3 also gets 3 points in SpamAssassin...

This is a little strange, when doing a "dig +short -x 190.210.44.145" on the CLI of PMG I get the same result. So DNS looks quite ok. However, when I ask for the IP with dig "mail.osssb.com.ar" it resolves to a different IP: 190.210.44.147 Maybe this is the reason, why PMG reject the connection?

Normally I wouldn't care, but when looking at the Tracking Center in PMG I only see "rejected messages" from this host and the message "aborted by limit (too many hits)". I thought PMG would have a function to block those over-active spammers!

No, it's not any IP that I know... and also the domain does not belong to me!

Thank you for your thoughts and the link to your posting. I read it very precisely. However, today I have 2 mail-servers bugging our mail-gateway all the time, PMG always rejects their mails, but they continue to try over and over... any idea how to stop this? (besides putting the ip addresses...

I don't really have a strategy on my own, I am just using the default rules, that PMG provides. I enabled DNSBL with these lists: zen.spamhaus.org,psbl.surriel.com,b.barracudacentral.org Where do I define postscreen settings? What mail filter rules would your recommend?

Hi Stoiko! Thanks for your reply. I enabled "Reject Unknown Clients" as you recommended. Of course I read the Getting Started page right after setup and added three DNSBLs. But here I can not find any other hint at all for improving Spam Detection?! Yes, I also read section 4.8.3, but I don't...

So, I did the update some days ago, evertyhing went fine! :)

Hi! I am using PMG for around 4 weeks now. After setup the recognition of spam was really good! But now, after running it for a while, I have more and more spam coming through... What can I do to improve the recognition of spam?? Is there any Howto available? During the last week from Monday...

Hi! We are running 2 Proxmox servers since December 2020. This is my first .x update now. Is it safe to simpy update the production environment via the WebGUI while VMs are running? Regards, Ingo