Re: Zimbra 6.0.9

[Jim Michael <jimm@csufresno.edu>]

So far, that's the only issue we've seen.  I've noticed the ability to "Forget" addresses from auto-complete, but haven't got a clear picture of when it is offered yet.

Jim

--
James D Michael
Associate Director, Systems
California State University, Fresno - ITS Dept
e-mail: jim_michael@csufresno.edu

Please take a few seconds to help me, and my team, improve!
https://rypple.com/jimm/HowAreWeDoing

“To love someone deeply gives you strength. Being loved by someone deeply gives you courage.” - Lao-Tzu

----- Original Message -----
> Excellent! Have you discovered any differences? Or was that the
> biggie?
> 
> Our group is hoping to upgrade our production environment in the near
> future, and we love avoiding surprises. :)
> 
> Beth
> 
> On Thu, 2 Dec 2010, Jim Michael wrote:
> 
> > Date: Thu, 2 Dec 2010 10:04:12 -0800 (PST)
> > To: Beth Halsema <bhalsema@purdue.edu>
> > From: Jim Michael <jimm@csufresno.edu>
> > Cc: Matt Mencel <MR-Mencel@wiu.edu>,
> >     zimbra-hied-admins <zimbra-hied-admins@sfu.ca>
> > Subject: Re: Zimbra 6.0.9
> >
> > Further update. My staff had noticed the bug that Beth reported and
> > included correcting that issue in last nights maintenance. So, we
> > are at 6.0.9 with that issue patched. So far our expereince remains
> > good.
> >
> > --
> > James D Michael
> > Associate Director, Systems
> > California State University, Fresno - ITS Dept
> > e-mail: jim_michael@csufresno.edu
> >
> > Please take a few seconds to help me, and my team, improve!
> > https://rypple.com/jimm/HowAreWeDoing
> >
> > “To love someone deeply gives you strength. Being loved by someone
> > deeply gives you courage.” - Lao-Tzu
> >
> > ----- Original Message -----
> > > We just upgraded from 6.0.7 to 6.0.9 last night. So far so good.
> > > We
> > > will look at the reported issue in our environment. Thanks for
> > > sharing
> > > this, Beth.
> > >
> > > --
> > > James D Michael
> > > Associate Director, Systems
> > > California State University, Fresno - ITS Dept
> > > e-mail: jim_michael@csufresno.edu
> > >
> > > Please take a few seconds to help me, and my team, improve!
> > > https://rypple.com/jimm/HowAreWeDoing
> > >
> > > “To love someone deeply gives you strength. Being loved by someone
> > > deeply gives you courage.” - Lao-Tzu
> > >
> > > ----- Beth Halsema <bhalsema@purdue.edu> wrote:
> > > >
> > > > We are seeing this behavior in our test environment as well. I
> > > > found
> > > > the
> > > > following Zimbra bug report:
> > > >
> > > > 	http://bugzilla.zimbra.com/show_bug.cgi?id=53584
> > > >
> > > > Beth
> > > > -------------------------------------------------------------------------
> > > > Beth A. Halsema email:bhalsema@purdue.edu
> > > > ITaP Mailhub Systems Administrator
> > > > OVPIT - IT Systems & Operations
> > > >
> > > >
> > > > On Wed, 1 Dec 2010, Matt Mencel wrote:
> > > >
> > > > > Date: Wed, 1 Dec 2010 16:01:34 -0600 (CST)
> > > > > To: zimbra-hied-admins <zimbra-hied-admins@sfu.ca>
> > > > > From: Matt Mencel <MR-Mencel@wiu.edu>
> > > > > Subject: Re: Zimbra 6.0.9
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > We upgraded this past Friday as well. Everything seems to be
> > > > > fine,
> > > > > but we did notice one strange issue.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Apparently in our case, the zimbra upgrade script didn't
> > > > > update
> > > > > some of the logrotate user:group ownerships in
> > > > > /etc/logrotate.d/zimbra.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > See here...
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > /var/log/zimbra.log {
> > > > >
> > > > > daily
> > > > >
> > > > > missingok
> > > > >
> > > > > notifempty
> > > > >
> > > > > create 0644 USER GROUP
> > > > >
> > > > > postrotate
> > > > >
> > > > > killall -HUP syslogd 2> /dev/null || true
> > > > >
> > > > > su - zimbra -c "/opt/zimbra/bin/zmswatchctl restart" >
> > > > > /dev/null
> > > > > 2>&1 || true
> > > > >
> > > > > endscript
> > > > >
> > > > > compress
> > > > >
> > > > > }
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > /var/log/zimbra-stats.log {
> > > > >
> > > > > daily
> > > > >
> > > > > missingok
> > > > >
> > > > > notifempty
> > > > >
> > > > > create 0644 USER GROUP
> > > > >
> > > > > postrotate
> > > > >
> > > > > killall -HUP syslogd 2> /dev/null || true
> > > > >
> > > > > su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl restart" >
> > > > > /dev/null 2>&1 || true
> > > > >
> > > > > endscript
> > > > >
> > > > > rotate 0
> > > > >
> > > > > }
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "USER GROUP" didn't get replaced correctly during the upgrade.
> > > > > It
> > > > > did this to every one of our servers and we didn't notice it
> > > > > until
> > > > > our volumes started growing and we realized logs weren't
> > > > > rotating.
> > > > >
> > > > >
> > > > > Matt Mencel
> > > > > WIU