[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Zimbra 6.0.9
Just forwarding this along:
----- Forwarded Message -----
From: skhavari@vmware.com
Sent: Thursday, December 2, 2010 5:08:08 PM
------=_Part_1552_340847000.1291338435983
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Jim,=20
Auto-complete results are displayed ranked by how frequently one sends to a=
particular recipient, aka its auto-complete rank. Eg, if you compose many =
messages to sam@zimbra.com, when you type s, sam@zimbra.com should be first=
in the list. ZCS remembers every recipient sent to and its rank and 'forge=
t' was introduced to give the user the ability to reset a suggestions rank.=
Most addresses have have 0 rank and we found that typos (invalid addresses=
) would bubble to the top. The 'forget' option gives users a way to reset t=
he ranking on these bad addresses.=20
The 'forget' option is displayed if at least one message has been sent to t=
he address (the address has a rank !=3D 0).=20
Cheers,=20
Sam=20
----- Original Message -----
From: "Jim Michael" <jimm@csufresno.edu>=20
To: "Beth Halsema" <bhalsema@purdue.edu>=20
Cc: "Matt Mencel" <MR-Mencel@wiu.edu>, "zimbra-hied-admins" <zimbra-hied-ad=
mins@sfu.ca>=20
Sent: Thursday, December 2, 2010 4:50:36 PM=20
Subject: Re: Zimbra 6.0.9=20
So far, that's the only issue we've seen. I've noticed the ability to "Forg=
et" addresses from auto-complete, but haven't got a clear picture of when i=
t is offered yet.=20
Jim=20
--=20
James D Michael=20
Associate Director, Systems=20
California State University, Fresno - ITS Dept=20
e-mail: jim_michael@csufresno.edu=20
Please take a few seconds to help me, and my team, improve!=20
https://rypple.com/jimm/HowAreWeDoing=20
=E2=80=9CTo love someone deeply gives you strength. Being loved by someone =
deeply gives you courage.=E2=80=9D - Lao-Tzu=20
----- Original Message -----=20
> Excellent! Have you discovered any differences? Or was that the=20
> biggie?=20
>=20
> Our group is hoping to upgrade our production environment in the near=20
> future, and we love avoiding surprises. :)=20
>=20
> Beth=20
>=20
> On Thu, 2 Dec 2010, Jim Michael wrote:=20
>=20
> > Date: Thu, 2 Dec 2010 10:04:12 -0800 (PST)=20
> > To: Beth Halsema <bhalsema@purdue.edu>=20
> > From: Jim Michael <jimm@csufresno.edu>=20
> > Cc: Matt Mencel <MR-Mencel@wiu.edu>,=20
> > zimbra-hied-admins <zimbra-hied-admins@sfu.ca>=20
> > Subject: Re: Zimbra 6.0.9=20
> >=20
> > Further update. My staff had noticed the bug that Beth reported and=20
> > included correcting that issue in last nights maintenance. So, we=20
> > are at 6.0.9 with that issue patched. So far our expereince remains=20
> > good.=20
> >=20
> > --=20
> > James D Michael=20
> > Associate Director, Systems=20
> > California State University, Fresno - ITS Dept=20
> > e-mail: jim_michael@csufresno.edu=20
> >=20
> > Please take a few seconds to help me, and my team, improve!=20
> > https://rypple.com/jimm/HowAreWeDoing=20
> >=20
> > =E2=80=9CTo love someone deeply gives you strength. Being loved by some=
one=20
> > deeply gives you courage.=E2=80=9D - Lao-Tzu=20
> >=20
> > ----- Original Message -----=20
> > > We just upgraded from 6.0.7 to 6.0.9 last night. So far so good.=20
> > > We=20
> > > will look at the reported issue in our environment. Thanks for=20
> > > sharing=20
> > > this, Beth.=20
> > >=20
> > > --=20
> > > James D Michael=20
> > > Associate Director, Systems=20
> > > California State University, Fresno - ITS Dept=20
> > > e-mail: jim_michael@csufresno.edu=20
> > >=20
> > > Please take a few seconds to help me, and my team, improve!=20
> > > https://rypple.com/jimm/HowAreWeDoing=20
> > >=20
> > > =E2=80=9CTo love someone deeply gives you strength. Being loved by so=
meone=20
> > > deeply gives you courage.=E2=80=9D - Lao-Tzu=20
> > >=20
> > > ----- Beth Halsema <bhalsema@purdue.edu> wrote:=20
> > > >=20
> > > > We are seeing this behavior in our test environment as well. I=20
> > > > found=20
> > > > the=20
> > > > following Zimbra bug report:=20
> > > >=20
> > > > http://bugzilla.zimbra.com/show_bug.cgi?id=3D53584=20
> > > >=20
> > > > Beth=20
> > > > -------------------------------------------------------------------=
------=20
> > > > Beth A. Halsema email:bhalsema@purdue.edu=20
> > > > ITaP Mailhub Systems Administrator=20
> > > > OVPIT - IT Systems & Operations=20
> > > >=20
> > > >=20
> > > > On Wed, 1 Dec 2010, Matt Mencel wrote:=20
> > > >=20
> > > > > Date: Wed, 1 Dec 2010 16:01:34 -0600 (CST)=20
> > > > > To: zimbra-hied-admins <zimbra-hied-admins@sfu.ca>=20
> > > > > From: Matt Mencel <MR-Mencel@wiu.edu>=20
> > > > > Subject: Re: Zimbra 6.0.9=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > > We upgraded this past Friday as well. Everything seems to be=20
> > > > > fine,=20
> > > > > but we did notice one strange issue.=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > > Apparently in our case, the zimbra upgrade script didn't=20
> > > > > update=20
> > > > > some of the logrotate user:group ownerships in=20
> > > > > /etc/logrotate.d/zimbra.=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > > See here...=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > > /var/log/zimbra.log {=20
> > > > >=20
> > > > > daily=20
> > > > >=20
> > > > > missingok=20
> > > > >=20
> > > > > notifempty=20
> > > > >=20
> > > > > create 0644 USER GROUP=20
> > > > >=20
> > > > > postrotate=20
> > > > >=20
> > > > > killall -HUP syslogd 2> /dev/null || true=20
> > > > >=20
> > > > > su - zimbra -c "/opt/zimbra/bin/zmswatchctl restart" >=20
> > > > > /dev/null=20
> > > > > 2>&1 || true=20
> > > > >=20
> > > > > endscript=20
> > > > >=20
> > > > > compress=20
> > > > >=20
> > > > > }=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > > /var/log/zimbra-stats.log {=20
> > > > >=20
> > > > > daily=20
> > > > >=20
> > > > > missingok=20
> > > > >=20
> > > > > notifempty=20
> > > > >=20
> > > > > create 0644 USER GROUP=20
> > > > >=20
> > > > > postrotate=20
> > > > >=20
> > > > > killall -HUP syslogd 2> /dev/null || true=20
> > > > >=20
> > > > > su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl restart" >=20
> > > > > /dev/null 2>&1 || true=20
> > > > >=20
> > > > > endscript=20
> > > > >=20
> > > > > rotate 0=20
> > > > >=20
> > > > > }=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > >=20
> > > > > "USER GROUP" didn't get replaced correctly during the upgrade.=20
> > > > > It=20
> > > > > did this to every one of our servers and we didn't notice it=20
> > > > > until=20
> > > > > our volumes started growing and we realized logs weren't=20
> > > > > rotating.=20
> > > > >=20
> > > > >=20
> > > > > Matt Mencel=20
> > > > > WIU=20
------=_Part_1552_340847000.1291338435983
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><head><style type=3D'text/css'>p { margin: 0; }</style></head><body><=
div style=3D'font-family: Verdana; font-size: 10pt; color: #1a1a1a'>Jim,<di=
v><br></div><div>Auto-complete results are displayed ranked by how frequent=
ly one sends to a particular recipient, aka its auto-complete rank. E=
g, if you compose many messages to sam@zimbra.com, when you type s, sam@zim=
bra.com should be first in the list. ZCS remembers every recipient se=
nt to and its rank and 'forget' was introduced to give the user the ability=
to reset a suggestions rank. Most addresses have have 0 rank and we =
found that typos (invalid addresses) would bubble to the top. The 'f=
orget' option gives users a way to reset the ranking on these bad addresses=
.</div><div><br></div><div>The 'forget' option is displayed if at least one=
message has been sent to the address (the address has a rank !=3D 0).</div=
><div><br></div><div>Cheers,</div><div>Sam<br><br><hr id=3D"zwchr"><b>From:=
</b>"Jim Michael" <jimm@csufresno.edu><br><b>To: </b>"Beth Halsema" =
<bhalsema@purdue.edu><br><b>Cc: </b>"Matt Mencel" <MR-Mencel@wiu.e=
du>, "zimbra-hied-admins" <zimbra-hied-admins@sfu.ca><br><b>Sent: =
</b>Thursday, December 2, 2010 4:50:36 PM<br><b>Subject: </b>Re: Zimbra 6.0=
.9<br><br>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 p=
icture of when it is offered yet.<br><br>Jim<br><br>--<br>James D Michael<b=
r>Associate Director, Systems<br>California State University, Fresno - ITS =
Dept<br>e-mail: jim_michael@csufresno.edu<br><br>Please take a few seconds =
to help me, and my team, improve!<br>https://rypple.com/jimm/HowAreWeDoing<=
br><br>=E2=80=9CTo love someone deeply gives you strength. Being loved by s=
omeone deeply gives you courage.=E2=80=9D - Lao-Tzu<br><br>----- Original M=
essage -----<br>> Excellent! Have you discovered any differences? Or was=
that the<br>> biggie?<br>> <br>> Our group is hoping to upgrade o=
ur production environment in the near<br>> future, and we love avoiding =
surprises. :)<br>> <br>> Beth<br>> <br>> On Thu, 2 Dec 2010, Ji=
m Michael wrote:<br>> <br>> > Date: Thu, 2 Dec 2010 10:04:12 -0800=
(PST)<br>> > To: Beth Halsema <bhalsema@purdue.edu><br>> &g=
t; From: Jim Michael <jimm@csufresno.edu><br>> > Cc: Matt Mence=
l <MR-Mencel@wiu.edu>,<br>> > zimbra-hied-admins =
<zimbra-hied-admins@sfu.ca><br>> > Subject: Re: Zimbra 6.0.9<br=
>> ><br>> > Further update. My staff had noticed the bug that B=
eth reported and<br>> > included correcting that issue in last nights=
maintenance. So, we<br>> > are at 6.0.9 with that issue patched. So =
far our expereince remains<br>> > good.<br>> ><br>> > --<=
br>> > James D Michael<br>> > Associate Director, Systems<br>&g=
t; > California State University, Fresno - ITS Dept<br>> > e-mail:=
jim_michael@csufresno.edu<br>> ><br>> > Please take a few seco=
nds to help me, and my team, improve!<br>> > https://rypple.com/jimm/=
HowAreWeDoing<br>> ><br>> > =E2=80=9CTo love someone deeply giv=
es you strength. Being loved by someone<br>> > deeply gives you coura=
ge.=E2=80=9D - Lao-Tzu<br>> ><br>> > ----- Original Message ---=
--<br>> > > We just upgraded from 6.0.7 to 6.0.9 last night. So fa=
r so good.<br>> > > We<br>> > > will look at the reported=
issue in our environment. Thanks for<br>> > > sharing<br>> >=
; > this, Beth.<br>> > ><br>> > > --<br>> > >=
James D Michael<br>> > > Associate Director, Systems<br>> >=
> California State University, Fresno - ITS Dept<br>> > > e-ma=
il: jim_michael@csufresno.edu<br>> > ><br>> > > Please ta=
ke a few seconds to help me, and my team, improve!<br>> > > https:=
//rypple.com/jimm/HowAreWeDoing<br>> > ><br>> > > =E2=80=
=9CTo love someone deeply gives you strength. Being loved by someone<br>>=
; > > deeply gives you courage.=E2=80=9D - Lao-Tzu<br>> > ><=
br>> > > ----- Beth Halsema <bhalsema@purdue.edu> wrote:<br>=
> > > ><br>> > > > We are seeing this behavior in o=
ur test environment as well. I<br>> > > > found<br>> > &g=
t; > the<br>> > > > following Zimbra bug report:<br>> >=
; > ><br>> > > > &nbs=
p; http://bugzilla.zimbra.com/show_bug.cgi?id=3D53584<br>> > >=
; ><br>> > > > Beth<br>> > > > -----------------=
--------------------------------------------------------<br>> > > =
> Beth A. Halsema email:bhalsema@purdue.edu<br>> > > > ITaP =
Mailhub Systems Administrator<br>> > > > OVPIT - IT Systems &am=
p; Operations<br>> > > ><br>> > > ><br>> > &g=
t; > On Wed, 1 Dec 2010, Matt Mencel wrote:<br>> > > ><br>&g=
t; > > > > Date: Wed, 1 Dec 2010 16:01:34 -0600 (CST)<br>> &=
gt; > > > To: zimbra-hied-admins <zimbra-hied-admins@sfu.ca>=
<br>> > > > > From: Matt Mencel <MR-Mencel@wiu.edu><br=
>> > > > > Subject: Re: Zimbra 6.0.9<br>> > > > =
><br>> > > > ><br>> > > > ><br>> > &=
gt; > ><br>> > > > > We upgraded this past Friday as w=
ell. Everything seems to be<br>> > > > > fine,<br>> > =
> > > but we did notice one strange issue.<br>> > > > =
><br>> > > > ><br>> > > > ><br>> > &=
gt; > ><br>> > > > > Apparently in our case, the zimbr=
a upgrade script didn't<br>> > > > > update<br>> > >=
; > > some of the logrotate user:group ownerships in<br>> > >=
; > > /etc/logrotate.d/zimbra.<br>> > > > ><br>> &g=
t; > > ><br>> > > > ><br>> > > > ><b=
r>> > > > > See here...<br>> > > > ><br>> =
> > > ><br>> > > > ><br>> > > > >=
<br>> > > > ><br>> > > > ><br>> > > =
> > /var/log/zimbra.log {<br>> > > > ><br>> > &g=
t; > > daily<br>> > > > ><br>> > > > > =
missingok<br>> > > > ><br>> > > > > notifempt=
y<br>> > > > ><br>> > > > > create 0644 USER =
GROUP<br>> > > > ><br>> > > > > postrotate<br=
>> > > > ><br>> > > > > killall -HUP syslogd =
2> /dev/null || true<br>> > > > ><br>> > > > =
> su - zimbra -c "/opt/zimbra/bin/zmswatchctl restart" ><br>> >=
> > > /dev/null<br>> > > > > 2>&1 || true<b=
r>> > > > ><br>> > > > > endscript<br>> &g=
t; > > ><br>> > > > > compress<br>> > > &g=
t; ><br>> > > > > }<br>> > > > ><br>> &=
gt; > > ><br>> > > > ><br>> > > > ><=
br>> > > > > /var/log/zimbra-stats.log {<br>> > > &=
gt; ><br>> > > > > daily<br>> > > > ><br>&=
gt; > > > > missingok<br>> > > > ><br>> > =
> > > notifempty<br>> > > > ><br>> > > >=
; > create 0644 USER GROUP<br>> > > > ><br>> > >=
> > postrotate<br>> > > > ><br>> > > > &g=
t; killall -HUP syslogd 2> /dev/null || true<br>> > > > >=
<br>> > > > > su - zimbra -c "/opt/zimbra/bin/zmlogswatchctl=
restart" ><br>> > > > > /dev/null 2>&1 || true<br=
>> > > > ><br>> > > > > endscript<br>> >=
; > > ><br>> > > > > rotate 0<br>> > > >=
; ><br>> > > > > }<br>> > > > ><br>> &g=
t; > > ><br>> > > > ><br>> > > > ><b=
r>> > > > > "USER GROUP" didn't get replaced correctly durin=
g the upgrade.<br>> > > > > It<br>> > > > > d=
id this to every one of our servers and we didn't notice it<br>> > &g=
t; > > until<br>> > > > > our volumes started growing =
and we realized logs weren't<br>> > > > > rotating.<br>> =
> > > ><br>> > > > ><br>> > > > >=
Matt Mencel<br>> > > > > WIU<br></div></div></body></html>
------=_Part_1552_340847000.1291338435983--
--
Steve Hillman IT Architect
hillman@sfu.ca IT Infrastructure
778-782-3960 Simon Fraser University