Re: sieve runtime error Fileinto: Permission denied

2016-05-23 Thread Jack Snodgrass via Info-cyrus
file permissions like right.. acl permissions look right... are you 
running with selinux set to something other than disabled? Just a 
guess... but everything else looks ok.


jack



On 05/23/2016 07:47 AM, Sundeep Singh Nanuwa via Info-cyrus wrote:



On 23/05/16 13:35, Bron Gondwana via Info-cyrus wrote:

You need to have "anyone p" acl to fileinto anything other than inbox.

That didn't work unfortunately.

Thanks



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



--
*jack* - Southlake Texas - http://mylinuxguy.net 
 - *817-601-7338*

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

what's the most efficient way to check multiple user's unseen message counts?

2016-05-06 Thread Jack Snodgrass via Info-cyrus
I have 100+ users that login to a web page to do their daily task. They 
stay on that page all day.  We have a 'unread' message count for each 
user's email account and some other shared accounts ( fax, 
customer-service, etc). Every 60 seconds, the web server does a php 
imap_open / imap_status  / imap _close for each user ( and the shared 
accounts ) and updates the web page with their unseen message count.


This has always struck me as inefficient We generate a lot of log 
messages constantly just to keep track of the unseen message count.


Is there a better way to handle this other than don't do this or do this 
less often?


We're using cyrus 2.4.  ( recently migrated from 2.2 )

I am not opposed to running a shell script on the mail server and 
returning the unseen counts for all users via a file system check or db 
read -vs- imap api.


I've thought of using imap idle but when we looked at that with cyrus 
2.2, it did not work for us might look at that again.


Just wanted to know if anyone had any thoughts on this.


Thanks - jack

--
*jack* - Southlake Texas - http://mylinuxguy.net 
 - *817-601-7338*

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: Migrating IMAP from Cyrus v2.2.13 to Cyrus v2.4.17

2016-04-08 Thread Jack Snodgrass via Info-cyrus
someone posted ( thanks ) a script with some commands that they used to 
migrate their cyrus imap data.


In there they had:

# move over all seen, sub files
rsync -Havz --delete-after -e ssh cyrus@oldserver:/var/lib/imap/user/ 
/var/lib/imap/user


# move over quota files
rsync -Havz --delete-after -e ssh cyrus@oldserver:/var/lib/imap/quota/ 
/var/lib/imap/quota



which I'd LOVE to do.. but I don't have files in those directories. I 
know what I have 'seen' flags set.. but not sure where  / how they are 
stored with Cyrus V2.2.x.


I have:
find  /var/lib/cyrus/user
/var/lib/cyrus/user
/var/lib/cyrus/user/c
/var/lib/cyrus/user/d
/var/lib/cyrus/user/w
.
.
.
.
but no files in those empty dirs.

what am I looking for EXACTLY in those dirs.. maybe we have them 
someplace else.

We don't have anything in /var/lib/imap.. we use /var/lib/cyrus


Thanks - jack





--
*jack* - Southlake Texas - http://mylinuxguy.net 
 - *817-601-7338*

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: Migrating IMAP from Cyrus v2.2.13 to Cyrus v2.4.17

2016-04-06 Thread Jack Snodgrass via Info-cyrus

I read that.. but after 8 hours of trying to get it going I gave up on it.

I the debian 8 / Cyrus 2.5 stuff did not want to process the cyrus 2.4 
db files from debian 6.


You can say pretty words like: "may require support for whichever 
backend you were using" but if all you have is access to apt-get and you 
have two systems that are YEARS apart in what they have setup.. how do 
you do this?  Tell me the apt-get install command to run so that  
ctl_cyrusdb -r works or it's just words.



jack



On 04/06/2016 01:32 PM, Dan White wrote:

On 04/06/16 13:20 -0500, Jack Snodgrass via Info-cyrus wrote:
Is there a documented process for taking a system from: Cyrus v2.2.13 
to Cyrus v2.4.17



I have rsync'd the mail between the two systems.

/usr/lib/cyrus/bin/reconstruct did NOT magically convert the system 
from the old to the new.



/usr/lib/cyrus/bin/reconstruct -G -f



The 'seen' flags and probably some other flags / acls are not working.


Check the upgrade instructions here:

https://cyrusimap.org/docs/cyrus-imapd/2.5.3/install-upgrade.php

'ctl_cyrusdb -r' may require support for whichever backend you were using
on the older version (on the new system), such as a legacy berkeleydb
version.



--
*jack* - Southlake Texas - http://mylinuxguy.net 
<http://mylinuxguy.net/> - *817-601-7338*

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: Migrating IMAP from Cyrus v2.2.13 to Cyrus v2.4.17

2016-04-06 Thread Jack Snodgrass via Info-cyrus
Tried to go to 2.5 and had more serious issues than going to 2.4.  From 
the top of my head I don't recall what it was...
I've still got the 2.5 binaries laying around.  Do you have a successful 
migration path from 2.2 to 2.5 that I can do? I've been told that the 
'seen' flags is a big deal for my peeps. I can ( I think... if I have to 
) write a script that checks the seen flags of all the mail on the old 
system and sets it on the new system... but I am hoping to NOT have to 
do that. I have 185Gig of mail files I have to process and if a 
migration script would do this for me, that's the path I'd like to take.



we are aiming for 0  / minimal down time and users changes. I want to 
get the mail setup on the new server and just change the ip address of 
the new server to the old server's ip address. Hoping to have minimal 
impact to the users.



jack



On 04/06/2016 01:25 PM, k...@rice.edu wrote:

On Wed, Apr 06, 2016 at 01:20:13PM -0500, Jack Snodgrass via Info-cyrus wrote:

Is there a documented process for taking a system from: Cyrus
v2.2.13 to Cyrus v2.4.17

I have an old debian box with Cyurs v2.2.13.

I have a new debian box with Cyrus v2.4.17

Is there a documented / official process for migrating mail like
this?  I could not find one.


I have rsync'd the mail between the two systems.

/usr/lib/cyrus/bin/reconstruct did NOT magically convert the system
from the old to the new.

I wrote a script to create the mailboxes and their folders.

After that ( or maybe before... ) I ran:

/usr/lib/cyrus/bin/reconstruct -G -f

and I think that has me close to where I want to be. I have mail
boxes and folders and test users can view their mail.

The 'seen' flags and probably some other flags / acls are not working.


Isn't there a simple upgrade / migrate script path that I am failing
to find?


jack


Hi Jack,

Why are you migrating to v2.5.x? It has been out for quite a while now?
If you have a lot of users, the 2.2 -> 2.4 upgrade can be painful I/O-wise.

Regards,
Ken



--
*jack* - Southlake Texas - http://mylinuxguy.net 
<http://mylinuxguy.net/> - *817-601-7338*

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

Migrating IMAP from Cyrus v2.2.13 to Cyrus v2.4.17

2016-04-06 Thread Jack Snodgrass via Info-cyrus
Is there a documented process for taking a system from: Cyrus v2.2.13 to 
Cyrus v2.4.17


I have an old debian box with Cyurs v2.2.13.

I have a new debian box with Cyrus v2.4.17

Is there a documented / official process for migrating mail like this?  
I could not find one.



I have rsync'd the mail between the two systems.

/usr/lib/cyrus/bin/reconstruct did NOT magically convert the system from 
the old to the new.


I wrote a script to create the mailboxes and their folders.

After that ( or maybe before... ) I ran:

/usr/lib/cyrus/bin/reconstruct -G -f

and I think that has me close to where I want to be. I have mail boxes 
and folders and test users can view their mail.


The 'seen' flags and probably some other flags / acls are not working.


Isn't there a simple upgrade / migrate script path that I am failing to 
find?



jack


--
*jack* - Southlake Texas - http://mylinuxguy.net 
 - *817-601-7338*

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 Murder with different Cyrus IMAP Server versions

2016-03-02 Thread Jack Snodgrass via Info-cyrus


I have a older Cyrus 2.2 version setup and running in production.

I want to move to a newer Cyrus 2.4 system with minimal downtime.

The goal is 1) limit down time and 2) keep the SAME ip address for the 
users imap configs.


I can convert my existing Cyrus 2.2 ( Debian v6 ) to Cyrus 2.4 ( Debian 
v8 ) but will be down around 8 ( at least ) for the two debian upgrades 
and converting 200gig of Cyrus 2.2 mail to Cyrus 2.4 - indexes and what not.


I was thinking.. maybe another approach would be to setup Cyrus Murder ( 
2.2 ) on my existing Cyrus 2.2 box and connect it up with a new Cyrus 
2.4 server ( on a new Debian v8 box ) and just move mail accounts over 
one at a time until all of the mail was off of the old box.  Once all of 
the mail was off of the old Cyrus 2.2 box, I could then upgrade that to 
debian v8 and Cyrus 2.4 and then have 2 systems that the mail could be 
split between.


Can I run a Murder 2.2 server and have it talk with a Cyrus 2.4 IMAP box 
or do the versions have to be the same?


Thanks - jack

--
*jack* - Southlake Texas - http://mylinuxguy.net 

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