On Sat, May 15, 2021 at 11:11:40AM +0100, Jeremy Harris via Exim-users wrote:
> On 15/05/2021 06:55, Jim Pazarena via Exim-users wrote:
> > a server with three IP numbers of the same subnet
>
> Generally a bad move. Unless the networks are physically
> separated, IP routing just gets confused.
On Sat, 15 May 2021, Jeremy Harris via Exim-users wrote:
On 15/05/2021 06:55, Jim Pazarena via Exim-users wrote:
a server with three IP numbers of the same subnet
Generally a bad move. Unless the networks are physically
separated, IP routing just gets confused.
Fix your network design.
Hm
Hi Jim,
Jim Pazarena via Exim-users (Sa 15 Mai 2021 07:55:24
CEST):
> I have a server with three IP numbers of the same subnet . my smtp transport
> specifies the specific outbound IP number .
> Yet other servers complain of an ssl mis-match because they are seeing one
> of the other IPs which a
On 15/05/2021 06:55, Jim Pazarena via Exim-users wrote:
a server with three IP numbers of the same subnet
Generally a bad move. Unless the networks are physically
separated, IP routing just gets confused.
Fix your network design.
--
Cheers,
Jeremy
--
## List details at https://lists.exim.o
On Fri, 14 May 2021, Jim Pazarena via Exim-users wrote:
I have a server with three IP numbers of the same subnet . my smtp transport
specifies the specific outbound IP number .
Yet other servers complain of an ssl mis-match because they are seeing one of
the other IPs which are not in the " int
I have a server with three IP numbers of the same subnet . my smtp
transport specifies the specific outbound IP number .
Yet other servers complain of an ssl mis-match because they are seeing
one of the other IPs which are not in the " interface = " line .
Is there an easy way to determine how
