Timo, Is the global listen directive supposed to be a governing directive, like in apache? or is it there just in case you dont use it in protocols? I set a specific ipv6 address in global listen, but use [::] in proto Testing to a secondary IP, not in the global listen, it still connects, so can I ask has the original use of global listen been deprecated? ciao
On 13.4.2013, at 7.13, Nick Edwards <nick.z.edwards at gmail.com> wrote:> Is the global listen directive supposed to be a governing directive, > like in apache? or is it there just in case you dont use it in > protocols? > > I set a specific ipv6 address in global listen, but use [::] in protoI don't understand what you mean by "in proto". If you mean inside protocol {} setting, that's a deprecated way and should log warnings about it.> Testing to a secondary IP, not in the global listen, it still > connects, so can I ask has the original use of global listen been > deprecated?It's the default listen setting, which gets used by all services' inet_listeners that don't override it.
So what is the point of the global? I commented out the address in inet_listener, assuming it then will use global, but no, cant connect at all then. Should for clarification, should we not use global entry and rely on inet_listener? Or should there be a change so inet_listener pulls its addresses from global if no address is provided in inet_listener statements it seems at present to be two competing options. On 4/19/13, Timo Sirainen <tss at iki.fi> wrote:> On 18.4.2013, at 2.36, Nick Edwards <nick.z.edwards at gmail.com> wrote: > >> I do not get warnings, and, >> >> listen = *, ::1, 2001:470:some:subnet::ffff >> >> _snip_ >> inet_listener imap { >> address = *,[::] >> port = 143 >> ... >> >> same with pop3 >> >> If I use 2001:470:some:subnet::2222 dovecot (2.1.16) answers > > If you override the imap+pop3 inet_listener, then yes it overrides the > default listen setting and Dovecot listens on [::]. What did you want to > happen? > >