@chuckjuhl wrote:
Same thing happened to me. No idea why it happened. But I think it has something to do with the most recent update to the new firewall module. I disabled, flushed iptables and whitelisted Vitelity's inbound and outbound IP's and was able to get back to normal. One issue I confirmed with vitelity is that accounts are being assigned to specific inbound servers. I had been using inbound28.vitelity.net for all of my Vitelity accounts, but now you have to make sure that the inbound IP you are using is the one assigned to your Vitelity account. That and the above got me back to normal, but the new Firewall module seems to still be FUBAR. Every time I enable it with eth0 placed in the "external" zone everything goes haywire. To get back to normal i have to disable the firewall and flush iptables.