This might be unrelated to the upgrade... and more to do with using our local ISP's DNS (Cox) 68.105.28.16 and 68.105.29.16
Since the upgrade we noticed a ton more spam is coming through.
spamassassin is firing the URIBL_BLOCKED rule - it's all over the logs. Spam that used to get flagged as spam now passes with a score of zero.
Reading these notes:
http://uribl.com/refused.shtml
If you are low volume user, you have a few options. Possibly changing your nameservers from a public dns provider (ie opendns/google) to your local ISP may solve it. If your local ISP is also effected because they are very large (ie cox/att/comcast/etc), you may need to use your own recursive DNS solution. If your company has DNS servers, point to them for resolution. Alternatively, you could setup a caching nameserver on the loopback of the machine doing the spam checking, and point the DNS to localhost.
We do have a DNS server internally within our network. Do I add the local IP address of our DNS server to Untangle's external interface primary DNS?