On su, 2010-05-30 at 10:12 +0200, Stephan Bosch wrote: > As we > have seen earlier, fully changing the protocol name from "managesieve" > to "sieve" is a bad idea, for one because it causes much confusion. > > Timo, can you take a look at this?
Well, what parts should now be called managesieve and what parts sieve? There are at least: - process name (clearly managesieve) - service name for auth lookups - service name for access lookups (tcpwrappers) - service name when logging %s in login_log_format_elements - inet_listener name
