Thank you. Perhaps I'm misremembering it, but I thought back in dbmail 2.x connecting by telnet gave the full capability string in the banner hence I was expecting it with dbmail 3.1.x
Daniel Reindl Harald Wed, 02 Oct 2013 01:52:57 -0700 Am 02.10.2013 10:44, schrieb Daniel Schütze: > Apologies if this is a daft question, but I was experimenting with the > capability string on 3.1.7 and was surprised when I couldnt actually change > the default. > > On my current server the capability is hashed out in the dbmail.conf and > using telnet to connect to 143 I get > > Trying 127.0.0.1... > Connected to loopback. > Escape character is '^]'. > * OK [CAPABILITY IMAP4 IMAP4rev1 AUTH=LOGIN] dbmail 3.1.7 ready. > > If I add the following line from the man page of dbmail in dbmail.conf > > capability = IMAP4 IMAP4rev1 AUTH=LOGIN ACL RIGHTS=texk NAMESPACE > CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE > > it makes no difference to the CAPABILITY reported by connecting with telnet you get the full capabilities after login with the capability command http://tools.ietf.org/html/rfc3501#section-6.1.1 that's RFC conform while i prefer the dovecot-way showing full capabilities in the banner ------------------------ CWA International Balmoral House 9 John Street London WC1N 2ES (t) + 44 (0)20 7242 8444 (e) [email protected] (w) http://www.cwa.uk.com/ _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
