[Dovecot] listen directive changed?
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@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 proto
I 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.
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
Sorry about previous direct message, darn gmail and darn bosses ( policy says cant use company email for public lists)
On 4/15/13, Timo Sirainen tss@iki.fi wrote:
On 13.4.2013, at 7.13, Nick Edwards nick.z.edwards@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 proto
I 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.
On 18.4.2013, at 2.36, Nick Edwards nick.z.edwards@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?
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@iki.fi wrote:
On 18.4.2013, at 2.36, Nick Edwards nick.z.edwards@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?
On 19.4.2013, at 1.53, Nick Edwards nick.z.edwards@gmail.com wrote:
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.
If you comment out the address in inet_listener, it does use the global listen setting. I don't know why you can't connect at all then. Either the global listen setting is wrong or there's a bug in code that parses it.
On Fri, 2013-04-19 at 01:56 +0300, Timo Sirainen wrote:
On 19.4.2013, at 1.53, Nick Edwards nick.z.edwards@gmail.com wrote:
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.
If you comment out the address in inet_listener, it does use the global listen setting. I don't know why you can't connect at all then. Either the global listen setting is wrong or there's a bug in code that parses it.
no bug in 2.1.16 at least, because it certainly does work that way.
participants (3)
-
Nick Edwards
-
Noel Butler
-
Timo Sirainen