Subject: Re: Quota notification problem - msg#00244

Previous Message by Date: click to view message preview

Re: migrating accounts - Read status and Subscriptions lost after mboxutil -r

Jesse Thompson wrote: Kelly, Those are store-wide files. We aren't moving all of the accounts at the same time. Then imsbackup/imsrestore would be a better option. When will the bug be fixed? The customer who reported it was able to workaround it. It is not yet fixed. If you cannot workaround this, you should open a support case. Kelly Can we migrate and just not do any partition moves until the bug is fixed, or will we have to wait for the bugfix before we start migrating accounts? Jesse Kelly Caudill wrote: bug 6410419 : mboxutil -r loses peruser info and store.usr WorkAround: do not lose the mboxlist databases during the migration. did you not copy over the mboxlist files as well? Kelly Jesse Thompson wrote: We are testing our process to migrate users off of our 5.2 stores and onto our new JES4 stores. We're copying the mail over using cpio over nfs mounts. The mail seems to migrate just fine as long as we are sure that the user isn't logged in and that a peruser checkpoint has run since the user has logged out (so that read status and folder subscriptions are retained). After the mail is copied we run reconstruct -p <partition> -u <user> -m, reconstruct -q and reconstruct -r user/<user>/INBOX on the new store. The user is able to log in successfully and read status and folder subscriptions are retained correctly. The problem we see is that the read status and folder subscriptions are lost when we attempt to move the user to a new partition via mboxutil -r on either the source (prior to the migration) or destination store. We tried waiting for a peruser checkpoint and restarting the JES store. It also doesn't seem to matter how long we wait. The only solution we have found is to log into the account, IMAP SELECT each folder, and wait for another checkpoint to run before using mboxutil -r to move the account to a new partition. We'd prefer not to have to do this in our migration process. Does anyone have ideas what the IMAP SELECT and peruser checkpoint are doing and how we could replicate that process without actually running those actions. Our suspicion is that there's some synchronization happening between the store's databases and the user's files (store.idx, store.sub, store.usr). Is there a configuration setting or command to make this happen "at will"? Jesse

Next Message by Date: click to view message preview

Re: imsimta process_held in JES4?

Kristin Hubner wrote: On Aug 21, 2006, at 1:23 PM, Jesse Thompson wrote: Kristin Hubner wrote: On Aug 21, 2006, at 9:22 AM, Jesse Thompson wrote: On our 5.2 stores we run this command to process queued messages after an account rename. imsimta process_held -uid=old_uid -domain=wisc.edu -new_uid=new_uid -v The process_held option isn't available on our JES4 stores. What is the best way to process queued messages for renamed users? Jesse After changing the user's mailUserStatus back to active (or the mailDomainStatus, if you'd set the entire domain to hold messages), go into imsimta qm, find the relevant .HELD files in the hold channel (e.g., "dir -held -to=<address> hold") and then use the "release" command to release them. But that doesn't rewrite the recipient address. The command (and you) don't need to change the address -- that will happen automatically once the (no longer held status) address is processed. The messages going to the hold channel (due to user or domain status of "held") are still in their more-or-less original form. It isn't until a user/domain status is "active" -- isn't until after the "release" -- that the processing of the "mailbox" delivery option occurs, with its resulting transformation of address into a form incorporating the uid. Sounds good. We'll give it a shot. Thanks for the help. Jesse Regards, Kristin Jesse Regards, Kristin smime.p7s Description: S/MIME Cryptographic Signature

Previous Message by Thread: click to view message preview

Quota notification problem

Hi, I just setup the quota notification for the messaging server but the users did not receive the warning message when they pass the 90% of quota usage and I see the following message in the imta log file: Store Error: Unable to deliver overquota notification to user-hcDgGtZH8xNBDgjK7y7TUQ@xxxxxxxxxxxxxxxx my configutil parameters are like this: local.store.overquotastatus = off store.defaultmailboxquota = 20971520 store.defaultmessagequota = -1 store.quotaenforcement = on store.quotaexceededmsginterval = 2 store.quotaexceededmsg="Subject: warning, overquota utilization$$Test message" store.quotagraceperiod = 24 store.quotanotification = on store.quotawarn = 90 I'm using JES2005Q4: Sun Java(tm) System Messaging Server 6.2-6.01 (built Apr 3 2006) libimta.so 6.2-6.01 (built 11:20:35, Apr 3 2006) Any Idea? Thanks in advanced. Regards -- Osvaldo Fonseca

Next Message by Thread: click to view message preview

Re: Quota notification problem

Thanks Kristin for your answer. yes I saw several messages like this: imta.25.1155933028:[18/Aug/2006:15:53:45 -0500] jes ims_master[4522]: General Error: Failed to parse message for lcastillo-hcDgGtZH8xPowKkBSvOlow@xxxxxxxxxxxxxxxx Please check (lang=en) configuration option I don't know if this is useful, but here there are the steps that I did to create the Quota Notification Message: I went to the Messaging Console --> Configuration --> Message Store --> Quota and created a Message to send to the user when quota limit is exceeded in Spanish. And check the store.quotaexceededmsg: store.quotaexceededmsg;lang-es = "Subject: Aviso, La utilizacion de su buzon sobrepasa el limite permitido$$Sobre utilizacion de su buzon, por favor libere espacio para que pueda recibir correos." Any idea? Thanks in advanced. On 8/21/06, Kristin Hubner <kristin.hubner-xsfywfwIY+M@xxxxxxxxxxxxxxxx> wrote: On Aug 21, 2006, at 11:29 AM, Osvaldo Fonseca wrote: > Hi, > > I just setup the quota notification for the messaging server but the > users did not receive the warning message when they pass the 90% of > quota usage and I see the following message in the imta log file: > > Store Error: Unable to deliver overquota notification to > user-hcDgGtZH8xNBDgjK7y7TUQ@xxxxxxxxxxxxxxxx Did you get any other errors -- say "Couldn't get preferred language for domain <domain>: <error>" or "Failed to parse message for <userid>. Please check (lang=<lang>) configuration option" or anything else, right before the error you quote? Conditions such that the overquota message can't be delivered would tend to result in a prior error message (for example, those above) with more details about the underlying problem -- though in some cases you might need a higher level of output enabled. If you don't seem to be seeing any other, earlier error message, then I recommend that you set logfile.imta.loglevel down to at least Information, if not Debug, and then try again. Regards, Kristin > > my configutil parameters are like this: > > local.store.overquotastatus = off > store.defaultmailboxquota = 20971520 > store.defaultmessagequota = -1 > store.quotaenforcement = on > store.quotaexceededmsginterval = 2 > store.quotaexceededmsg="Subject: warning, overquota utilization$$Test > message" > store.quotagraceperiod = 24 > store.quotanotification = on > store.quotawarn = 90 > > I'm using JES2005Q4: > Sun Java(tm) System Messaging Server 6.2-6.01 (built Apr 3 2006) > libimta.so 6.2-6.01 (built 11:20:35, Apr 3 2006) > > Any Idea? > > Thanks in advanced. > Regards > -- > Osvaldo Fonseca -- Osvaldo Fonseca