It turns out that simply using the literal string <1@example.com> matches... ie. including the <> brackets within the value section... and inbound mail to that specific address gets blocked.
While it works, I don't understand why I'm able to block any number of other recipient addresses with...
Just to clarify, using '.*1@domain.com.*' and testing with '1@domain.com' did yield a match. The problem is that it also matched 'xxx1@example.com' ... whereas I need it to match the exact string '1@domain.com' and nothing else.
pmgversion -v reports the following...
proxmox-mailgateway...
I use the received headers because many spam To: address is an alias or group distribution list of some sort. The received headers reveal the actual user the mail was intended for. I use the received header check for all others and it works fine, likely because they are more unique...
Did you find a solution? I'm having a similar problem and cannot get it to work.
I'm trying to block the exact recipient address "1@mydomain.com". I have a blacklist set up as a What Object (Match Field received=) and it works for all others that I block, but this one unfortunately allws mail...
Ugh... found it. Apparently some genius thought it would be a good idea to use systemd sshd.socket instead of the standard sshd.service mechanism when they built the "LXC default image for Centos 7 (20190926)"
The solution is:
systemctl disable sshd.socket
systemctl stop sshd.socket
systemctl...
Now I've changed the listen port in sshd_config as well as the ssh entry in /etc/services, and still upon boot, the LXC's init is listening on port 22.
netstat only shows it listening on tcp6 but I can connect to it via tcp4.
This makes no sense. Anyone able to help? Thank you
I removed /usr/sbin/sshd and rebooted. This time, I am unable to login via ssh -- ie. no magical listeners appear. But, netstat still shows init has port 22 bound:
# netstat -tulpn|grep :22
tcp6 0 0 :::22 :::* LISTEN 1/init
What's even...
By "init-based sshd", this is what I mean:
# netstat -tulpn|grep :22
tcp6 0 0 :::22 :::* LISTEN 1/init
# ps -ef|grep sshd
#
Note how init has port 22 bound, but there is no sshd listener.
Where as a normal sshd listener looks like this:
#...
Hi All,
How does ssh into an LXC container work?
I have a Centos 7.9 LXC container that I can ssh into, but I can't figure out what sshd is listening. systemctl start sshd fails with the complaint that it can't bind to port 22, and status shows it's disabled and dead. A third-party sshd also...
Hi All,
I have several Win10 guests and even though the all show idle (~2%) cpu utilization, the proxmox host is showing 15-20% for the kvm process running these machines.
I do not see this problem with Win7 or Win2012 hosts.
I've tried to find answers, and this seems to be a pretty common...
Hi All,
I'm confused on how to create a full clone...
Does GUI-->Rt. Click VM --> Clone create a full clone or a linked clone?
The pop-up has no options to specify what kind of clone to create, it just seems to do what it does without asking, but when I compare the disk images from the...
Hi All,
How can I get valid interface details from a paravirtualized interface within a VM? ethtool doesn't show anything useful with the para driver...
ethtool ens19
Settings for ens19:
Supported ports: [ ]
Supported link modes: Not reported
Supported...
I think I've stumbled across a problem with proxmox on this one. Looking at ifconfig ouput, I just happened to notice the MTU size for the interface was different than that of the bridge (1500 vs 15000) ... even though the definition in /etc/network/interfaces stated otherwise.
In the proxmox...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.