[OGo-Users] OgO Bug 789 - any progress?
Adam Tauno Williams
users@opengroupware.org
Mon, 28 Jan 2008 10:11:09 -0500
--=-L3qBwYqHUgpJ7gBAfZth
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
> bugs 789 [1] and 843 [2] are still open, although they are now 3.5 =20
There is only one bug here, 843 is marked as a duplicate of 789
> years old. And they are still annoying if user names shall be spelled =20
> correctly. I built OgO from scratch using sope-4.7.1-fwd-r1502.tar.gz =20
> and opengroupware.org-1.1.7-close-r1987.tar.gz, and it's still in.
> Any idea when it will be fixed? Could you give me a pointer where I =20
> had to look for this stuff; having built the sources anyway, I would be =20
> willing to look into that issue myself.
I'm not familiar enough with specific mail standards to know how this
should be represented (what should happen to umulats, etc... in a mail
header?). We also don't use the OGo webmail interface much at all - it
is very easily the weakest component of the suite. But I'll help steer
you to the right place in the OGo/SOPE code if I can.
(1) I'd ask on the SOGo list if they can duplicate the problem; if so
then the bug lies in SOPE (below OGo/SOGo) and needs to be fixed there.
(2) I'd look at the raw message on you IMAP server to see what the
message looks like on disk.
If it is OK in both those then the problem must be in WebUI/Mailer
somewhere. Is the message buggered up just when it is being viewed (the
displayed to:) or does the user have to hit reply, etc... in order to
get a buggered address? I'd log that transaction (see WMOGAG's
debugging section) to see what is actually being sent to the browser,
to narrow down if OGo is sending the wrong string to the browser or if
the browser is mangling the string (perhaps the codepage of the browser
isn't set correctly, just guessing)?
> Best, Albrecht.
> [1] <http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=3D789>
> [2] <http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=3D843>
--=-L3qBwYqHUgpJ7gBAfZth
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQBHnfCNLRePpNle04MRAoM9AJ9NLNSZzrHZlj2HoX8f9ytwB9hotwCeIrb2
g9p3YJg4nCV6fjRWqNAxqkA=
=1T1p
-----END PGP SIGNATURE-----
--=-L3qBwYqHUgpJ7gBAfZth--