Am 01.01.2014, 17:04 Uhr, schrieb Paul J Stevens <[email protected]>:
On 01-01-14 16:36, Harald Leithner wrote:
Dbmail doesn't send this capabilities before the user is authenticated.
It will send them after login, so the proxy should? not announce the
capabilities before login or?
Looks like nginx will merge in the backend capabilities after
authentication.
I get this after login:
"OK [CAPABILITY IMAP4rev1 ACL RIGHTS=texk NAMESPACE CHILDREN SORT QUOTA
THREAD=ORDEREDSUBJECT UNSELECT IDLE STARTTLS ID] User xxx authenticated"
If you use TLS on the nginx side, you should probably disable STARTTLS
on the dbmail side, either by commenting the tls_ parameters in
dbmail.conf or by setting the CAPABILITY string manually.
Good idea, thx
If I don't tell the proxy the complete list I don't have to maintain it
after an upgrade of dbmail ;-)
set nginx:
imap_capabilities IMAP4 IMAP4rev1;
works fine now
nginx will merge the authentication and tls capabilities, and after
authentication everything from dbmail itself.
Also I don't know if nginx support IDLE.
I've been using nginx for ages with dbmail-2 and never had any problems
or complaints. IDLE just works fine.
Was only a example, maybe there is a capability that should not be
announced before the client is logged in.
@Paul that correct not to send all capabilities before login or?
Absolutely! This behavior was modelled on dovecot's behavior and
verified by the RFC.
I don't see the UIDPLUS behaviour on the nginx versions I'm
using/testing. It must be a recent addition.
--
Harald Leithner
ITronic
Wiedner Hauptstraße 120-124/5.1, 1050 Wien, Austria
Tel: +43-1-545 0 604
Fax: +43-1-786 23 88 26
Mobil: +43-699-123 78 4 78
Mail: [email protected] | itronic.at
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
