Search results

This definitely helps for whitelisting, but for blacklisting the use case is usually to blacklist emails/senders that slipped through spam filters. In other words, if you find spam in your Inbox, you can forward to blacklist@domain.com and it will get added to the user blacklist.

That was actually very helpful info, thanks a lot. Seems the network to which our new IP belongs to was indeed on UCEPROTECTL2. Moving the gateway to another completely unlisted IP now shows successful direct delivery (without smarthost) also to outlook.com. I still wish there would be better...

Thanks for your feedback. I tried to work with transports yesterday after posting the second example, but I didn't get it to work. It does indeed seem PMG only uses it for inbound mail. I also noticed the manual describes /etc/pmg/transports but then in main.cf we have transport_maps =...

We've been using PMG for a couple of weeks but today I saw our IP address seems to be on a Microsoft blocklist - ignore this part, how to get unblocked is not the reason why I am posting. Rather, I'd like to see how to get PMG to work with selective smarthosts or possibly some other suggestions...

I assume this has not been implemented after all?

Apologies, misunderstood your question, I thought you wanted a second email. If I understand this correct you could add the following command to your crontab at 06:00. /usr/bin/pmgqm send --timespan yesterday

The default Debian AMI I tested in AWS seems to come without swap space configured. If proper swap is assigned PMG also starts properly on t2.small with 2GiB of memory only and another 2GiB of swap. As far as I can tell, swap is required by clamd to properly start on t2small with only 2GiB.

Hmm, the same happens when I install a 1 CPU 2GB container with the official PMG template (7.0.8) on a local PVE7 server. clamd hangs on start and memory far exceeds the 2GB from the 'minimum requirements' page. When I increased swap from 512MB to 2048MB it recovered. And installing in a 1CPU...

I am currently evaluating PMG to replace a AWS EC2 based Windows 2019 mail server (MDaemon) running in a single AWS EC2 t2.small instance (1 vCPU 2GB RAM). Today I installed PMG on a t2.small on top of the stock Debian 11 AMI and it would become unresponsive when clamd starts up. Changing the...

Turns out EC2 instance type t2.small (1 vCPU, 2GB) are too small, unresponsiveness was caused by clamd starting up and never recovering. Changing to instance type t2.medium (2 vCPU, 4GB RAM) or t2.large (8GB) solved the problem. So, after all this back and forth it seems it works just fine...

OK, so I went ahead and wanted to try that myself with the above mentioned strategies using NetworkManager and both ifupdown 3.0.0/Debian and also another one with 3.1.0/Proxmox. Virgin t2.small instance with the stock Debian 11 API. Both survived reboots, despite a few error messages from...

Why not take a snapshot of your EC2 instance and then try to update. This would answer your question and help me decide if I should follow your footsteps or not ;)