Activity Not Available

News

 
Posted 19 days ago by Suyi
Hi partners and friends,

Here is a short update from our side regarding the WebApp 1.6 BETA. As you may know, it was released two weeks ago. We thank the community members that have sent us feedback and input.

Some unpleasant bugs ... [More] have come to our attention. With this second BETA release we want to address these issues:

 

When using the new HTML-editor (TinyMCE), [enters] are removed in your email (WA-6813).

In addition, we came across several issues during testing which were related to the fix above. We managed to fix most of them, except for WA-6849. This issue is in the TinyMCE-editor itself and we hope to fix this within the next release. 

How to get it

You can grab the latest version of the WebApp here.

Thanks again for your feedback. We are able to tackle these issues much quicker due your efforts.

Kind regards,

Zarafa Q&A

 

PS: our Jira system is currenrtly being updated and will be available later. [Less]
Posted 21 days ago by Robert Scheck
About 2.5 years ago I presented the first public version of pam_mapi. If you don't know pam_mapi, please have a look to my project.

Today I am happy to announce pam_mapi 0.2.0 - which is supporting Zarafa's feature management. What does this ... [More] mean? Since Zarafa 7.0.0 some features can be enabled and disabled on a per-user basis. If e.g. IMAP is disabled for a specific user any IMAP login will fail. More about this can be read in the Zarafa documentation, section "8.7. Zarafa Feature management".

This feature management can be now optionally applied to pam_mapi for e.g. SMTP authentication. But so far even if both, IMAP and POP3 were disabled, pam_mapi was still succeeding authentication and thus allowing to relay e-mails. If this is unwished the new argument "service=pop3|imap" can now be added to the PAM configuration file /etc/pam.d/smtp. This requires that either POP3 or IMAP is enabled to pass authentication.

Valid values for the "service" argument are values from "disabled_features" in /etc/zarafa/server.cfg. Multiple services can be listed using the pipe character ("|") and behave like a digital logic OR gate.

Configuration example for /etc/pam.d/smtp when authenticating only against Zarafa users while the IMAP feature must be enabled in Zarafa:

#%PAM-1.0
auth       required     pam_mapi.so try_first_pass service=imap
account    required     pam_mapi.so
More configuration examples are available in the documentation of pam_mapi.

Of course pam_mapi still supports Zarafa versions before 7.0.0 - however without feature/service management (and without unicode). The oldest with pam_mapi 0.2.0 tested Zarafa version is 6.20; the release where Zarafa got Open Source. [Less]
Posted about 1 month ago by Kiffin
We're on our way to the final release of WebApp 1.6, and it looks like it is a smooth road ahead.

For those of you that want to try it out early and get a sneak preview, you can download it here.

Lately I've been receiving a flood ... [More] of emails inquiring about the official release date, and it is apparent that many of you out there are eager to get your hands on this improved version.

In addition to a veritable slew of bug fixes totaling no less than sixty-five, we've introduced some nice new features.

To name a few: smoother and more user friendly rich text editor, pictures for contacts, deferred email send until all attachments have been uploaded, Apache 2.4 support, wildcards in mail filters for received, contact folders are included in the address book, keyboard shortcut for selecting all items above or below a given list item, a reset button to restore settings to factory default, and more.

For more information, feel free to look at the changelog.

Have fun and hold on to your pancakes!

Kiffin Gish
Development and Release Manager [Less]
Posted about 1 month ago by Jelle van der Waa
Employees at Zarafa often want to debug issues related to MAPI and verify if properties are written correctly in MAPI. All of our developers use GNU/Linux as their standard development environment and often want to look into how the data is stored ... [More] when they create an email (or for example import an EML). For GNU/Linux there aren't any tools which can connect to a Zarafa-server and display the stored information, so this blog article describes the development of the Zarafa-Inspector, it's usage and possible future features!

A couple of months ago we started working on the new Python Zarafa search solution. For search we created a new module called python-zarafa which makes it easy to interact with Zarafa. The developer who uses this module no longer has to have specific low-level knowledge of MAPI which makes it much easier to write code. Using python-zarafa we created a UI which makes it possible to look into MAPI and named it Zarafa-Inspector. The tool uses PyQt which is a python binding of the cross-platform GUI toolkit Qt for the creation of UI components.

 

The Zarafa-Inspector consists of two tabs, the first tab contains the global address book (GAB) and lists all of the users on the connected server. When you click on a user in the GAB tab, it will load the user's User Store in the "User Store" tab which contains:

a folder tree structure of the users store
the records in a selected folder (which are shown when you click on a folder)
the property table of the selected folder or record. (which is shown when you click on a folder or record)
the attachment and recipient table of a message (can be shown by right clicking on a record)

 

The right clicking on a record or folder also provides the following functionality:

deleting a message
creating a folder
export folder as MBOX
export folder as Maildir
importing an EML
saving an attachment from the attachment table

The Zarafa-Inspector is still under development and in the future I would like to add the following features:

Importing emails and MBOX formatted folders

Import and export Maildir

Editing records and properties

Viewing the recipienttable

Automatically syncing the userstore

 

You can start using the Zarafa-Inspector by following the instructions on Github, it's already possible to connect to a remote Zarafa-server using SSL. Please note that the program is still in it's experimental phase, so don't panic when things break!

 

Issues can be reported via the Github issuetracker https://github.com/zarafagroupware/zarafa-inspector/issues, also note that the performance of Zarafa-Inspector might be suboptimal since it hasn't been optimized to handle big mailfolders (200+ emails).

I hope you find my tool useful! [Less]
Posted about 1 month ago by Jelle van der Waa
Employees at Zarafa often want to debug issues related to MAPI and verify if properties are written correctly in MAPI. All of our developers use GNU/Linux as their standard development environment and often want to look into how the data is stored ... [More] when they create an email (or for example import an EML). For GNU/Linux there aren't any tools which can connect to a Zarafa-server and display the stored information, so this blog article describes the development of the Zarafa-Inspector, it's usage and possible future features!

A couple of months ago we started working on the new Python Zarafa search solution. For search we created a new module called python-zarafa which makes it easy to interact with Zarafa. The developer who uses this module no longer has to have specific low-level knowledge of MAPI which makes it much easier to write code. Using python-zarafa we created a UI which makes it possible to look into MAPI and named it Zarafa-Inspector. The tool uses PyQt which is a python binding of the cross-platform GUI toolkit Qt for the creation of UI components.

 

The Zarafa-Inspector consists of two tabs, the first tab contains the global address book (GAB) and lists all of the users on the connected server. When you click on a user in the GAB tab, it will load the user's User Store in the "User Store" tab which contains:

a folder tree structure of the users store
the records in a selected folder (which are shown when you click on a folder)
the property table of the selected folder or record. (which is shown when you click on a folder or record)
the attachment and recipient table of a message (can be shown by right clicking on a record)

 

The right clicking on a record or folder also provides the following functionality:

deleting a message
creating a folder
export folder as MBOX
export folder as Maildir
importing an EML
saving an attachment from the attachment table

The Zarafa-Inspector is still under development and in the future I would like to add the following features:

Importing emails and MBOX formatted folders

Import and export Maildir

Editing records and properties

Viewing the recipienttable

Automatically syncing the userstore

 

You can start using the Zarafa-Inspector by following the instructions on Github, it's already possible to connect to a remote Zarafa-server using SSL. Please note that the program is still in it's experimental phase, so don't panic when things break!

 

Issues can be reported via the Github issuetracker https://github.com/zarafagroupware/zarafa-inspector/issues, also note that the performance of Zarafa-Inspector might be suboptimal since it hasn't been optimized to handle big mailfolders (200+ emails).

I hope you find my tool useful! [Less]
Posted about 1 month ago by Kiffin
We are very pleased to announce the launch of ZCP 7.1.10 final.

Only one week ago we announced that the first release candidate ZCP 7.1.10 RC was available. As it was preceded by a significant amount of additional QA verification tests, we ... [More] felt pretty confident that in the end it would prove to be the Real McCoy.

That's what happened. This final release is identical to the RC since no issues have been reported and all additional internal testing has not shown up any other problems. Indeed, the promotion to final was a simple press of a button.

This final release introduces a number of exciting new features while at the same time maintaining stability. A new automated patching mechanism allows Outlook versions to be supported before an actual update via Microsoft Update.

This is the first release to support Click2Run versions which will make many of our customers quite happy. Secure Boot in combination with Windows 8 is now also a supported environment for the compatibility component.

For a complete list of changes, please have a look at the changelog.

So with all of that said, enjoy the ride and hang on to your zebra!

 

Kiffin Gish
Development and Release Manager [Less]
Posted about 1 month ago by Mark Dufour
As mentioned in my previous blog post New search using Xapian and Python, we are using Python more and more at Zarafa. For example, ZWS, the new Xapian-based search prototype, our internal testing framework and many custom system administration ... [More] scripts are written in Python. The main advantage of Python over especially C++ is that productivity is greatly increased. There is no compilation step, so building software becomes faster and (remote) debugging becomes easier. Automatic memory management further greatly improves stability (perhaps the biggest selling point of Java :-)). And last but not least, because of the high-level nature, Python programs are easier to understand, maintain and extend. It is no wonder that Python is one of the most popular high-level languages within the wider open source community.

Unfortunately, our current Python bindings are closely coupled to MAPI (hence the name "python-mapi"), which in many cases does not correspond to the abstraction level of the problems one is trying to solve. For example, suppose we want to scan the contents of attachments (which we clearly do in search). Using python-mapi, this would involve poking at a variety of MAPI properties, tables and streams and dealing with MAPI errors. But it can get even more complex when there are so called "named properties" involved. The bottom line is that MAPI is low-level and complicated as it has organically grown to suit new needs. While some helper functions have been added to python-mapi (such as a "GetUsers" function), we would really like to be able to use a fully object-oriented, more high-level, let's say "pythonic" layer above python-mapi which keeps simple things simple, while at the same time of course still allows one to dive into MAPI as needed.

Enter python-zarafa. While developing the new Xapian-based prototype replacement for search (see my previous blog post), we made sure to abstract as much MAPI-specific code to a separate, object-oriented library as possible. All the while paying much attention to reusability by other (future) programs. In fact there is little MAPI-specific code left in our prototype, only where needed (it is needed as search indexes individual MAPI properties). While there are many other things one can already do with this new library, the following (full!) sample program illustrates the most important aspects.

import zarafa

 

# connect to server, as specified on command-line (possibly including SSL info) or via defaults

s = zarafa.Server()

 

# loop over users on this server, with 'parse' checking the command-line for specific user names

for user in s.users(parse=True):

 

    # some basic user info

    print user.name, user.email, user.store.guid

 

    # print an indented overview of all folders in the user's default store

    for folder in user.store.folders(recurse=True):

        print folder.depth*'    '+folder.name

 

    # print an overview of attachments in inbox

    for item in user.store.inbox:

        print item.subject

        for attachment in item.attachments():

            print attachment.filename, len(attachment.data)

 

    # dive into MAPI if needed

    print user.properties(), user.store.properties()

As can be seen from the comments, through some underwater Python magic, the program automatically acquires several common command-line options. For example one can add '-c /etc/zarafa/admin.cfg' or '--user username' (or --help to see all common options), and the program will act accordingly. In recent versions of python-zarafa, it is even possible to setup a complete Zarafa 'service', so the program automatically gains a '-F' option, and logging is performed automatically as specified in the right configuration file. Error handling is also improved, as Python comes out-of-the-box with advanced exception handling and traceback functionality, and as we replace MAPI error codes with more readable error messages. It probably won't come as a surprise that the new search prototype is only a few hundred lines of code. Of course this is also due to the fact that we use an off-the-shelf search engine as well as Python itself.

As for the future, we hope to steadily improve and stabilize these bindings. Being quite a large (but fun!) job, it may take many months for it to become more or less feature-complete. Although in the meantime it is already quite useful. We just can't make a guarantee for the foreseeable future that the API will not change in major ways. Obviously one can always bundle a version of python-zarafa with a script, so it will not break, but ultimately our goal is to provide a stable 'python-zarafa' package. For the time being the bindings are also "read-only" for the most part, but in many situations of course we are not actually changing anything. The current version of the code, including some other examples, can already be found on github in any case, and we very much welcome your early feedback:

 

https://github.com/zarafagroupware/python-zarafa

 

In upcoming blog posts, we plan to describe some new programs and scripts that have already been written on top of python-zarafa, such as an alternative to MAPISpy/MFCMAPI called "zarafa-inspector". We will also provide further updates on the development of python-zarafa, so stay tuned!

 

For more information about the advantages of using Python, see the following interview:

Python and the Programmer
The Zen of Python
Type Checking and Techie Control
Python and the Tipping Point [Less]
Posted about 1 month ago by Kiffin
We are very pleased to announce the availability of the latest beta release ZCP 7.1.10 RC1.

As release candidate this is the first potential version to be a final product which is ready to release
unless significant bugs emerge ... [More] during internal testing.

As mentioned in the previous BETA1 announcement, this time around we were able to get in the last
changes to provide full support for S/MIME with offline profiles in MS Outlook.

We are happy to notify you that this version includes the new automated patching mechanism which
allows Outlook versions to be supported before an actual update via Microsoft Update.

Additionally, this release is the first release to support Click2Run versions. Secure Boot in combination
with Windows 8 is now also a supported environment for the compatibility component.

Finally, due to some performance issues we decided to revert MariaDB changes to a previous version
in order to allow us for time to investigate the issue more carefully. We expect to be taking a different
approach without the effect of performance degradation in the near future (for MariaDB).

Once again we would like to thank Robert Scheck for providing us with another amazing patch, this
one which fixes the RFC-3501 violating reply of the Zarafa IMAP gateway in response to a partial
fetch request.

From now on it's full steam ahead to the final release. Hang on to your umbrellas.

Kiffin Gish
Development and Release Manager [Less]
Posted 2 months ago by Kiffin
They say that the month of May brings with it new celebrations of life: warmer weather, blooming flowers and lots of new opportunities.

In a similar mood, we are excited to announce the latest ZCP 7.1.10 beta release.This is a first glimpse ... [More] at the many fixes and improvements as we quickly move forward to the final version.

The next step in Zarafa’s compatibility to Outlook

The biggest news is the upcoming completion of ZCP’s ‘Automatic Outlook patching mechanism’). Outook is a rather popular fat client at many Zarafa customers. Small groups of heavy users depend on such desktop applications. The mechanism provides a seamless on-the-fly integration with newer Outlook updates and ensures backward compatibility. This also works flawlessly with the Windows 8 secure boot.

Bugs, security patches and more

Next to the big new feature above, we also took care on many smaller things. I’ve summed up most of it for you:

 

Many major/minor bug fixes and code quality improvements (DRY refactoring and safer pointer usage).
Three security patches and several Zarafa Gateway fixes (special thanks to Robert Scheck)
More consistent dagent log level prios, Admins ability to backup archive stores with the zarafa-admin tool
Fixes to a couple rare glitches causing empty mail body Better support for UTF-8 character encoding

 

The next releases

Note that there are two known issues which are nearly finished but due to time constraints we were unable to include, namely:

Support for offline S/MIME public certificates
Final component Click2Run for Outlook 2013 (shared calendars)

We hope to include these fixes in the next beta. So until then have fun with this beta, enjoy the month of May and hang on to your hats.

Kiffin Gish

Development and Release Management [Less]
Posted 2 months ago by Kiffin
They say that the month of May brings with it new celebrations of life: warmer weather, blooming flowers and lots of new opportunities.

In a similar mood, we are excited to announce the latest ZCP 7.1.10 beta release.This is a first glimpse ... [More] at the many fixes and improvements as we quickly move forward to the final version.

The next step in Zarafa’s compatibility to Outlook

The biggest news is the upcoming completion of ZCP’s ‘Automatic Outlook patching mechanism’). Outook is a rather popular fat client at many Zarafa customers. Small groups of heavy users depend on such desktop applications. The mechanism provides a seamless on-the-fly integration with newer Outlook updates and ensures backward compatibility. This also works flawlessly with the Windows 8 secure boot.

Bugs, security patches and more

Next to the big new feature above, we also took care on many smaller things. I’ve summed up most of it for you:

 

Many major/minor bug fixes and code quality improvements (DRY refactoring and safer pointer usage).
Three security patches and several Zarafa Gateway fixes (special thanks to Robert Scheck)
More consistent dagent log level prios, Admins ability to backup archive stores with the zarafa-admin tool
Fixes to a couple rare glitches causing empty mail body Better support for UTF-8 character encoding

 

The next releases

Note that there are two known issues which are nearly finished but due to time constraints we were unable to include, namely:

 

Support for offline S/MIME public certificates
Final component Click2Run for Outlook 2013 (shared calendars)

We hope to include these fixes in the next beta. So until then have fun with this beta, enjoy the month of May and hang on to your hats.

Kiffin Gish

Development and Release Management [Less]