Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. 6.0.1 SOGo email filters are gone

6.0.1 SOGo email filters are gone

Scheduled Pinned Locked Moved Solved Support
8 Posts 4 Posters 1.3k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    adrw
    wrote on last edited by
    #1

    The filters still seem to be applying but I can't see them in the UI anymore in SOGo after upgrading to Cloudron 6.0.1.

    girishG 1 Reply Last reply
    0
    • A adrw

      The filters still seem to be applying but I can't see them in the UI anymore in SOGo after upgrading to Cloudron 6.0.1.

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by girish
      #2

      @adrw Do you mean the filter UI itself is missing or just the filters are missing? One thing you can check is if the filters are there on the server. You can do this by:

      cd /home/yellowtent/boxdata/mail/vmail
      find . -type f "*.sieve"
      
      A 2 Replies Last reply
      1
      • girishG girish

        @adrw Do you mean the filter UI itself is missing or just the filters are missing? One thing you can check is if the filters are there on the server. You can do this by:

        cd /home/yellowtent/boxdata/mail/vmail
        find . -type f "*.sieve"
        
        A Offline
        A Offline
        adrw
        wrote on last edited by
        #3

        @girish Thanks! I had been logging in with the wrong email username, and my filters were on the other one. Whoops!

        1 Reply Last reply
        1
        • girishG girish

          @adrw Do you mean the filter UI itself is missing or just the filters are missing? One thing you can check is if the filters are there on the server. You can do this by:

          cd /home/yellowtent/boxdata/mail/vmail
          find . -type f "*.sieve"
          
          A Offline
          A Offline
          adrw
          wrote on last edited by
          #4

          @girish Would it be possible to unite the sieve filters per mailbox across all email apps instead of silo-ing them?

          jimcavoliJ 1 Reply Last reply
          0
          • A adrw

            @girish Would it be possible to unite the sieve filters per mailbox across all email apps instead of silo-ing them?

            jimcavoliJ Offline
            jimcavoliJ Offline
            jimcavoli
            App Dev
            wrote on last edited by jimcavoli
            #5

            @adrw Not really. The management of the filters is largely up to the apps themselves, and they tend not to play super nicely with each other.

            1 Reply Last reply
            2
            • robiR Offline
              robiR Offline
              robi
              wrote on last edited by
              #6

              has anyone tried to compare the .sieve files and see what makes them so different?

              Conscious tech

              1 Reply Last reply
              0
              • girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by girish
                #7

                To add to what @jimcavoli said, I think the reason is that the sieve language is probably hard to parse. Curiously, rainloop has a whole meta language going with comments in the sieve file which helps it parse.

                A 1 Reply Last reply
                0
                • girishG girish

                  To add to what @jimcavoli said, I think the reason is that the sieve language is probably hard to parse. Curiously, rainloop has a whole meta language going with comments in the sieve file which helps it parse.

                  A Offline
                  A Offline
                  adrw
                  wrote on last edited by
                  #8

                  @girish Oh wow, had no idea that it wasn't as standardized as it seems. Thanks others for clarifying too.

                  1 Reply Last reply
                  0
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  • Login

                  • Don't have an account? Register

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Bookmarks
                  • Search