Search results

Make sure your script has the two lines, first runs local, second runs remote

After the changes I described on that post, segmentation fault stopped Tracking Center not in sync

I woke up with a better solution. Instead of copying logs from one server to another, messing up the files, I created my "own" pmg-log-tracker. First you need to rename /usr/bin/pmg-log-tracker to something else, example pmg-log-tracker-default, on server Master and Node. Then create...

You can also use smtp_fallback_relay postfix parameter. For example, if 1 is down, it will send to 2; 2 down, send to 3. relay_transport = smtp:[10.10.10.1]:25 smtp_fallback_relay = [10.10.10.2]:25, [10.10.10.3]:25

I found another thread with exactly same problem https://forum.proxmox.com/threads/pmg-log-tracker-segfault-error.42735/

I have exactly same problem. Did you solve it?

Right, but user will only known that the message was moved to quarantine and had the option to release on the next day by the spam report.

Sorry, Tom. I did not understand what you mean about test case.

Right, Tom. What do you need?

Memory is fine, 18% of 16 GB. Logs also. Yeah, it actually works, however, with plenty of logs/messages, it crashes.

Greetings, Imagine that user@gmail.com sends a message to 20 users. Message gets high SA score and is moved to spam quarantine. You are the admin and needs to release it. First, you need to track the message, write down all the receivers, go to spam quarantine and use that drop down E-mail...

Hello Tom. # pmgversion -v proxmox-mailgateway: 5.0-9 (API: 5.0-71/a0907ff5, running kernel: 4.13.16-3-pve) pmg-api: 5.0-71 pmg-gui: 1.0-38 proxmox-spamassassin: 3.4.1-55 proxmox-widget-toolkit: 1.0-18 pve-kernel-4.13.16-3-pve: 4.13.16-49 pve-kernel-4.13: 5.1-45 pve-kernel-4.13.13-5-pve...

Greetings, When using Tracking Center for 48 hours back search, I got the error below. command '/usr/bin/pmg-log-tracker -v -l 2000 -s 1531105200 -e 1531278000 -n -g -f gmail.com' failed: got signal 11 (500) Running the same command at linux, I got several results, however, at the end...

Really nice job @heutger I will wait for @proxmox team to implement all your optimizations and release it on the next version :D

So, no bounce, OK. Is there a way to put some custom log entry? For example, put LDAP reject with mail filter action and be able to search on tracking center using filter.

Did you restart the server?

Yes

@dietmar The receiving mail server is a second layer that does not have the valid recipients addresses. Also, that is why I am not using verify receiver option.

Greetings, I am using Who Objects with LDAP Group - Unknown LDAP address to reject invalid recipients. Today I am using the block action, but better option would be bounce the message, as default MTA behavior. Is there a way to create a bounce action? Thank you

@heutger thanks for sharing. I started using your first tier list today.