Path to shared Calendars and task lists

2020-06-05 Thread Ian
Hi All,

One thing that I wasn't sure from the documentation was where shared
calendars and tasklists are on the CalDav server.

If joe has permission to fred's calendar 

https://servername/dav/calendars/user/joe/Default

Attempting access to the following by joe fails even when joe has full
access to all of fred's folders. What URL should be used?
https://servername/dav/calendars/user/fred/Default


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: Renaming mailboxes

2020-06-05 Thread Marco



Hello David,

Il 27/05/2020 16:48, David Moyes ha scritto:


I want to rename a mailbox (and all of its descendants), however I am
struggling with what, on the surface, would appear to be a simple task.

I first tried to use cyradm rename command to rename user.foo to
user@example.com, like this:

 localhost> rename user.foo user@example.com

However the rename command does not appear to be recursive, and I could
not find any argument to tell it to recurse. Do I have this right or am
I doing something wrong?


from what I remember, the rename is "recursive". If you login as an 
admin you can simply rename all users mailboxes from a name to a new 
name in a single step.


If you login as the user, then you have to move all folders as you 
describe below. Pay attention to specialuse folders and to the xapian 
indexes which could increase a lot.


I didn't remember on cyradm, but I currently use Cyrus::IMAP::Admin for 
almost all my scripts. I don't know if something of this could be useful 
for you:


https://github.com/falon/cyr_scripts
https://cloudsmith.io/~csi/repos/cyrus-scripts/packages/

(see at cyr_moveMailboxPart.pl, cyr_moveINBOX.pl)

Greetings
Marco


I decided to try it in a Perl script using Cyrus::IMAP::Admin. By doing
a `list` I could get the mailbox and its descendants like this:

 @mailboxes = $client->list("user/$oldname");
 @mailboxes_sub = $client->list("user/$oldname/*");
 push (@mailboxes , @mailboxes_sub);

(I found that listing "user/$oldname*" got me user.foo but also
user.foobar so I had to combine two calls to prevent that.)

Then I could iterate over the mailboxes doing

 $client->rename( $oldmailbox, $mailbox );

However, nothing works after the first rename; the program just exits,
not even "or die" error messages are displayed. In case it means
anything, the exit status is 141 which I think indicates a SIGPIPE (as
confirmed using `kill -l "$?"` which returns `PIPE`).

I did also notice a similar thing in cyradm, that after doing a rename
that subsequent action caused cyradm to exit:

localhost> rename user/testuser/Trash user/t...@example.net/Trash
renamemailbox:
localhost> lm  # this curiously returns nothing!

localhost> echo $?
0
localhost> lm
[cyrus@fee7fffd9be7 ~]$ echo $?
141


Any help would be greatly appreciated. I am currently using cyrus-imapd
3.0.13-3 on Arch Linux.



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 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 IMAP 3.2.1 released

2020-06-05 Thread ellie timoney
Hi Marco,

On Thu, Jun 4, 2020, at 11:04 PM, Marco wrote:
> On 29/05/2020 06:20, ellie timoney has written:
> > The Cyrus team is proud to announce the immediate availability of a new 
> > version of Cyrus IMAP: 3.2.1
> 
> Hello,
> 
>   in Redhat EL8 I still fail these tests:
> 
> ERRORS:
> Rename.rename_inbox
>   Perl exception: Errors found in syslog
>   at Cassandane/Instance.pm line 1322,  line 91.

You probably saw on github -- I've just pushed a fix to Cassandane which I 
think should fix up the remaining syslog-related failures...

Though, Rename.rename_inbox is a special exception.  This one will probably 
always error on 3.2.  There's a real (niche) bug, which this test is detecting. 
 It's existed for a very long time, but we're not sure how to fix it yet, so 
you might as well just ignore it.

Though... it's very interesting that it FOUND errors in syslog, when the usual 
RedHat problem is not being able to find the syslog output.  Curious?

> FAILS:
> 
> 1) Admin.imap_admins
>   expected 'ok', got 'no' at Cassandane/Cyrus/Admin.pm line 90.

This is interesting.  I'd like to see the full output please!

> 2) Caldav.supports_event
>   Boolean assertion failed at 
> /usr/share/perl5/vendor_perl/Test/Unit/Exception.pm line 13.

I think we discussed Caldav.supports_event before -- it passes here, still no 
idea what the difference is.  Maybe it's a libical thing?  What version is your 
libical?

> 3) ImapTest.append-binary
>   Boolean assertion failed at 
> /usr/share/perl5/vendor_perl/Test/Unit/Exception.pm line 13.
> 4) ImapTest.fetch-binary-mime
>   Boolean assertion failed at 
> /usr/share/perl5/vendor_perl/Test/Unit/Exception.pm line 13.
> 5) ImapTest.urlauth-binary
>   Boolean assertion failed at 
> /usr/share/perl5/vendor_perl/Test/Unit/Exception.pm line 13.

The "ImapTest.*-binary*" tests were known to be not-quite-right, and I believe 
have been removed from ImapTest-- my build is from 20190509 and doesn't contain 
them.  If you can't update ImapTest, it's reasonable to just suppress these 
three instead.

> 10) Cassandane::Test::Core.core_files_*
>didn't match /(?^:Core files found)/ at Cassandane/Test/Core.pm line 96.

The RedHat environment is probably preventing core files from being created, in 
which case the Test::Core tests will always fail.  That being the case, I'd 
suggest just suppressing them.

> The details are attached, if it could be of interest.

There's no attachment, did the mailing list eat it?  Feel free to send to me 
directly

If you update to the latest Cassandane (for the syslog fixes), then you'll 
start seeing failures on 3.2.1 from these tests:

JMAPEmail.blob_get
JMAPEmail.email_query_guidsearch_mixedfilter

These tests have been updated to detect bugs that will be fixed in 3.2.2, but 
of course they fail for 3.2.1 cause the bugs still exist in that version.

Cheers,

ellie

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