CAPABILITY response in banner, how to disable it?
Hello, we recently switched from imapd version 2.2.12 to 2.4.12. Now my cellphone with bada-os 2.0 wont use the idle feature anymore. I assume the problem lies in the change that happened in version 2.3.4, the changelog states: "Implemented CAPABILITY response in banner and after authentication." The old version responded something like this: > TLS connection established: TLSv1 with cipher AES256-SHA (256/256 bits) > S: * OK Cyrus IMAP4 v2.2.13-Debian-2.2.13-13ubuntu3 server ready > C: C01 CAPABILITY > S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID > NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT > THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE AUTH=PLAIN SASL-IR > S: C01 OK Completed > Please enter your password: The new version responds like this: > TLS connection established: TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 > bits) > S: * OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE AUTH=PLAIN AUTH=LOGIN > SASL-IR] mail Cyrus IMAP v2.4.12-Debian-2.4.12-2 server ready > Please enter your password: > C: A01 AUTHENTICATE PLAIN string > S: A01 OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE ACL RIGHTS=kxte QUOTA > MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN > MULTIAPPEND BINARY CATENATE CONDSTORE ESEARCH SORT SORT=MODSEQ SORT=DISPLAY > THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE LIST-EXTENDED WITHIN > QRESYNC SCAN XLIST URLAUTH URLAUTH=BINARY LOGINDISABLED IDLE] Success (tls > protection) So it seems since the change in version 2.3.4 the imapd announces some CAPABILITYs already in the greeting/banner, but only a subset of the CAPABILITYs missing "idle" for example. The full CAPABILITYs string is presented after login. Now i guess that is the reason that i cant select the idle feature (push-sync) on my bada 2 device anymore. There is the option "serverinfo" in imapd.conf, but using this option has no influence on the CAPABILITYs string in the greeting. Is there a way to return to the old behaviour, or is there a good reason not to return to the old behaviour? Best regards Michael -- Michael Neumann michael.neum...@ub.tu-dortmund.de Universitaetsbibliothek Dortmund Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: CAPABILITY response in banner, how to disable it?
Am 31.10.2012 14:33, schrieb Patrick Boutilier: > > This doesn't answer your question but you can still issue the CAPABILITY > command before logging in. I see, so you can get the full CAPABILITY-string without being logged in. I guess the bada device only issues the CAPABILITY command if it is not in the server greeting already. So it is just bad luck for me that idle is not provided in the server greeting. > If you setup imap telemetry for the user you can see what commands the > bada device is issuing on connect. Above seems plausible to me, or would it be helpful to do more debugging here? Regards Michael -- Michael Neumann michael.neum...@ub.tu-dortmund.de Universitaetsbibliothek Dortmund Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Injecting a mail folder into a users inbox/restore from backup
Am 05.12.2012 15:19, schrieb John Wade: > We typically create a subfolder of the user's mailbox via cyradm or IMAP > commands, restore the files from the backup into this subdirectory and > run reconstruct. > > Requires no thought. Have used this far less since the delayed expunge > was introduced. Hello, delayed expunge sounds interesting to me, so far we used reconstruct to recover deleted mail from our backups. So i need the option expunge_mode set to delayed. Do i also need to set the option delete_mode to delayed? Most restore operations we have to do are about whole folders that have been deleted. Best regards Michael -- Michael Neumann michael.neum...@ub.tu-dortmund.de Universitaetsbibliothek Dortmund Bibliotheks-IT Telefon: +49 231 755 4773 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Injecting a mail folder into a users inbox/restore from backup
Am 12.12.2012 08:35, schrieb Michael Menge: > > expunge_mode is only for mails, delete_mode is the option for > folders but works slightly different. The deleted folder is > moved to a special folder (option deletedprefix in imapd.conf) > You can restore the folder with cyradm by movin it to the old > place. > > cyr_expire will remove the old mails an folders. Take a look at > the options and configure a cyr_expire run in the EVENT section > of cyrus.conf Thanks, so the delete_duration for mailboxes is set using the -D option of cyr_expire. I am now unsure about expunge_mode, there is an option expunge_days in imapd.conf and the -X option of cyr_expire, how do those two options work together? Best Regards Michael -- Michael Neumann michael.neum...@ub.tu-dortmund.de Universitaetsbibliothek Dortmund Bibliotheks-IT Telefon: +49 231 755 4773 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Injecting a mail folder into a users inbox/restore from backup
Am 12.12.2012 10:20, schrieb Sebastian Hagedorn: > > It pays to read the archive: > > <https://lists.andrew.cmu.edu/pipermail/info-cyrus/2012-January/035731.html> Yes, sorry and thanks, that clarifies it. Best Regards Michael -- Michael Neumann michael.neum...@ub.tu-dortmund.de Universitaetsbibliothek Dortmund Bibliotheks-IT Telefon: +49 231 755 4773 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
List currently logged on users
Hello, i am looking for a command that outputs the currently logged on users of cyrus imapd, is there something available? Best regards -- Michael Neumann Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: List currently logged on users
Am 12.09.2014 um 17:02 schrieb Michel Blanc:
>
> Hello,
>
> I use the following handy one liner :
>
>
> lsof -p `pidof imapd|tr ' ' ','` | \
> grep '/var/lib/cyrus/user/.*\.seen$' | \
> awk '{ print $9 }' | sort | uniq | \
> cut -f7 -d'/' | cut -f1 -d'.'
>
> with cyrus 2.2 under ubuntu server, YMMV !
Thanks, using lsof is a good idea, can be used to gather other useful
imap connection informations as well.
Regards
--
Michael Neumann
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: single instance message store problem.
Am 29.05.2015 um 22:19 schrieb Ken Murchison: > > Also, are you sure that your MTA isn't breaking up the recipients into > separate LMTP transactions? lmtpd can/will only do single instance > store for recipients that are part of the same transaction (MAIL FROM, > RCPT TO, DATA sequence). If the recipients are sent one at a time with > duplicate DATA commands, there are treated as distinct messages. That is the problem, postfix default local transport does only one at a time, that breaks single instance storage. We had to redefine it to: local_transport = lmtp:unix:/lmtp/lmtp Please read about the consequences in postconf manual. Hope that helps -- Michael Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: single instance message store problem.
Am 30.05.2015 um 13:43 schrieb John McMonagle: > > Michael > Thanks that works. > > Now maps in /etc/aliases are not working. > I have aliases in ldap that are working. > > Read http://www.postfix.org/LOCAL_RECIPIENT_README.html > Sounds like need local_recipient_maps. > It already existed and has hash:/etc/aliases. > > These are may maps: > #maps > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases > virtual_alias_maps = hash:/etc/postfix/virtual, > ldap:/etc/postfix/ldapdistlist.cf, > ldap:/etc/postfix/ldapvirtual.cf, > ldap:/etc/postfix/ldap-aliases.cf > #relocated_maps = hash:/etc/postfix/relocated > transport_maps = ldap:/etc/postfix/ldaptransport.cf > #virtual_mailbox_maps = $virtual_alias_maps > local_recipient_maps = $virtual_alias_maps, $alias_maps, > hash:/etc/postfix/local-accounts > > Just add hash:/etc/aliases to virtual_alias_maps ? Yes, we have it there too. Please consider that only mail address aliases will work, a pipe to a command, that is normally possible in /etc/aliases, wont work anymore (because you redefined the local_transport). Best regards -- Michael Neumann Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
