We use PF instead of IPTABLES, where overloading leads to banning of specific
IP (hence the useful absence of NAT). One such "workaround" would have to be
managed, for example with an e-mail to alert sysadmin followed up by some
manual labour. It is doable, but it does not solve the problem with
On Monday 08 May 2017 19:25:26 Rupert Gallagher wrote:
> Today the problem raised its head again, with a twist. A LAN client lost the
> DNS setting that pointed directly to the LAN address of the IMAP server,
> and two things happened: the LAN client could not connect to IMAP as we
> know, and a te
Today the problem raised its head again, with a twist. A LAN client lost the
DNS setting that pointed directly to the LAN address of the IMAP server, and
two things happened: the LAN client could not connect to IMAP as we know, and a
telephone call from the external client reported the same. Whe
