Re: Debugging A5 BAD Unexpected extra arguments to Search ?
Am 24.10.18 um 21:38 schrieb Stephan: Couldn't this be debugged by enabling telemetry logging ? Or is this feature missing from the newer releases ? https://www.cyrusimap.org/2.5/imap/faqs/o-telemetry.html I will have a look at this, thanks. :) I'm currently moving from cyrus 2.2 (old Ubuntu 10.04) to a "newer" (cyrus 2.4) version on Ubuntu 16.04. Maybe telemetry still works in these versions... :) Cheers, Kristian 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
Transfer folder subscriptions
Folks; I'm in the process of moving mails between two cyrus installations in order to at some point switch over all users. So far using imapsync and doing so as cyrus user met most of my needs, however I so far fail to transfer each users folder subscriptions. Given user names and folder hierarchy are exactly the same on both systems, is there any way to transfer the list of folders each user has subscribed without resetting all their passwords and running a tool such as imapsync on a per-user level? Thanks in advance and all the best, Kristian 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: Debugging A5 BAD Unexpected extra arguments to Search ?
Hi Ellie; ok, thanks for explaining. So I'll dive into the Java application and see whether debugging the search terms gets me any further. Cheers, Kristian Am 24.10.18 um 03:27 schrieb ellie timoney: The "A5" and "A7" are just the "tags" associated with the client's search commands, they have no semantic value. The client prefixes each command with some tag, and then the server uses the same tag in the response (so that you can identify which response applies to which command). In these two cases, your client has chosen "A5" and "A7" as tags. Tags are described in detail here: https://tools.ietf.org/html/rfc3501#section-2.2.1 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
Debugging A5 BAD Unexpected extra arguments to Search ?
Hi all; we're running a Java (and Java Mail) based application interacting with our cyrus imapd server. Trying to use complex search terms (searching for multiple criterias, such as message-id and message date), we regularly (all the time?) end up with messages such as A5 BAD Unexpected extra arguments to Searchor A7 BAD Unexpected extra arguments to Search Questions here: What's the difference between A5 and A7? Any way to debug what exactly is wrong about our search terms here? TIA and all the best, Kristian 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: mailbox / user migration to a new server
Hi Sebastian; Am 02.01.2018 um 14:12 schrieb Sebastian Hagedorn: > > You could copy the spool directories individually. You just need to > create all the new directories first, and your copy script needs a > mapping from the old user name to the new one. Then your script can use > the "mbpath" utility to find the disk path to each user's directory. thanks bunches for your feedback. So I'll see whether I'll get things done that way and get back here in case of any issues. :) Best, Kristian 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
mailbox / user migration to a new server
Folks; we're in the process of moving an "old" (cyrus 2.2.13, local Unix users) IMAP structure to a "newer" installation (cyrus 2.4.18, ActiveDirectory users attached using winbind). In total I'm about to move somewhere next to 300GB of mail spool knowing that ... - ... all this data has to be moved from one server to another and - ... most of the users now do have different user names (as the "old" Unix names differ from the "new" AD names) so data needs to be copied between different mailboxes. So just copying /var/spool/cyrus won't possibly work. Likewise, however, I can't use any of the IMAP migration scripts that do these things on a per-user basis as I am not supposed to know or mess with each users passwords; whatever I do sync-wise should be done using cyrus / administrative user accounts. Is something like this possible? How if so? What is the best way of doing this? TIA and all the best, Kristian 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: cyrus 2.4.18 / ubuntu and autocreateinboxfolders?
Hi Nicola; thanks for your response. Am Dienstag, den 24.10.2017, 10:40 +1100 schrieb Nicola Nye: > > We would certainly encourage moving to 3.0 if you can : there's a lot > of old bugs that have been fixed as well as some great new features > you might want to use. > No doubt and I actually would love to do so, but so far I fail to find a way to upgrade to 3.0 we can handle. :( So far I have been searching the repositories for virtually all distributions we could eventually dare to support in production, and the most "current" cyrus version I found is something like 2.15.xx, and I haven't found any newer Docker images either, not even sure whether Docker would be a way that might work for our setup. Do you guys really all run cyrus built from source in production? Likewise, does anyone have any idea what's the minimum version I would need for the autocreateinboxfolders feature to work? Right now this seems the only feature I am missing in the current 2.4 setup... Thanks in advance and all the best, Kristian 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
cyrus 2.4.18 / ubuntu and autocreateinboxfolders?
Folks; trying to set up a new cyrus system on top of Ubuntu 16.04 LTS (running cyrus 2.4.18), I fail to get the autocreateinboxfolder option to work. No errors to report - it simply doesn't seem to do anything, and I fail to get any more information why. So to ask: - I read that this feature originally came in in a patch one needed to apply to earlier versions of the server source. Is this still the case for 2.4.18? Could this be an Ubuntu thing, or should it work out of the box on 2.4.18 anyway? - As far as I see, the website is outlining cyrus 3.0.x as "stable" release. Is there a point in still using 2.4.18 anyway? Thanks loads and all the best, Kristian 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
"seen" flag for multiple users // cyrus and procmail
Hello all,... ...being pretty new to imap, I am running cyrus on top of several Debian woody machines inside some small / mid-range company networks. By now, I am quite happy about cyrus, procmail and postfix handling mail on my servers, still there are (right now) two things I couldn't get along with, so far: (a) in this network, IMAP is used because the vast majority of mail traffic needs to be seen not only by a single user but by a group of persons. For what I have experienced and also read in the archive of this list, it is not possible in cyrus (in IMAP?) to have a general "seen" flag for mails or mailboxes so this way it is impossible for any user who is able to read mail in the shared mailboxes to find out whether or not anyone else already has read and possibly answered new mail. Is there a way to work around this condition? Reading the cyrus man pages I hoped that the "s" ACL setting would be doing right what I need here but obviously it didn't work. (b) On my machine, procmail is used to sort mails. In some situ- ations mail needs to be delivered to more than just one mailbox, so I tried to use procmail filtering recipes like that: :0 c * ^TOwhoever | $DELIVER_TO_ANOTHER_MAILBOX The ":0 c" is working well while delivering mail to mail folders but it doesn't work while using cyrdeliver to put mails into IMAP mail boxes. _Is_ it possible to make some procmail configuration like this work with cyrus? TIA, have a nice evening everyone... Cheers, Kris -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
