[Dovecot] Dovecot 2.0beta4: Managesieve example config
Hi,
the 'example-config' holds an incorrect value for the listener socket:
$ head -10 20-managesieve.conf ## ## ManageSieve specific settings ##
# Service definitions
service managesieve-login { #inet_listener sieve { # port = 4190 #}
inet_listener sieve <> inet_listener managesieve
Regards Thomas
Code has managesieve, example config has sieve. I guess the code is wrong, since http://www.iana.org/assignments/port-numbers calls the 4190 port "sieve".
On Sun, 2010-04-25 at 12:27 +0200, Thomas Leuxner wrote:
Hi,
the 'example-config' holds an incorrect value for the listener socket:
$ head -10 20-managesieve.conf ## ## ManageSieve specific settings ##
# Service definitions
service managesieve-login { #inet_listener sieve { # port = 4190 #}
inet_listener sieve <> inet_listener managesieve
Regards Thomas
Hi Timo,
Timo Sirainen wrote:
Code has managesieve, example config has sieve. I guess the code is wrong, since http://www.iana.org/assignments/port-numbers calls the 4190 port "sieve".
Hmm, didn't we decide to use "managesieve" everywhere as to avoid confusion? I've renamed the service back and forth back then, remember?
Regards,
Stephan.
On Wed, 2010-05-26 at 16:48 +0200, Stephan Bosch wrote:
Code has managesieve, example config has sieve. I guess the code is wrong, since http://www.iana.org/assignments/port-numbers calls the 4190 port "sieve".
Hmm, didn't we decide to use "managesieve" everywhere as to avoid confusion? I've renamed the service back and forth back then, remember?
Yes, I remember we did. :) But I'm not sure about the port specifically. Maybe the port names should match what's in /etc/services.. Or maybe it doesn't matter. I'm not sure.
Onsdag 26. mai 2010 17.20.29 skrev Timo Sirainen :
On Wed, 2010-05-26 at 16:48 +0200, Stephan Bosch wrote:
Code has managesieve, example config has sieve. I guess the code is wrong, since http://www.iana.org/assignments/port-numbers calls the 4190 port "sieve".
Hmm, didn't we decide to use "managesieve" everywhere as to avoid confusion? I've renamed the service back and forth back then, remember?
Yes, I remember we did. :) But I'm not sure about the port specifically. Maybe the port names should match what's in /etc/services.. Or maybe it doesn't matter. I'm not sure.
Er, maybe I'm shooting my foot here, but I think it should match. Unless we're discussing different things port 2000 is listed for sieve in /etc/services
grep sieve /etc/services cisco-sccp 2000/tcp sieve # Cisco SCCP
Changing it would be (exaggeration!) like putting IMAP on port 1234
Arne
Arne K. Haaje | www.drlinux.no T: 69 51 15 52 | M: 92 88 44 66
On 05/26/2010 09:41 PM Arne K. Haaje wrote:
Er, maybe I'm shooting my foot here, but I think it should match. Unless we're discussing different things port 2000 is listed for sieve in /etc/services
grep sieve /etc/services cisco-sccp 2000/tcp sieve # Cisco SCCP
Changing it would be (exaggeration!) like putting IMAP on port 1234
hm, user@localhost dovecot-2.0 $ grep sieve /etc/services && ll !$ grep sieve /etc/services && ll /etc/services sieve 4190/tcp # ManageSieve Protocol -rw-r--r-- 1 root root 19226 Dec 12 00:26 /etc/services
And also IANA (http://www.iana.org/assignments/port-numbers) says: sieve 4190/tcp ManageSieve Protocol
Regards, Pascal
The trapper recommends today: cafefeed.1014621@localdomain.org
Den 26.05.2010 21:53, skrev Pascal Volk:
On 05/26/2010 09:41 PM Arne K. Haaje wrote:
Er, maybe I'm shooting my foot here, but I think it should match. Unless we're discussing different things port 2000 is listed for sieve in /etc/services
grep sieve /etc/services cisco-sccp 2000/tcp sieve # Cisco SCCP
Changing it would be (exaggeration!) like putting IMAP on port 1234
hm, user@localhost dovecot-2.0 $ grep sieve /etc/services&& ll !$ grep sieve /etc/services&& ll /etc/services sieve 4190/tcp # ManageSieve Protocol -rw-r--r-- 1 root root 19226 Dec 12 00:26 /etc/services
And also IANA (http://www.iana.org/assignments/port-numbers) says: sieve 4190/tcp ManageSieve Protocol
I can only reply that Kmail sets 2000 as default port when setting "server supports sieve".
But this is an interesting update, it looks like ManageSieve has officially been moved to 4190 from 2000; http://news.debian.net/2009/12/13/debian-is-moving-sieve-to-its-iana-allocat...
So old stuff out and new stuff in I guess ;)
Arne
participants (5)
-
Arne K. Haaje
-
Pascal Volk
-
Stephan Bosch
-
Thomas Leuxner
-
Timo Sirainen