Announcement

Collapse
No announcement yet.

External IMAP working / Sieve error / --dbonly flag missing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • External IMAP working / Sieve error / --dbonly flag missing

    Hello Community,

    i have succesfully set up OX on Ubuntu via the short Installation walkthrough in the project wiki.
    Everything is working fine and i really appreciate the work on the community edition.

    I'm using OX with an external IMAP server from my Service Provider. Mail access works like a charm. I've read a lot of posts regarding external IMAP servers. In every post regarding this issue it is advised to use the --dbonly flag. But if i try to create a user with this option i get the following

    Code:
    Error: Unrecognized options on the command line: Unknown option '--dbonly'
    Also, the --extendedoptions flag doesn't show me this option.

    The main problem i have is the following error in the OX GUI after login:

    Error in low level connection to sieve server
    As i understand, sieve works together with cyrus but since i use an external IMAP do i need sieve at all? Would the --dbonly flag fix this issue? Why can't i use it?

    I hope anyone could give me a hint.

    Greetings,
    Sven

  • #2
    Hi Sven,

    the --dbonly flag is only required when using the Open-Xchange Express Edition because it comes with a configuration toolkit that automatically creates users at the local IMAP Server. With the open-xchange-admin-plugin-hosting package installed you won't need to set this flag (and it does not exist at the hosting plugin).
    Just use --imapserver --smtpserver and --imaplogin to specify your ISP servers credentials.
    Sieve is a widely used protocol to manage mailfiltering rules. If your ISP does not offer this at his IMAP Server you can uninstall the corresponding package from the system or disable the osgi bundle using the "uninstallbundle" command line tool.

    Greetings
    Last edited by Martin Heiland; 08-05-2008, 01:11 PM.

    Comment


    • #3
      Some more information about the OSGI stuff we're using. It allows to load/unload parts of the server in runtime, just like adding a device driver to your operating system. You can see the list of all available bundles by using the listbundles tool:

      oxhegw01:/opt/open-xchange/sbin# ./listbundles

      bundlename: org.eclipse.osgi status: ACTIVE
      bundlename: com.openexchange.authentication.database status: ACTIVE
      bundlename: com.openexchange.axis2 status: ACTIVE
      bundlename: com.openexchange.caching status: ACTIVE
      bundlename: com.openexchange.charset status: ACTIVE
      bundlename: com.openexchange.common status: ACTIVE
      bundlename: com.openexchange.configjump.generic status: ACTIVE
      bundlename: com.openexchange.configread status: ACTIVE
      bundlename: com.openexchange.control status: ACTIVE
      bundlename: com.openexchange.global status: ACTIVE
      bundlename: com.openexchange.group.managerequest status: ACTIVE
      bundlename: com.openexchange.groupware.settings.extensions status: ACTIVE
      bundlename: com.openexchange.i18n status: ACTIVE
      bundlename: com.openexchange.imap status: ACTIVE
      bundlename: com.openexchange.mail.filter status: ACTIVE
      bundlename: com.openexchange.management status: ACTIVE
      bundlename: com.openexchange.monitoring status: ACTIVE
      bundlename: com.openexchange.push.udp status: ACTIVE
      bundlename: com.openexchange.resource.managerequest status: ACTIVE
      bundlename: com.openexchange.server status: ACTIVE
      bundlename: com.openexchange.sessiond status: ACTIVE
      bundlename: com.openexchange.smtp status: ACTIVE
      bundlename: com.openexchange.spamhandler.default status: ACTIVE
      bundlename: javax.servlet status: ACTIVE
      bundlename: net.freeutils.jcharset status: ACTIVE
      bundlename: org.apache.commons.logging status: ACTIVE
      bundlename: org.eclipse.equinox.event status: ACTIVE
      bundlename: org.eclipse.osgi.services status: ACTIVE


      "com.openexchange.mail.filter" is the module that provides the sieve implementation, as you can see this is in state ACTIVE which means it is working and currently in use. To end this module, just use the stopbundle tool:

      ./stopbundle com.openexchange.mail.filter

      The list now shows the bundle as RESOLVED which means it is available but not running. Now the sieve service is disabled and after a user does a relogin you won't experience the sieve error.

      Comment


      • #4
        Gemoje,

        Thanks for your advice and fast reply.

        OBSOLETE: Was writing my post just in time with yours
        Everything's fine now, you earned a bottle of IRLE Beer!! Thanks.


        Sorry I'm fairly new to OX, could you help me a little bit further?
        Which bundle do i have to uninstall?

        Code:
        :~$ /opt/open-xchange/sbin/listbundles
        bundlename: org.eclipse.osgi status: ACTIVE
        bundlename: com.openexchange.authentication.database status: ACTIVE
        bundlename: com.openexchange.axis2 status: ACTIVE
        bundlename: com.openexchange.caching status: ACTIVE
        bundlename: com.openexchange.charset status: ACTIVE
        bundlename: com.openexchange.common status: ACTIVE
        bundlename: com.openexchange.configjump.generic status: ACTIVE
        bundlename: com.openexchange.configread status: ACTIVE
        bundlename: com.openexchange.control status: ACTIVE
        bundlename: com.openexchange.global status: ACTIVE
        bundlename: com.openexchange.group.managerequest status: ACTIVE
        bundlename: com.openexchange.groupware.settings.extensions status: ACTIVE
        bundlename: com.openexchange.i18n status: ACTIVE
        bundlename: com.openexchange.imap status: ACTIVE
        bundlename: com.openexchange.mail.filter status: ACTIVE
        bundlename: com.openexchange.management status: ACTIVE
        bundlename: com.openexchange.monitoring status: ACTIVE
        bundlename: com.openexchange.push.udp status: ACTIVE
        bundlename: com.openexchange.resource.managerequest status: ACTIVE
        bundlename: com.openexchange.server status: ACTIVE
        bundlename: com.openexchange.sessiond status: ACTIVE
        bundlename: com.openexchange.smtp status: ACTIVE
        bundlename: com.openexchange.spamhandler.default status: ACTIVE
        bundlename: javax.servlet status: ACTIVE
        bundlename: net.freeutils.jcharset status: ACTIVE
        bundlename: org.apache.commons.logging status: ACTIVE
        bundlename: org.eclipse.equinox.event status: ACTIVE
        bundlename: org.eclipse.osgi.services status: ACTIVE
        If I try to

        Code:
        :~$ /opt/open-xchange/sbin/uninstallbundle org.eclipse.osgi
        for example the corresponding bundle is still marked as ACTIVE. Tried a groupware restart also.

        Am i missing a parameter?

        Code:
        uninstallbundle (-h <jmx host> -p <jmx port>) bundle name
        Greetings,
        Sven
        Last edited by Guest; 08-05-2008, 01:37 PM.

        Comment


        • #5
          I prefer Bosch and Krombacher, but thanks anyway

          Comment

          Working...
          X