Apologies if this is a daft question, but I was experimenting with the
capability string on 3.1.7 and was surprised when I couldn’t 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.

If I just add IDLE (which is what I wanted to test) to the line i.e.

capability = IMAP4 IMAP4rev1 AUTH=LOGIN IDLE

again connecting by telnet just gives [CAPABILITY IMAP4rev1 AUTH=LOGIN]

I have tried editing another setting in the dbmail.conf file (the banner) to
make sure I am editing the correct file and that’s confirmed. I have also
confirmed that there is only one capability = line and that putting rubbish
in there (i.e. removing IMAP4 and IMAP4rev1) prevents dbmail-imapd from
loading.

So is there a reason why the capability string would not be making the
change I’m expecting (i.e. be reported when I connect to port 143 via
telnet?)

Daniel


------------------------
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

Reply via email to