RE: Missing Email & Folders
> If you suspect this is due to a client related problem, you could > enable telemetry logging to find out who/what is causeing the emails to go missing. > > https://www.cyrusimap.org/imap/reference/faqs/o-telemetry.html Good idea will turn this on. > > If the purpose is to (mostly) copy emails into the folder and rarely > delete, you could restrict delete access to a specific account via ACL. > > https://www.cyrusimap.org/imap/reference/admin/access-control/rights- > reference.html Believe it is setup like this, been awhile since I did it. Will confirm. Also forgot to say the one account is ~90GB if that makes any difference... -Bob (sent twice) 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
Missing Email & Folders
Hello All, Have a few weird situations that I have been unable to find solutions to. Server: CentOS release 6.x cyrus-imapd-2.4.17-6.el5.src.rpm (Simon Matter) Client: Outlook 2013 Our client is using Cyrus to store related emails for their clients. The server does not actually receive mail, it is placed (copied) there. Approximately eight clients connect to "one" Cyrus account. When an email comes in for client X the user will find the appropriate imap folder and copy it to it. If the folder does exist it is created. Issue One: Randomly the server side imap folder is empty. Client imap folder has what was supposed to be on the server but it is not. The copy of the email appears to have been successful. Issue Two: Randomly computers will not see newly created imap folders from other users. Regardless of how we attempt to get the folder in the imap list we have to recreate the account. My assumption is that this is most likely due to imap support in Outlook and not Cyrus. Wanting to know if anyone has seen anything like this and if a solution was found. Thanks in advance. -Bob PS Have been on this mailing list for almost 20 years (since v1.6 I believe). Can say it is one of the best mailing lists I have been on. Never ceases to amaze me the quality of feedback and support provided. 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: Vanishing quota information
Do you still have the user folder with their emails? I have seen this as well on 2.1.15, although not as frequently as your seeing. We have about 800 users and every so often a client does not have any quota information when they view the account in our Client Interface. When we check further their email directory is just gone. We just wrote it off as user error because there was not rhyme or reason for it happening (that we could see). Is that similar to what you are seeing? -Bob > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Simon Matter > Sent: Tuesday, June 29, 2004 6:47 AM > To: Ken Murchison > Cc: [EMAIL PROTECTED] > Subject: Re: Vanishing quota information > > > > Simon Matter wrote: > > > >>>I have a new problem with vanishing quota. At least I didn't notice it > >>>earlier. The situation is that we have quota for all users but suddenly > >>>quota for some users are lost, the user. file in the quota dir just > >>>doesn't exist anymore. We are using legacy_quota, so nothing new here. > >>>This is on cyrus-imapd-2.2.6. > >> > >> > >> I can't believe nobody else has this problem. I have it on > more than one > >> server now and it keeps going on. The thing is that my > cyrus-imapd 2.2.6 > >> seems to forget quota of about 6 users daily with a ~2000 userbase. > >> > >> I'm using the following hack to detect missing quota. > > > > > > Is there a user..NEW file for these users? > > No, just nothing. > > > > > -- > > Kenneth Murchison Oceana Matrix Ltd. > > Software Engineer 21 Princeton Place > > 716-662-8973 x26 Orchard Park, NY 14127 > > --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp > > > > > > > --- > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
RE: deliver -q won't ignore quotas
So the "IGNOREQUOTA" does not pertain to my situation? I am seeing the same
that Jamie was, in that our system messages for over quota are getting
bounced because they are over quota. For example when our quota checker ran
this morning we got:
The original message was received at Tue, 15 Jun 2004 23:00:05 -0500 (CDT)
from localhost.rolet.com [127.0.0.1]
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
(reason: 552 5.2.2 Over quota)
How would we address this situation using the "-q"?
Thanks,
-Bob
> -Original Message-
> From: Ken Murchison [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 15, 2004 8:55 PM
> To: Robert Covell
> Cc: Jamie Davey; [EMAIL PROTECTED]
> Subject: Re: deliver -q won't ignore quotas
>
>
> Robert Covell wrote:
>
> > We are doing something similar but opening deliver a bit
> different (with the
> > user name and -q). Before we put this in production would the
> following be
> > correct (the previous open of deliver is commented out):
>
> No, the commented out version is correct. The difference being that
> Jamie is using the '-l' option which means that the client is speaking
> LMTP directly (with deliver being a middle-man). In your case, you're
> just telling deliver what to do and it creates the LMTP session with the
> appropriate commands/arguments.
>
>
> >
> > //$MP = "/usr/local/cyrus/bin/deliver -q $user";
> > $MP = "/usr/local/cyrus/bin/deliver $user IGNOREQUOTA";
> >
> > $fp = popen($MP,"w");
> > fputs($fp, $toheader);
> > fputs($fp, $fromheader);
> > fputs($fp, $replytoheader);
> > fputs($fp, $dateheader);
> > fputs($fp, $subjectheader);
> > fputs($fp, "$message");
> > pclose($fp);
> >
> > Thanks,
> > Bob
> >
> >
> >>-Original Message-
> >>From: [EMAIL PROTECTED]
> >>[mailto:[EMAIL PROTECTED] Behalf Of Ken Murchison
> >>Sent: Wednesday, June 09, 2004 3:17 PM
> >>To: Jamie Davey
> >>Cc: [EMAIL PROTECTED]
> >>Subject: Re: deliver -q won't ignore quotas
> >>
> >>
> >>Jamie Davey wrote:
> >>
> >>
> >>>Hi all
> >>>
> >>>I am trying to get a script (derived from the archives of this list)
> >>>running that will deliver a warning mail to users who are in danger of
> >>>breaching / have breached their mailbox quota. The script
> >>
> >>determines the
> >>
> >>>users affected by running the quota command and then tries to send them
> >>>a mail using deliver with the -q directive to deliver regardless of
> >>>their quota usage. It works fine for users who are approaching their
> >>>full quota but not for those currently over it.
> >>>
> >>>I have run the script without the deliver portion and manually sent the
> >>>mails, again using "deliver -q -l" and get a "452 4.2.2 Over quota"
> >>>error which disregards the recipient. Is this a bug with
> >>
> >>deliver or am I
> >>
> >>>doing something wrong
> >>
> >>If you're going to speak LMTP directly (-l option), then no other
> >>options apply and you need to add the IGNOREQUOTA protocol element
> >>yourself (see below). Actually, if you're writing your own LMTP client,
> >>then talk to lmtpd directly instead of using deliver as a pass-through
> >>proxy.
> >>
> >>
> >>># Warning messages
> >>>if (@warn) {
> >>> open(DELIVER, "| $deliverprog -q -l");
> >>> print DELIVER "MAIL FROM:<[EMAIL PROTECTED]>\n";
> >>> foreach $warnuser (@warn) {
> >>> print DELIVER "RCPT TO:<$warnuser>\n";
> >>
> >>This should be "RCPT TO:<$warnuser> IGNOREQUOTA\n"
> >>
> >>
> >>
> >>> };
> >>> print DELIVER "DATA\n";
> >>> print DELIVER < >>
> >>--
> >>Kenneth Murchison Oceana Matrix Ltd.
> >>Software Engineer 21 Princeton Place
> >>716-662-8973 x26 Orchard Park, NY 14127
> >>--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
> >>---
> >>Cyrus Home Page: http://asg.web.cmu.edu/cyrus
> >>Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
> >>List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
> >>
> >
> >
> > ---
> > Cyrus Home Page: http://asg.web.cmu.edu/cyrus
> > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
> > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
> >
>
>
> --
> Kenneth Murchison Oceana Matrix Ltd.
> Software Engineer 21 Princeton Place
> 716-662-8973 x26 Orchard Park, NY 14127
> --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
>
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
RE: deliver -q won't ignore quotas
We are doing something similar but opening deliver a bit different (with the
user name and -q). Before we put this in production would the following be
correct (the previous open of deliver is commented out):
//$MP = "/usr/local/cyrus/bin/deliver -q $user";
$MP = "/usr/local/cyrus/bin/deliver $user IGNOREQUOTA";
$fp = popen($MP,"w");
fputs($fp, $toheader);
fputs($fp, $fromheader);
fputs($fp, $replytoheader);
fputs($fp, $dateheader);
fputs($fp, $subjectheader);
fputs($fp, "$message");
pclose($fp);
Thanks,
Bob
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Ken Murchison
> Sent: Wednesday, June 09, 2004 3:17 PM
> To: Jamie Davey
> Cc: [EMAIL PROTECTED]
> Subject: Re: deliver -q won't ignore quotas
>
>
> Jamie Davey wrote:
>
> > Hi all
> >
> > I am trying to get a script (derived from the archives of this list)
> > running that will deliver a warning mail to users who are in danger of
> > breaching / have breached their mailbox quota. The script
> determines the
> > users affected by running the quota command and then tries to send them
> > a mail using deliver with the -q directive to deliver regardless of
> > their quota usage. It works fine for users who are approaching their
> > full quota but not for those currently over it.
> >
> > I have run the script without the deliver portion and manually sent the
> > mails, again using "deliver -q -l" and get a "452 4.2.2 Over quota"
> > error which disregards the recipient. Is this a bug with
> deliver or am I
> > doing something wrong
>
> If you're going to speak LMTP directly (-l option), then no other
> options apply and you need to add the IGNOREQUOTA protocol element
> yourself (see below). Actually, if you're writing your own LMTP client,
> then talk to lmtpd directly instead of using deliver as a pass-through
> proxy.
>
> >
> > # Warning messages
> > if (@warn) {
> >open(DELIVER, "| $deliverprog -q -l");
> >print DELIVER "MAIL FROM:<[EMAIL PROTECTED]>\n";
> >foreach $warnuser (@warn) {
> >print DELIVER "RCPT TO:<$warnuser>\n";
>
> This should be "RCPT TO:<$warnuser> IGNOREQUOTA\n"
>
>
> >};
> >print DELIVER "DATA\n";
> >print DELIVER <
> --
> Kenneth Murchison Oceana Matrix Ltd.
> Software Engineer 21 Princeton Place
> 716-662-8973 x26 Orchard Park, NY 14127
> --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
> ---
> Cyrus Home Page: http://asg.web.cmu.edu/cyrus
> Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
RE: Shared sent-mail folder
Unfortunately we are not using Postfix. We are using sendmail. Does anyone know how to do this for specific domains in sendmail? -Bob > -Original Message- > From: Scott Russell [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 01, 2004 9:37 AM > To: Robert Covell > Cc: Info-Cyrus > Subject: Re: Shared sent-mail folder > > > On Thu, 2004-04-01 at 10:21, Robert Covell wrote: > > We have a client that is wanting to track all incoming and > outgoing mail in > > his business for auditing purposes. We can do incoming mail by > dropping the > > message into two accounts (one for the original recip and the > catch-all). > > > > What we cannot figure out is how to catch outgoing mail. > > > > Or is there a way to collect sent-mail for users? > > At the MTA level Postfix will handle this. See "always_bcc" in man > pickup(8). > > Set your BCC address to deliver to an "exec account" which has a shared > mailbox that only certain people can read from. > > -- > Scott Russell <[EMAIL PROTECTED]> > Linux Technology Center System Admin > > > --- Home Page: http://asg.web.cmu.edu/cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Shared sent-mail folder
We have a client that is wanting to track all incoming and outgoing mail in his business for auditing purposes. We can do incoming mail by dropping the message into two accounts (one for the original recip and the catch-all). What we cannot figure out is how to catch outgoing mail. Should we use a shared sent-mail box. We could migrate their users to IMAP and have them share a user for sending out-going mail and point the setup to a folder on the server. Our problem with this is that we believe "sent-mail" folder is taken from the incoming setup and not the outgoing mail setup. What would be the best way to share a sent-mail folder? Or is there a way to collect sent-mail for users? Thanks, -Bob --- Home Page: http://asg.web.cmu.edu/cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
RE: Reconstructing A Single Mailbox
Thanks for the reply. We got it working after all. When we placed the old email in their box the owner was not set to cyrus, so it could not read anything. Changing them to cyrus:mail resolved the issue and let reconstruct do it's magic. -Bob > -Original Message- > From: Dave McMurtrie [mailto:[EMAIL PROTECTED] > Sent: Friday, February 06, 2004 10:15 AM > To: Robert Covell > Cc: Info-Cyrus > Subject: Re: Reconstructing A Single Mailbox > > > On Fri, 6 Feb 2004, Robert Covell wrote: > > > We have a client that deleted all their emails for about 10 employees > > (through an automated process). We have backups of their mail and are > > trying to use reconstruct to get their email back to them. When we do a > > reconstruct on one of their boxes it does nothing (that we can see): > > > > %./reconstruct user.the-user > > user.the-user > > % > > > > What is the best way to accomplish this? > > Using imap protocol (i.e. cyradm), create any mailboxes that were deleted. > After you create the mailboxes you can restore the mail to the filesystem, > then reconstruct the mailboxes. All should be well. We do this as a > matter of routine. > > Thanks, > > Dave > -- > Dave McMurtrie, Systems Programmer > University of Pittsburgh > Computing Services and Systems Development, > Development Services -- UNIX and VMS Services > 717P Cathedral of Learning > (412)-624-6413 > > PGP/GPG Key: http://www.pitt.edu/~dgm/gpgkey.asc.txt > > --- Home Page: http://asg.web.cmu.edu/cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Reconstructing A Single Mailbox
We have a client that deleted all their emails for about 10 employees (through an automated process). We have backups of their mail and are trying to use reconstruct to get their email back to them. When we do a reconstruct on one of their boxes it does nothing (that we can see): %./reconstruct user.the-user user.the-user % What is the best way to accomplish this? -Bob --- Home Page: http://asg.web.cmu.edu/cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
RE: postmaster mail
I too would be interested in the question about "abnormal amount of emails to postmaster". We get about 15K a day of these and just recently started to pipe them into /dev/null. It is more of a burden to delete them manually. Anyone else have high postmaster email counts? Sincerely, Robert T. Covell President / Owner Rolet Internet Services, LLC Web: www.rolet.com Email: [EMAIL PROTECTED] Phone: 816.471.1095 Fax: 816.471.3447 24x7: 816.210.7145 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Scott Adkins > Sent: Wednesday, January 21, 2004 1:38 PM > To: Cyrus Info Mailing List > Subject: postmaster mail > > > Okay, I thought I would pull from the wisdom from the group, but I hope it > isn't too far off topic. > > We have been using an alias for the root account to get all root destined > mail to the /var/spool/mail/root mailbox, bypassing the Cyrus system. > However, our system has grown significantly over the years and now we get > on average 25,000 messages a day to the root account alone. Basically, > we just fire up mailx and delete everything. If there is anything useful > in that mailbox, it is doubtful we would have ever found it anyways. > > So, today, I created the user.root mailbox and changed the alias so that > all the mail can go to it. I also created a postmaster subfolder and > directory the postmaster alias to send its mail to root+postmaster. It > all works... really works... :) > > It is clear that 99.9% of all our mail is postmaster mail. It looks like > it is mostly unknown user mails, over quota mails, connection refused or > deferred mails, etc. I know that there may be some important postmaster > mail that we should keep... obviously, we have been deleting stuff for a > long time, but it would be nice to not delete blindly and actually keep > the important messages we should be dealing with. Incidentally, in the > last 20 minutes, 300 messages came into the postmaster folder. > > So, the question is, do we just turn off postmaster mail altogether (is > that actually doable? maybe by setting PostmasterCopy to nothing?), or > do I somehow build an intelligent sieve script that throws away most the > stuff that we think are junk? > > What have you guys done? I am more interested in the larger email system, > ones receiving on the order of 500k+ messages a day. Is it abnormal to > see such a large volume of postmaster mail like this? Have any of you > developed a sieve script that would be useful to the Cyrus community as a > whole? > > Enquiring minds want to know! > > Thanks for any thoughts on the subject... > Scott > -- > +---+ > Scott W. Adkinshttp://www.cns.ohiou.edu/~sadkins/ >UNIX Systems Engineer mailto:[EMAIL PROTECTED] > ICQ 7626282 Work (740)593-9478 Fax (740)593-1944 > +---+ > PGP Public Key available at http://www.cns.ohiou.edu/~sadkins/pgp/
Opps-Made A Mistake
Yesterday we changed our backup script for Cyrus. When we zipped up the partition-default: /usr/cyrusmail we used a "move" switch instead of a "copy" switch. The system was essentially without a partition-default: for about 4 hours. We have unzipped everything and put it back but now some people cannot login via pop. I believe that imap is fine because clients that cannot login via pop can from webmail which is imap. Do we need to update something or reconstruct the mailboxes? Do the seen/unseen flags need to be restored? Not sure where to look because our logs don't show any errors. All the mail from 2 am was put in a sendmail queue and has since been delivered. None of the other config files were modified by the backup script, just the partition-default. Thanks, -Bob
RE: lmtp_overquota_perm_failure
We are using deliver only to notify them of being over quota. Everything else is coming in via sendmail. It does notify the sender of the user being over quota but the user still gets the email. Just wonder if anything else could be causing conflicting settings. btw: FreeBSD 4.8 sendmail-8.12.10 cyrus-imapd-2.1.15 cyrus-sasl-2.1.15 w/mysql auth Thanks -Bob > -Original Message- > From: Andrew Morgan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 04, 2003 11:20 AM > To: Robert Covell > Cc: Jernej Porenta; Info-Cyrus > Subject: RE: lmtp_overquota_perm_failure > > > > > On Tue, 4 Nov 2003, Robert Covell wrote: > > > Thanks for your reply. We do that now to let users know they are over > > quota. But we don't want messages delivered if they are over quota. We > > don't even want them to be queued on the system, just bounce back to the > > sender. Any experience if the lmtp_overquota_perm_failure > performs this or > > do we need another config option? > > > > Thanks again. > > > > -Bob > > If you have lmtp_overquota_perm_failure set to "no" (the default I think), > then mail will be refused for that user with a temporary error. The MTA > will continue trying to deliver the mail until it gives up (most MTAs > default to 5 days). This allows someone to go over their quota > temporarily and still have time to fix the problem and receive the backlog > of mail waiting for them in the mail queue. > > If you have lmtp_overquota_perm_failure set to "yes", mail will bounce > back to sender as undeliverable right away, instead of sitting in the > MTA's mail queue for 5 days. > > If you have mail being delivered even though the user is over their quota, > then I don't think lmtp_overquota_perm_failure will help one or the other. > Are you sure you aren't using cyrus' deliver program with: > > -q Deliver message even when receiving mailbox is over quota. > > > Andy > >
RE: lmtp_overquota_perm_failure
Thanks for your reply. We do that now to let users know they are over quota. But we don't want messages delivered if they are over quota. We don't even want them to be queued on the system, just bounce back to the sender. Any experience if the lmtp_overquota_perm_failure performs this or do we need another config option? Thanks again. -Bob > -Original Message- > From: Jernej Porenta [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 04, 2003 10:18 AM > To: Robert Covell > Subject: Re: lmtp_overquota_perm_failure > > > Hello! > > If you are using deliver command to deliver mails, I think that there is a > switch that allows deliver to deliver mail to mailbox even if it is over > quota.. > > I dont know the switch but check them out... > > Greetz, Jernej > > On Tue, 4 Nov 2003, Robert Covell wrote: > > > Is this the config option to stop emails from being delivered > if they are > > over quota? > > > > We have it set to: > > > > lmtp_overquota_perm_failure: yes > > > > I thought I read another post regarding that it does just this. > > > > The system does return a over quota message to the sender but > the messages > > still get through. > > > > Is there something else I should look at to stop delivery, or a > conflicting > > config option? > > > > Thanks, > > > > -Bob > > > > > >
lmtp_overquota_perm_failure
Is this the config option to stop emails from being delivered if they are over quota? We have it set to: lmtp_overquota_perm_failure: yes I thought I read another post regarding that it does just this. The system does return a over quota message to the sender but the messages still get through. Is there something else I should look at to stop delivery, or a conflicting config option? Thanks, -Bob
DBERROR db3: 4 lockers
We are in the process of replacing our 1.5.24 Cyrus box with a new 2.1.15 box. After we got everything setup, tested and stabilized we rebooted the box and got: Sep 25 16:12:09 mail1b ctl_cyrusdb[152]: checkpointing cyrus databases Sep 25 16:12:09 mail1b lmtpd[155]: DBERROR db3: 4 lockers Sep 25 16:12:09 mail1b ctl_cyrusdb[152]: done checkpointing cyrus databases Sep 25 16:12:09 mail1b imapd[156]: DBERROR db3: 4 lockers Sep 25 16:12:11 mail1b imapd[172]: DBERROR db3: 4 lockers I saw the post on this: http://www.irbs.net/internet/info-cyrus/0208/0466.html And the other recommended post: http://asg.web.cmu.edu/archive/message.php?mailbox=archive.cyrus-sasl&msg=23 11 Is the recommendation of using skiplist with mailboxes.db still valid? Or do we need to shutdown the cyrus server before we shutdown? If shutting it down before a reboot what is the preferred method? We are still in a position to change the format if necessary before migrating 800+ users... Sincerely, Robert T. Covell President / Owner Rolet Internet Services, LLC Web: www.rolet.com Email: [EMAIL PROTECTED] Phone: 816.471.1095 Fax: 816.471.3447 24x7: 816.210.7145
Migration from 1.5.24 to 2.1.15
We are about to migrate 700+ users from 1.5.24 to 2.1.15 and wanted to verify that the previous post still pertains to our situation on 2.1.15 rather than 2.0.16. Our setup was and will be: Old server: - FreeBSD 4.1.1 - Cyrus IMAPd 1.5.24 - pwcheck_mysql-0.1 (for all access) New server: - FreeBSD 4.8 or 5.1 (maybe 5.1) - Cyrus IMAPd 2.1.15 - SASL 2.1.15 We are not sure how to have the new system check for passwords via mysql. Anyone have information regarding this in 2.1.15? Thanks, -Bob Previous Post Hi everyone, I'm posting here a kind of step by step guide for the most newbie (like me :-) for the migration of user mailbox from Cyrus 1.5.14 to 2.0.16. This guide worked fine in my configuration: Old server: - Linux SUSe 7.0 - Cyrus IMAPd 1.5.14 New server: - Linux SUSe 7.0 - Cyrus IMAPd 2.0.16 - SASL 1.5.24 - Berkeley DB3.2.9 I'm assuming to have a backup file of mailbox in the old format that includes everything under /var/imap & /var/spool/imap (imapbackup.tar.gz) # 1. Delete the actual spool dir: rm -r /var/spool/imap/* rm -r /var/imap/* # 2. Untar the backup file: (imapbackup.tar.gz) mkdir /tmp/backimap cd /tmp/backimap tar zxf imapbackup.tar.gz # 3. Move the backup to the spool dir: cd imap mv * /var/imap cd ../spool/imap mv * /var/spool/imap # 4. Create the rest of directories: /usr/cyrus/tools/mkimap # 5. Check permission chown -R cyrus:mail /var/spool/imap/* chown -R cyrus:mail /var/imap/* # 6. Reconstruct the mailboxes: su - cyrus /usr/cyrus/tools/undohash /usr/cyrus/tools/dohash cd /var/imap /usr/cyrus/bin/ctl_mboxlist -u < mailboxes cd /var/spool/imap /usr/cyrus/bin/reconstruct -r user.* # 7. Delete the delivered.db: mv /var/imap/delivered.db /var/imap/_delivered.db # 8. Delete the temp dir exit rm -rf /tmp/backimap # 9. Startup the sysem: /usr/cyrus/bin/master &
