Re: 20200108 -- nexthop destinations separated by comma or whitespace

2020-01-29 Thread Viktor Dukhovni
On Wed, Jan 29, 2020 at 10:52:02AM +0100, Ralf Hildebrandt wrote: > > This looks wrong, it should be : > > > > exchange.charite.de > > exchange:s-mx14-ht01.charite.de,s-mx14-ht02.charite.de > > > > One "exchange" transport, multiple nexthop hosts. > > Cool. > > > Not sure why it worked

Re: 20200108 -- nexthop destinations separated by comma or whitespace

2020-01-29 Thread Ralf Hildebrandt
* Viktor Dukhovni : > > exchange.charite.de > > exchange:s-mx14-ht01.charite.de,exchange:s-mx14-ht02.charite.de > > This looks wrong, it should be : > > exchange.charite.de > exchange:s-mx14-ht01.charite.de,s-mx14-ht02.charite.de > > One "exchange" transport, multiple nexthop hosts.

Re: 20200108 -- nexthop destinations separated by comma or whitespace

2020-01-29 Thread Viktor Dukhovni
On Wed, Jan 29, 2020 at 09:56:45AM +0100, Ralf Hildebrandt wrote: > I don't see the change 20200108 reflected in the transport(5) man page. The HISTORY file writeup was: 20200108 UI cleanup: SMTP (and LMTP) client support for a list of nexthop destinations separate