Re: Fedora26. Cyrus- 3.0.3. cyr_virusscan None Configured.

> "AS" == Anton Shilov via Info-cyrus > writes: AS> I think it is missconfig because ClamAV isn't part of cyrus-imap AS> packet. The Fedora package is not configured to use clmav. This is because clamav in Fedora still uses the old openssl libraries

Re: update to 3.0.3 even more problematic than 3.0.2

FYI, upgrading from 2.4.12 to 2.5.11, and then to 3.0.3 (so, after that 2.5.11 converted the db files), I got a clean startup from the beginning, with no hassle on conversions. Still, I have the problem with LIST "" "Other Users" returning nothing :( As I mentioned, if I run LIST "" "Other

Re: update to 3.0.3 even more problematic than 3.0.2

That may be a good try :) Anyway I tried building / upgrading to 2.5.11, it converted my files in twoskip with no problems, and the shared folders work fine. Pity, I see it doesn't implement "THREAD=REFS" nor xapian ... :( I will try this version a little, then will try upgrading from this to

Re: update to 3.0.3 even more problematic than 3.0.2

Have you tried 3.0.3 (or 3.0.2) on a clean system just to be sure that your compile/install is working? 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

update to 3.0.3 even more problematic than 3.0.2

I tried upgrading to 3.0.3, same build, same everything. My original 2.4.12 db files are skiplist. I know almost all db files now default to twoskip, if not specified in imapd.conf, and it's not specified. This time, on first startup cyrus exited with strange errors about failing conversion.

Re: 2.4.12 vs 3.0.2 different protocol behaviour

I just upgraded from 2.4.17 to 3.0..3. My only troubles were with default options that changed, like the hierarchy separator, the namespace and delayed expunge. They all forced me to update scripts all around. And the namespace change had a nasty side effect: users must delete and add their

Re: 2.4.12 vs 3.0.2 different protocol behaviour

I will. Another note. I tried restarting from scratch, replicated my entire 2.4.12 system, checked that it worked as expected, updated packages to 3.0.2 and started cyrus as is with no upgrade : the problem is there just after updating the binaries, even before migrating the data to the new

Re: 2.4.12 vs 3.0.2 different protocol behaviour

This is 3.0.3 on Centos 7: * OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE XAPPLEPUSHSERVICE AUTH=DIGEST-MD5 AUTH=CRAM-MD5 AUTH=PLAIN AUTH=LOGIN SASL-IR] xx.xx.x Cyrus IMAP 3.0.3-Cyrus 3.0.3 server ready . login x x . OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE ACL

Fedora26. Cyrus- 3.0.3. cyr_virusscan None Configured.

Hi. I've installed Cyrus-imapd 3.0.3 into Fedora26 from standart packet manager "dnf install cyrus-imapd". This  rpm includes tool "cyr_virusscan". If I use it I get result such as: = # ./cyr_virusscan Using virus scanner 2 mailboxes scanned, 0 infected messages found =

Re: 2.4.12 vs 3.0.2 different protocol behaviour

Can anyone check these commands against their 3.0.2 and see if they get the same results? I've seen Thunderbird does not bother about it and correctly shows "Other Users" as "phantom", then shows the underlying tree. If what I found is the intended result, the only way for me is to find some