Been using Untangle for awhile and the quarantine digest is working for the most part. Untangle is in bridge mode and we have our own exchange server on the lan. The quarantine port is forwarded on our firewall (not using the firewall module in untangle).
My 2 problems are:
1 - new users (been here > 6 months) still do not have a quarantine. I know it's possible but it seems unlikely that they have received 0 spam in that time frame. Is there a way to test this by sending spam to their address and see if the quarantine is created as it should be (without signing them up for a barrage of future spam)? I did not change the default setting of '*' for create quarantines.
2 - we have several users outside the office and they cannot access their quarantine digest. Some connect via VPN and some do not. I have setup the hostname as untangle.ourdomain.com and setup the internal dns record on our DC. It works fine within the lan by IP or hostname. The vpn users cannot access the quarantine unless I allow outside https access but that seems to kill our untangle box. Do I need a bypass rule for this?
Even if I setup untangle.ourdomain.com at a dns registrar I don't think it will work. I tried going to our IP:port/quarantine from outside our network and it still did not work.
Not sure what to try for either of these problems.
My 2 problems are:
1 - new users (been here > 6 months) still do not have a quarantine. I know it's possible but it seems unlikely that they have received 0 spam in that time frame. Is there a way to test this by sending spam to their address and see if the quarantine is created as it should be (without signing them up for a barrage of future spam)? I did not change the default setting of '*' for create quarantines.
2 - we have several users outside the office and they cannot access their quarantine digest. Some connect via VPN and some do not. I have setup the hostname as untangle.ourdomain.com and setup the internal dns record on our DC. It works fine within the lan by IP or hostname. The vpn users cannot access the quarantine unless I allow outside https access but that seems to kill our untangle box. Do I need a bypass rule for this?
Even if I setup untangle.ourdomain.com at a dns registrar I don't think it will work. I tried going to our IP:port/quarantine from outside our network and it still did not work.
Not sure what to try for either of these problems.