Search results

Oh, I missed that. I created a second rule to catch the header. Thanks!

Hello, I created a filter rule that block email if *@ourdomain.tld is found in the from field: Rule name: blacklist Action Object: Quarantine From: blacklist Who object name: blacklist Regular expression: .*@.*\.domain\.tld Regular expression: .*@domain\.tld This worked great when I tested...

One more thing, the regexp doesn't match when the subject field is missing. How could I mark my message as external if the subject field is missing? If I don't add the "what" exclusion rule it works fine and the subject become "No Subject [EXTERNE]".

It works great! Thank you!

I want to match any mails not containing the string "[EXTERNE]" at all in the subject field. The goal is to tag only a message if the tag is not already present (when users are receiving a reply of a reply, the tag would be already there).

Hello, I created a rule for incoming mail that add a suffix to the mail subject. This usually work fine but I found that some mails are not being tagged. I found that theses mails have something in common. The "subject" field contain a line return so the subject is displaying on two or more...

Hello, I see you have VM/CT encryption on your roadmap. Do you expect to add this feature for the next release or this is planned for a later one? Thanks.

Well, the clone is very similar to the baclup&restore, very long execution time depending of the content of the disk. What should I rename and edit? I could write a little helper script that would automate that. Thanks.

Hello, I use the last bit of ip address to generate my VMID. I refreshed a VM using a temporary ID to replace an existing VM. I made that VM into production and retired the old one. How could I change the VMID? I'm using lvm-thin local storage. I know I could backup&restore, but I don't like...

Interesting. Not sure if it's related. My NAS is running FreeNAS, not Synology. Also, PVE is able to connect most of the time to the NFS server, it just glitch randomly when doing vzdump on night.

Seem like this issue only occurs on my cluster upgraded to 6.0. My other cluster at 5.4 doesn't have this issue.

Hi, in my case I'm sure the server never goes to sleep.

Hello, What can cause this message? Each night, I do a scheduled vzdump of all VM in the cluster. I scheduled them in order that only one host is doing the task at a time to avoid to overload the NFS server. It works great most of the time. Sometime I have a VM failing to be backed up (timeout...

I still have nodes at 5.4 in my cluster (I suspended my upgrades when I discovered this issue). Is there an updated libknet for this release? I'm using this repo: http://download.proxmox.com/debian/corosync-3/. Thanks.

I created a what object that filter on attachment name "*\..*" and then used the action remove attachment (not the remove all attachment action). Seem to work fine. Thanks.

Hello, I'm trying to remove all attachment received by an email address. When I use the action remove all attachment, this also match "plain/text" attachement that content the message. Is there a way to block all attachment but allow text/plain and text/html? Thanks,

I have a single gigabit lan, so it can be somewhat loaded on backup time, but not more than before. Also, I didn't checked since I upgraded libknet, but before that, I found it was consuming good amount of RAM when the cluster is broken. Everything is back to normal once I restart corosync on...

Hello, I have a problem that seem related. I updated libknet on all my host (mix of 6.0 and 5.4 with upgraded corosync) but I still have problems with my cluster. My cluster is lost each night. I found that if I disable scheduled vzdump of my VMs, the cluster survives.

Cluster resumed once I restarted corosync on all nodes. Will see if the problem occurs again... I tried to see corosync logs, but the directory /var/log/corosync is empty (only have a file named ".empty").

Hello, I have a cluster of 5 nodes. Yesterday, I upgraded all nodes to corosync 3. Then I upgraded 2 of the nodes to Proxmox 6.0. So I now have 3 nodes at 5.4 and 2 at 6.0. Everything was working great yesterday after this upgrade. Today I come back to work and I see that all my nodes are...