Re: Recommended ManageSieve TCP port 2000 is already allocated to Cisco SCCP

[Arnt Gulbrandsen <arnt@xxxxxxxxxxxxxxxxxxx>]

Pushing SCCCP out of the way isn't going to work very well... I suggest 
getting a new port (x) and using these rules:

Clients MUST try port x first. If a client gets connection refused on 
the right port number, it MAY try 2000, but in that case it should 
watch out for SCCCP. Sieve banners look like <example>, and always 
contain a line starting with "SIEVE " and one starting with 
"IMPLEMENTATION ". SCCCP banners look like <example>, and always 
<dan?>.

Servers MUST listen to port x, and MAY also listen to 2000 to cater to 
old clients.

Client and server implementers using port 2000 should note that 
some/many old servers and clients have a bug wrt. literals. Sending 
correct literals may cause the peer to detect a "syntax error", and so 
does sending incorrect literals.

Arnt