Search results

Thanks for the reply, pmg version pmg-api: 6.1-2 pmg-gui: 2.1-3 pve-kernel-5.3: 6.0-12 pve-kernel-helper: 6.0-12 pve-kernel-5.3.10-1-pve: 5.3.10-1 libarchive-perl: 3.3.3-1 libjs-extjs: 6.0.1-10 libjs-framework7: 4.4.7-1 libpve-apiclient-perl: 3.0-2 libpve-common-perl: 6.0-8...

HI Currently i was checking to update the database of clam AV im getting this error Feb 1 23:18:52 mail freshclam[16755]: Trying again in 5 secs... Feb 1 23:18:57 mail freshclam[16755]: Your ClamAV installation is OUTDATED! Feb 1 23:18:57 mail freshclam[16755]: Local version: 0.101.4...

HI I was wondering if someone could shed some light Currently on my test environment trying to test out how to replace a disk when bios is using uefi These are the steps i have so far, Were going to assume that ata-VBOX_HARDDISK_VBd49634a6-155a6124-part3 died root@pve:~# zpool status pool...

i would love to try it out, running zabbix 5.2 with proxmox 6.x.x

thanks for the reply, correct they both have the same domain, but synchronization@mydomain.com is not an email we have it was a fake email that was sent from cloudgate.m1net.com.sg what i did was a reboot and now i saw that it was getting blocked, it seems that the rules were getting blocked

on the return path i get this the who object is @mydomain.com Return-Path: <synchronization@mydomain.com> Received: from mail.mydomain.com (LHLO mail.mydomain.com) (192.168.3.170) by mail.mydomain.com with LMTP; Thu, 9 Dec 2021 13:17:00 -0500 (COT) Received: from mail.mydomain.com (unknown...

thanks for the reply, the rule was to block any @mydomain.com because internally email do not pass though PMG the fakeemail is @mydomain.com

Hi I was wondering if someone could shed some light on the issue im having, Currently i created rules so that external emails cannot send fake email to my domain ex: synchronization@mydomain.com to cartera@mydomain.com synchronization@mydomain.com being the fake email i created a rule to...

Well whats odd is that it did not affect none of the vms for me

your right, i had the rule for outbound didnt realize it thank you again

Thanks for the reply, so i solved on zimbra using the BCC going inside of I tried the BCC on Proxmox but only works for outbound nano /opt/zimbra/common/conf/sender_bcc and adding @domain.com and redirect to the email i want

correct, but its to forward mails and not domain

Thanks for the reply, but on the action objects i dont have the action forward running 6.1.2

Hi I was wondering if someone else has accomplish this, Currently im trying to redirect emails from @clientdomain.com to a certain user@mydomain.com the idea is that But i could not find any option or action to send or forward Thank you

Hi I was wondering if someone else has tried the xshok proxmox script on their server for production? Currently using it on a test environment and i see that everything seems to be working fine. Havent seen nothing out of the ordinary wget...

Thanks for the reply, correct i was reading back then that its dangerous running it, but so far haven't had any troubles yet as i have copies. I use ZFS because of the way it uses snapshots while having the VM on with no issue. I thought adding a slog or l2arc would speed up more the ZFS pool...

thanks for the reply, so if i have zfs set sync=disabled rpool its pointless having a slog?

Hi I was wondering if someone could shed some light. Currently trying to test out the speed difference with slog and without, in my test environment i have computer with 32 gigs of ram and raid zfs1 with toshiba 1tb HDD 7200rpm I ran a bench test (not sure if its the correct way to benchmark)...

Thank you so much, that did the trick, I had to add on hosts root@pve3:~# cat /etc/hosts 127.0.0.1 localhost.localdomain localhost 192.168.6.48 pve3.casa.local pve3 192.168.6.49 a1 and with editing the .ssh/config host a1 HostName 192.168.6.49 Port 2201

Thanks for the reply, so after trying various was still could not get it working, Not sure if i understood correctly, so i created a test environment to try it out before so server b1 is 192.168.6.48 and server a2 192.168.6.49 on server b1 i went to the config and added this root@pve3:~# cat...