Re: sync_client: IOERROR: fetching subscriptions

2020-10-09 Thread Jean Charles Delépine 
Jean Charles Delépine  écrivait (wrote) :

> 2020-10-06T10:51:45.070636+02:00 cyrus-3.0.8  cyrus/imap[2714758]: IOERROR: 
> fetching subscriptions for user1

user1.sub didn't have correct tab line termination. Certainly my fault
sometime in the past.

Jean Chales Delépine

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

sync_client: IOERROR: fetching subscriptions

2020-10-07 Thread Jean Charles Delépine 

Hello,

While replicating one 3.0.9 server to a 3.2.3 server 2 accounts failed to 
synchronise with this error :


OK success
cyrus/sync_client[2745008]: IOERROR: fetching subscriptions for user1
Error from sync_do_user(user1): bailing out!
cyrus/sync_client[2745008]: Error in sync_do_user(user1): bailing out!

1601973199>EXIT

<1601973199Trying to migrate this mailbox on another server (3.0.9) gave a similar 
error :


2020-10-06T10:51:43.556312+02:00 cyrus-3.0.8  cyrus/imap[2714758]: XFER: user 
'user1' ->  cyrus-3.2.3
2020-10-06T10:51:43.558342+02:00 cyrus-3.0.8  cyrus/imap[2714758]: XFER: 
initial sync of user user1
2020-10-06T10:51:43.558575+02:00 cyrus-3.0.8  cyrus/imap[2714758]: USER user1
2020-10-06T10:51:43.933958+02:00 cyrus-3.0.8  cyrus/imap[2714758]: 
LOCAL_MAILBOX user.user1
2020-10-06T10:51:44.714252+02:00 cyrus-3.0.8  cyrus/imap[2714758]: 
LOCAL_MAILBOX user.user1.Drafts
[...]
2020-10-06T10:51:44.988079+02:00 cyrus-3.0.8  cyrus/imap[2714758]: 
LOCAL_MAILBOX user.user1.Trash
2020-10-06T10:51:45.070636+02:00 cyrus-3.0.8  cyrus/imap[2714758]: IOERROR: 
fetching subscriptions for user1

The user can list his subscriptions and change them :

C: A01 AUTHENTICATE PLAIN ZGQtbGFyaWEAZGQtbGFyaWEARzRsYUZvdWkx  
S: A01 OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE ACL RIGHTS=kxten QUOTA MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT 
CHILDREN MULTIAPPEND BINARY CATENATE CONDSTORE ESEARCH SEARCH=FUZZY SORT SORT=MODSEQ SORT=DISPLAY SORT=UID THREAD=ORDEREDSUBJECT THREAD=
REFERENCES THREAD=REFS ANNOTATEMORE ANNOTATE-EXPERIMENT-1 METADATA LIST-EXTENDED LIST-STATUS LIST-MYRIGHTS LIST-METADATA WITHIN QRESYNC 
SCAN XLIST XMOVE MOVE SPECIAL-USE CREATE-SPECIAL-USE DIGEST=SHA1 X-REPLICATION URLAUTH URLAUTH=BINARY MUPDATE=mupdate://cyrus-mupdate/

LOGINDISABLED COMPRESS=DEFLATE X-QUOTA=STORAGE X-QUOTA=MESSAGE 
X-QUOTA=X-ANNOTATION-STORAGE X-QUOTA=X-NUM-FOLDERS IDLE] Success (tls
 protection) SESSIONID= 
Authenticated.  
Security strength factor: 256   
. LSUB "*" "*"  
* LSUB (\HasChildren) "." INBOX 
[...]

* LSUB () "." INBOX.archives.2000-2019.2018
* LSUB () "." INBOX.archives.2000-2019.2019 
. OK Completed (0.006 secs) 
. UNSUBSCRIBE INBOX.archives.2000-2019.2019 
. OK Completed  
. LSUB "*" "*"  
* LSUB (\HasChildren) "." INBOX

[...]
* LSUB () "." INBOX.archives.2000-2019.2018



I don't understand. Where can be the problem ?

Sincerly,
 Jean Charles Delépine

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: Replication : IMAP_PROTOCOL_ERROR Protocol error

2020-10-01 Thread Jean Charles Delépine 
Jean Charles Delépine  écrivait (wrote) :

> Jean Charles Delépine  écrivait (wrote) :
> 
> > Hello,
> > 
> > I'm on the way to migrate one quite big murder config with Cyrus IMAP
> > 3.0.8-Debian-3.0.8-6+deb10u4
> > to Cyrus IMAP 3.2.3-Debian-3.2.3-1~bpo10+1.
> > 
> > My plan is to replicate 3.0.8's backends on 3.2.3 ones. This plan has work
> > before for 2.5
> > to 3.0. migration.
> > 
> > Il can replicate empty mailboxes. So the conf (attached) seems ok.
> > But if the mailbox isn't empty here's the result (completes traces 
> > attached) :
> 
> The conf might not be _that_ ok.
> 
> If the option conversation is set to 1 and I create new mailboxes, ond
> send mails to this mailboxes, no sync of these mailboxes is possible.
> 
> If I remove the option 'conversation: 1', any new populated mailboxes can 
> be sync.
> 
> So, the problem seems to be in this option.
> 
> But even after removing "conversation: 1" and zeroed conversation indexes
> (ctl_conversationsdb -z), the old "bad" mailboxes can't be synced. Even
> removing their .conversations and .counters files doesn't help.
> 
> Can I, and how can I,  get rid of those conversation indexes in order to have
> my mailboxes being "as if there never been conversation" ?

After removing "conversations: 1" option AND restarted the serveur,
ctl_conversationsdb -z did correctly remove conversations indexes and
the replication finally works fine.

I did have to revert xapian usage (which needs conversations) and switch
back to squat indexes.

Jean Charles Delépine

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: Replication : IMAP_PROTOCOL_ERROR Protocol error

2020-09-26 Thread Jean Charles Delépine 
ellie timoney  écrivait (wrote) :

> On Thu, 24 Sep 2020, at 1:44 AM, Jean Charles Delépine wrote:
> > Is this a known problem corrected after 3.0.9 ?
> 
> Off the top of my head I no longer remember, but the current release in the 
> 3.0 series is 3.0.14.  I'd suggest, if you haven't already, that you look in 
> the release notes from 3.0.8-3.0.14 and see if anything looks relevant.  
> They're here: 
> https://www.cyrusimap.org/imap/download/release-notes/3.0/index.html

I didn't find anything relevant.

> We don't generally recommend in-place upgrades between series (so, upgrading 
> in-place from 3.0.8 to 3.2.3 is not something we'd recommend).  
> Within-series, an in-place upgrade ought to be safe -- but please check the 
> release notes carefully for extra steps/considerations you may need to make, 
> depending on your deployment.  I think you'll probably want to upgrade your 
> 3.0 systems in place as far forward as you can (while staying 3.0), and then 
> use the replication strategy to upgrade to 3.2 after that.

I just do that. My test server is now using 3.0.14 (self build debian package) :

>1601118406>APPLY MAILBOX %(UNIQUEID m8lfz12835tr5y3dfucebk95 MBOXNAME 
>user.testes2 SYNC_CRC 2393559122 SYNC_CRC_ANNOT 4164967045 LAST_UID 2 
>HIGHESTMODSEQ 4 RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE 1601117744 
>POP3_LAST_LOGIN 0 POP3_SHOW_AFTER 0 XCONVMODSEQ 4 UIDVALIDITY 1601117689 
>PARTITION default ACL "testes2lrswipkxtecdan  " OPTIONS P RECORD 
>(%(UID 1 MODSEQ 4 LAST_UPDATED 1601118406 FLAGS (\Expunged) INTERNALDATE 
>1601117744 SIZE 2890 GUID 6f160d7026f4adbaebb2d0941c6398272a8692da ANNOTATIONS 
>(%(ENTRY /vendor/cmu/cyrus-imapd/thrid USERID NIL VALUE fee5d4912d9da6a8))) 
>%(UID 2 MODSEQ 3 LAST_UPDATED 1601118406 FLAGS () INTERNALDATE 1601117744 SIZE 
>2890 GUID 6f160d7026f4adbaebb2d0941c6398272a8692da ANNOTATIONS (%(ENTRY 
>/vendor/cmu/cyrus-imapd/thrid USERID NIL VALUE fee5d4912d9da6a8)
<16011184061601118406>EXIT
<1601118406http://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: Replication : IMAP_PROTOCOL_ERROR Protocol error

2020-09-24 Thread Jean Charles Delépine 
Jean Charles Delépine  écrivait (wrote) :

> Hello,
> 
> I'm on the way to migrate one quite big murder config with Cyrus IMAP
> 3.0.8-Debian-3.0.8-6+deb10u4
> to Cyrus IMAP 3.2.3-Debian-3.2.3-1~bpo10+1.
> 
> My plan is to replicate 3.0.8's backends on 3.2.3 ones. This plan has work
> before for 2.5
> to 3.0. migration.
> 
> Il can replicate empty mailboxes. So the conf (attached) seems ok.
> But if the mailbox isn't empty here's the result (completes traces attached) :

The conf might not be _that_ ok.

If the option conversation is set to 1 and I create new mailboxes, ond
send mails to this mailboxes, no sync of these mailboxes is possible.

If I remove the option 'conversation: 1', any new populated mailboxes can 
be sync.

So, the problem seems to be in this option.

But even after removing "conversation: 1" and zeroed conversation indexes
(ctl_conversationsdb -z), the old "bad" mailboxes can't be synced. Even
removing their .conversations and .counters files doesn't help.

Can I, and how can I,  get rid of those conversation indexes in order to have
my mailboxes being "as if there never been conversation" ?

Sincerly,
  Jean charles Delépine

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

Replication : IMAP_PROTOCOL_ERROR Protocol error

2020-09-23 Thread Jean Charles Delépine 

Hello,

I'm on the way to migrate one quite big murder config with Cyrus IMAP  
3.0.8-Debian-3.0.8-6+deb10u4

to Cyrus IMAP 3.2.3-Debian-3.2.3-1~bpo10+1.

My plan is to replicate 3.0.8's backends on 3.2.3 ones. This plan has  
work before for 2.5

to 3.0. migration.

Il can replicate empty mailboxes. So the conf (attached) seems ok.
But if the mailbox isn't empty here's the result (completes traces attached) :

cyrus/sync_client[3082351]: MAILBOX received NO response:  
IMAP_PROTOCOL_ERROR Protocol error

cyrus/sync_client[3082351]: do_folders(): update failed: user.t 'Bad protocol'
cyrus/sync_client[3082351]: IOERROR: do_user_main: Bad protocol for t  
to [no channel] (test-3.2.3)

Error from sync_do_user(t): bailing out!
cyrus/sync_client[3082351]: Error in sync_do_user(t): bailing out!

The destination server says :
   SYNCERROR: failed to parse uploaded record


If I upgrade this test server to 3.2.3-Debian-3.2.3-1~bpo10+1 with  
the same configuration, the same mailbox

can be sync whith the problem being corrected :


APPLY MAILBOX %(UNIQUEID 6kjf8ro4032wfjefcdewaqyl MBOXNAME user.t  
SYNC_CRC 3435668400 SYNC_CRC_ANNOT 1359939586 LAST_UID 1 HIGHESTMODSEQ  
3 RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE 0 POP3_LAST_LOGIN 0  
POP3_SHOW_AFTER 0 XCONVMODSEQ 3 UIDVALIDITY 1600855436 PARTITION  
default ACL "" OPTIONS P FOLDERMODSEQ 3 SINCE_MODSEQ 3 SINCE_CRC 0  
SINCE_CRC_ANNOT 12345678 RECORD ())

<1600872848cyrus/sync_client[3131948]: MAILBOX received NO response:  
IMAP_SYNC_CHECKSUM Checksum Failure
cyrus/sync_client[3131948]: SYNC_NOTICE: CRC failure on sync user.t,  
recalculating counts and trying again


Error but retry.

MAILBOX user.t
1600872848>APPLY MAILBOX %(UNIQUEID 6kjf8ro4032wfjefcdewaqyl  
MBOXNAME user.t SYNC_CRC 3435668400 SYNC_CRC_ANNOT 1370712396  
LAST_UID 1 HIGHESTMODSEQ 3 RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE  
0 POP3_LAST_LOGIN 0 POP3_SHOW_AFTER 0 XCONVMODSEQ 3 UIDVALIDITY  
1600855436 PARTITION default ACL "" OPTIONS P FOLDERMODSEQ 3 RECORD  
())

<1600872848cyrus/sync_client[3131948]: MAILBOX received NO response:  
IMAP_SYNC_CHECKSUM Checksum Failure

cyrus/sync_client[3131948]: CRC failure on sync for user.t, trying full update

Error then full update

FULLMAILBOX user.t

1600872848>GET FULLMAILBOX user.t
<1600872848<* MAILBOX %(UNIQUEID 6kjf8ro4032wfjefcdewaqyl MBOXNAME  
user.t SYNC_CRC 0 SYNC_CRC_ANNOT 12345678 LAST_UID 1 HIGHESTMODSEQ 3  
RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE 0 POP3_LAST_LOGIN 0  
POP3_SHOW_AFTER 0 XCONVMODSEQ 3 UIDVALIDITY 1600855436 PARTITION  
default ACL "" OPTIONS P FOLDERMODSEQ 3 RECORD ())

OK success
cyrus/sync_client[3131948]: user.t: same message appears twice 1 2
MAILBOX user.t
1600872849>APPLY MESSAGE (%{default  
f0eeef2cc42f23884089760cf5de1961b358a498 2627}



)
<16008728491600872849>APPLY MAILBOX %(UNIQUEID 6kjf8ro4032wfjefcdewaqyl  
MBOXNAME user.t SYNC_CRC 1009437458 SYNC_CRC_ANNOT 455745080  
LAST_UID 2 HIGHESTMODSEQ 5 RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE  
0 POP3_LAST_LOGIN 0 POP3_SHOW_AFTER 0 XCONVMODSEQ 5 UIDVALIDITY  
1600855436 PARTITION default ACL "" OPTIONS P FOLDERMODSEQ 3 RECORD  
(%(UID 1 MODSEQ 5 LAST_UPDATED 1600872848 FLAGS (\Expunged)  
INTERNALDATE 1600855652 SIZE 2627 GUID  
f0eeef2cc42f23884089760cf5de1961b358a498 ANNOTATIONS (%(ENTRY  
/vendor/cmu/cyrus-imapd/thrid USERID "" MODSEQ 0 VALUE  
611d36cdcf46289a))) %(UID 2 MODSEQ 4 LAST_UPDATED 1600872848 FLAGS  
() INTERNALDATE 1600855652 SIZE 2627 GUID  
f0eeef2cc42f23884089760cf5de1961b358a498 ANNOTATIONS (%(ENTRY  
/vendor/cmu/cyrus-imapd/thrid USERID "" MODSEQ 0 VALUE  
611d36cdcf46289a)

<16008728491600872849>APPLY MAILBOX %(UNIQUEID nckzm4o710aom3c22o9ugy6a  
MBOXNAME user.t.Drafts SYNC_CRC 0 SYNC_CRC_ANNOT 0 LAST_UID 0  
HIGHESTMODSEQ 2 RECENTUID 0 RECENTTIME 0 LAST_APPENDDATE 0  
POP3_LAST_LOGIN 0 POP3_SHOW_AFTER 0 XCONVMODSEQ 2 UIDVALIDITY  
160087 PARTITION default ACL "" OPTIONS P FOLDERMODSEQ 2 RECORD  
())

<1600872849
1600872849>EXIT

<1600872849Is there something I can do to successfully replicate my backends to  
my new servers ?


Sincerly,
Jean Charles Delépine
configdirectory: /var/lib/cyrus
proc_path: /run/cyrus/proc
mboxname_lockpath: /run/cyrus/lock
defaultpartition: default
partition-default: /var/spool/cyrus/mail
partition-news: /var/spool/cyrus/news
newsspool: /var/spool/news
altnamespace: no
postuser: share-post
unixhierarchysep: no
lmtp_downcase_rcpt: yes
allowanonymouslogin: no
popminpoll: 1
autocreate_post: yes
autocreate_quota: 0
umask: 077
sieveusehomedir: false
sievedir: /var/spool/sieve
httpmodules: caldav carddav
hashimapspool: true
sasl_auto_transition: no
tls_client_ca_dir:
tls_session_timeout:
tls_versions:
lmtpsocket: /var/run/cyrus/socket/lmtp
idlesocket: /var/run/cyrus/socket/idle
notifysocket: /var/run/cyrus/socket/notify
syslog_prefix: cyrus
admins: mailadmin
metapartitio

Re: Upgrade to 3.2.2 and sieve

2020-06-26 Thread Jean Charles Delépine 
Stephan  écrivait (wrote) :

> sieve_rebuild: [path to script] parse failed: script errors:#015#012line
> 5: header 'resent-from': not a valid header for an address test

I had the same error with a 2.5 to 3.0 migration.

Corrected with 'rfc3028_strict: 0' :

rfc3028_strict: 1
  If enabled, Sieve will be strict (per RFC 3028) with regards to which
  headers are allowed to be used in address and envelope tests.  This means that
  only those headers which are defined to contain addresses will be allowed in
  address tests and  only  "to"  and "from" will be allowed in envelope tests.
  When disabled, ANY grammatically correct header will be allowed.


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

Debian's cyrus 2.5.10 ctl_mboxlist segfault

2017-08-08 Thread Jean Charles Delépine 


Hello,

I'm using debian's cyrus 2.5.10 on a big installation for my students.  
On 26 Jully /run/cyrus, a tmpfs, became full

and cyrus start generate many such error :

2017-07-26T18:11:24.268202+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: autocreateinbox: User d21702882, INBOX was su

ccessfully created
2017-07-26T18:11:24.316643+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: autocreateinbox: User d21702882, subfolder Tr

ash creation succeeded.
2017-07-26T18:11:24.322689+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: autocreateinbox: User d21702882, subscription

   to Trash succeeded
2017-07-26T18:11:24.367002+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: autocreateinbox: User d21702882, subfolder Te

mplates creation succeeded.
2017-07-26T18:11:24.368849+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: autocreateinbox: User d21702882, subscription

   to Templates succeeded
2017-07-26T18:11:24.416869+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: autocreateinbox: User d21702882, subfolder Se

nt creation succeeded.
2017-07-26T18:11:24.418801+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: autocreateinbox: User d21702882, subscription

   to Sent succeeded
2017-07-26T18:11:24.420601+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: autocreateinbox: User d21702882, subfolder Dr

afts creation failed. System I/O error
2017-07-26T18:11:24.422464+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: autocreateinbox: User d21702882, subfolder sp

am creation failed. System I/O error
2017-07-26T18:11:24.422472+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: User d21702882, Inbox subfolders, created 3,

subscribed 3
2017-07-26T18:11:24.422487+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: created proc directory
2017-07-26T18:11:24.422520+02:00 cyrus-backend-etud-01  
cyrus/imap[22644]: IOERROR: creating /run/cyrus/proc/22644.new: No  
space left on device


At this point cyrus can't anymore start any new process.

The server has been reboot on July 30 but cyrus doesn't want to start  
anymore :


2017-07-30T11:30:19.550254+02:00 cyrus-backend-etud-01  
cyrus/ctl_cyrusdb[2062]: skiplist: clean shutdown file missing,  
updating recovery stamp
2017-07-30T11:30:19.550695+02:00 cyrus-backend-etud-01  
cyrus/ctl_cyrusdb[2062]: recovering cyrus databases
2017-07-30T11:30:56.139131+02:00 cyrus-backend-etud-01  
cyrus/ctl_cyrusdb[2062]: done recovering cyrus databases
2017-07-30T11:31:57.976574+02:00 cyrus-backend-etud-01  
cyrus/master[2045]: process type:START name:mupdatepush  
path:/usr/sbin/cyrus age:0.000s pid:2432 signaled to death by signal  
11 (Segmentation fault)
2017-07-30T11:31:57.976583+02:00 cyrus-backend-etud-01  
cyrus/master[2045]: can't run startup
2017-07-30T11:31:57.976586+02:00 cyrus-backend-etud-01  
cyrus/master[2045]: exiting


Back from hollidays I've tried serveral things :

- /run/cyrus size has been double sized.
- cyrus has been upgraded from 2.5.8 to 2.5.10
- mailboxes.db has been converted to flat from twoskip with no  
success (still signal 11 on ctl_mboxlist -d and ctl_mboxlist -m).

- reconstruct has been used on all mailboxes

flat mailboxes.db has 313716 lines

last lines of strace ctl_mboxlist -d :

stat("/var/lib/cyrus/mailboxes.db", {st_mode=S_IFREG|0600,  
st_size=37058416, ...}) = 0

fcntl(6, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0
fcntl(6, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0
fstat(6, {st_mode=S_IFREG|0600, st_size=37058416, ...}) = 0
stat("/var/lib/cyrus/mailboxes.db", {st_mode=S_IFREG|0600,  
st_size=37058416, ...}) = 0

fcntl(6, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x1c} ---
+++ killed by SIGSEGV +++

I don't know anymore what to do...

Sincerly,
Jean Charles Delépine



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

setting acl on autocreate folders

2016-06-22 Thread Jean Charles Delépine via Info-cyrus 
Hello,

I'm playing with autocreate mailboxes but I can't find a way to set
extraneous acl on the created mailboxes.

My users intensively use plussed addresses and they want those plussed
mail to be delivered in the correct folder.

This, to be achieved, needs the acl anyone:p be set on the INBOX (that will 
be inherited by its subfolders on creation).

defaultacl is only for non users mailboxes
implicit_owner_rights is only for owner acl

So, is there a way to automatically set acl anyone:p on newly created
user mailboxes ? 

Sincerly,
 Jean Charles Delépine

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: Problems with murder upgrade from 2.2.13 to 2.5.8

2016-06-06 Thread Jean Charles Delépine via Info-cyrus 


Quoting Mathieu Pellieux via Info-cyrus :


Hello,

Aren't you missing the folowwing ACLs? (since cyrus 2.3 at least)

k: The ACI subject has the right to CREATE a new folder if the /k/  
<http://www.cyrusimap.org/%7Evanmeeuwen/imap/admin/access-control/rights-reference.html#imap-admin-access-control-right-k> right exists on the parent folder of the folder to be  
created.
x: Use the /x/  
<http://www.cyrusimap.org/%7Evanmeeuwen/imap/admin/access-control/rights-reference.html#imap-admin-access-control-right-x> right to indicate the ACI subject has the right to DELETE the folder on which the ACL is set, as opposed to the now obsolete /c/ <http://www.cyrusimap.org/%7Evanmeeuwen/imap/admin/access-control/rights-reference.html#imap-admin-access-control-right-c> right or /d/ <http://www.cyrusimap.org/%7Evanmeeuwen/imap/admin/access-control/rights-reference.html#imap-admin-access-control-right-d>  
right.
t: The ACI subject is allowed to delete messages from this folder,  
meaning that the ACI subject is allowed to flag messages as \\Deleted.
e: The ACI subject is allowed to expunge messages in this folder,  
meaning the ACI subject has the right to remove all messages that  
have been flagged as \\Deleted from all visibility.


Right, I should have a look to that, indeed. But after the upgrade.

My 2.2 backends don't accept those acl for the moment. And my 2.2  
frontends work

fine with the upgraded one, and those, untouch by upgrade, acl.

Anyway, I should have, better, read the docs :
https://cyrusimap.org/imap/release-notes/2.5/x/2.5.0.html :

" Cyrus IMAP Murder Topologies

Environments that run a Cyrus IMAP Murder topology will want to upgrade
their backends before they upgrade their frontends. See Task #16 for
details. "

Task #16 isn't relevant to my particular problem but the doc says I should
wait backends upgrade before upgrading frontends. I will wait.
And submailboxes creation works fine from 2.2 frontends to 2.5 backends.


Ps: I had a class with you in 2005 (first ISRAD prom)


Great! Good prom. Nice memories.

Thanks for your answer.



Regards,

On 06/06/2016 15:49, Jean Charles Delépine via Info-cyrus wrote:

Hello,

I'm on the way to make a big (late) upgrade.

My murder config is composed of 16 1To backends. I can't upgrade
all of them simultaneously. So I planed to :

  - upgrade mupdate server (make a new one, and update frontend's and
backend's conf)
  - replace frontends with upgraded one's
  - upgrade backends one after the other, nightly, on serveral night

mupdate server upgrade is ok. But I have problems with 2.5 frontends and 2.2
backends interaction. All seems fine (no error), but users can't  
create new sub

mailboxes (admin can create mailboxes and sub mailboxes) :

loggued as mailbox owner :
imap-01> lam INBOX
delepine lrswipcda
anyone p
imap-01> cm INBOX.hop
createmailbox: Permission denied

My tests say that, whichever mupdate server version :
  Frontend 2.2 can create 2.2 mailboxes and 2.5 mailboxes
  Frontend 2.5 can't create 2.2 mailboxes but can create 2.5 mailboxes

All others tested features work.

The 2.2 is using saslauthd + pam_ldap for authentification. The 2.5  
is using either

ldapdb or saslauthd + ptoader and ldap.

With or without
  suppress_capabilities: ESEARCH QRESYNC XLIST LIST-EXTENDED WITHIN
on 2.5 frontends.

2 questions :
  - do you have an idea why users can't create submailboxes on 2.2
backends with 2.5 frontends ? Is there any acl new option I
miss ? ...
  - what are the risks if I wait for all backends to migrate before
using 2.5 frontends ? My option with this problem. I didn't find
any problem... but surely, if there's one, my users will find it.

Options that might be relevant :
On backends :
  proxyservers: proxy
  proxy_authname: proxy

On frontends:
  proxy_authname: proxy
  proxy_password: <>
  proxyd_allow_status_referral: 0
  proxyd_disable_mailbox_referrals: 1

backends are in an internal non routable network.

Sincerly,
  Jean Charles Delépine

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


--
Mathieu Pellieux 
Administrateur Systèmes
sysadmin 
01.73.02.75.01





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

Problems with murder upgrade from 2.2.13 to 2.5.8

2016-06-06 Thread Jean Charles Delépine via Info-cyrus 
Hello,

I'm on the way to make a big (late) upgrade. 

My murder config is composed of 16 1To backends. I can't upgrade 
all of them simultaneously. So I planed to :

  - upgrade mupdate server (make a new one, and update frontend's and 
backend's conf)
  - replace frontends with upgraded one's
  - upgrade backends one after the other, nightly, on serveral night

mupdate server upgrade is ok. But I have problems with 2.5 frontends and 2.2
backends interaction. All seems fine (no error), but users can't create new sub 
mailboxes (admin can create mailboxes and sub mailboxes) :

loggued as mailbox owner :
imap-01> lam INBOX
delepine lrswipcda
anyone p
imap-01> cm INBOX.hop
createmailbox: Permission denied

My tests say that, whichever mupdate server version :
  Frontend 2.2 can create 2.2 mailboxes and 2.5 mailboxes
  Frontend 2.5 can't create 2.2 mailboxes but can create 2.5 mailboxes

All others tested features work.

The 2.2 is using saslauthd + pam_ldap for authentification. The 2.5 is using 
either
ldapdb or saslauthd + ptoader and ldap.

With or without 
  suppress_capabilities: ESEARCH QRESYNC XLIST LIST-EXTENDED WITHIN
on 2.5 frontends.

2 questions :
  - do you have an idea why users can't create submailboxes on 2.2
backends with 2.5 frontends ? Is there any acl new option I 
miss ? ...
  - what are the risks if I wait for all backends to migrate before
using 2.5 frontends ? My option with this problem. I didn't find
any problem... but surely, if there's one, my users will find it.

Options that might be relevant :
On backends :
  proxyservers: proxy
  proxy_authname: proxy

On frontends:
  proxy_authname: proxy
  proxy_password: <>
  proxyd_allow_status_referral: 0
  proxyd_disable_mailbox_referrals: 1

backends are in an internal non routable network.

Sincerly,
  Jean Charles Delépine

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