Oops, my mistake. Sorry, hadn't read the Outlook docs. Came as far as the sogo admin install and config docs, and made my assumption based on the info available on the web site. But it is an indicator that tells us that many people read the web site back and forward to get their information. Important info like the one I didn't find could have been there, and not only in the downloadable pdfs... just my two cents...
Sorry guys ;o), and Thanks Fabián for bringing this to my attention.
On Wednesday, January 18, 2012 09:51 AM CET, Fabián Rodríguez <[email protected]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2012-01-18 03:05, Harry M. Aasterud wrote:
> Mr Marcotte,
>
[...]
> Nowhere in the documentation it is written that the native Outlook
> compatibility is only supported up to a certain degree due to missing
> features.
It's actually pretty clear in the documentation:
"The current version of the Native Microsoft Outlook compatibility layer
has some limitations.
Those limitations will be overcome in the upcoming beta. If you are
interested in having those limitations fixed more rapidly, please
contact Inverse by sending an email to [email protected]."
(page 14 of
http://www.sogo.nu/files/docs/SOGo%20Native%20Microsoft%20Outlook%20Configuration.pdf
at http://www.sogo.nu/downloads/documentation.html)
Not sure if that doc was posted after b1 but it looks good.
Having a PDF handy to forward to the Windows admins with an exact quote
in 2 sentences, which also covers commercial support (pay if you can't
wait) is as good as it gets.
Great work, indeed.
Cheers,
F.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: PGP/Mime available upon request
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8WiBwACgkQfUcTXFrypNUDZQCdF79xPCePoqbBpOgiH+vZbpQa
E5QAoJ+70fkqLt0HDAq5SBGbY03oSpbG
=/knB
-----END PGP SIGNATURE-----
--
[email protected]
https://inverse.ca/sogo/lists
