Sieve DBERROR with avelsieve

From: Mike Husmann (no email)
Date: Thu Oct 05 2006 - 09:49:39 EDT

  • Next message: Elizabeth Schwartz: "Cyrus, Solaris 10, ZFS? (and NIS?)"

    Hey all,
      I just upgraded the avelsieve plugin in my Squirrelmail site install to 1.9.7 and
    have suddenly started receiving errors. Every time I make a modification using
    the sieve plugin, I get the following error:

    Oct 5 08:24:38 rusty sieve[18879]: DBERROR: error exiting application: Invalid
    argument

    But for that same transaction, there is no mention of any error in the debug log:

    Oct 5 08:24:37 rusty sieve[18879]: executed
    Oct 5 08:24:37 rusty sieve[18879]: accepted connection
    Oct 5 08:24:37 rusty sieve[18879]: mystore: starting txn 2147484734
    Oct 5 08:24:37 rusty sieve[18879]: mystore: committing txn 2147484734
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 16
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 96
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 192
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 300
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 528
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 644
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 748
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 860
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 988
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 1108
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 1232
    Oct 5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 1404
    Oct 5 08:24:38 rusty sieve[18879]: entered bc_action_emit with filelen: 1508
    Oct 5 08:24:38 rusty master[18370]: process 18879 exited, status 0

    I have passed this on as a probable bug in the plugin, but I wanted to see if there
    was anything I can do about it (or if I had anything wrong) as well.

    imapd.conf:
    # server conf
    servername: rusty.morningside.edu
    umask: 077
    reject8bit: no
    quotawarn: 90
    timeout: 30
    poptimeout: 10
    # singleinstancestore: yes

    username_to_lower: yes
    lmtp_downcase_rcpt: yes
    lmtp_over_quota_perm_failure: yes

    altnamespace: yes

    # user conf
    postmaster: postmaster
    admins: cyrus cyrusadm

    # directory and file locations
    configdirectory: /var/spool/cyrus-imap
    partition-default: /var/spool/cyrus-imap
    sievedir: /var/spool/cyrus-imap/sieve
    sievenotifier: mailto

    sendmail: /usr/sbin/sendmail

    # authentication
    allowanonymouslogin: no
    allowplaintext: yes
    sasl_mech_list: plain
    sasl_minimum_layer: 0
    sasl_pwcheck_method: saslauthd

    # new user automated creates
    autocreate_sieve_script: /var/spool/cyrus-imap/sieve/phpscript
    autocreate_sieve_compiledscript: /var/spool/cyrus-imap/sieve/phpscript.bc
    generate_compiled_sieve_script: yes
    sieve_maxscriptsize: 64
    sieve_maxscripts: 50

    autocreateinboxfolders: Spam
    autosubscribeinboxfolders: Spam
    autocreatequota: 51200
    createonpost: yes

    # security certificate information
    tls_cert_file: /etc/ssl/certs/imap.morningside.edu.crt
    tls_key_file: /etc/ssl/certs/imap.morningside.edu.key
    tls_ca_file: /etc/ssl/certs/imap.morningside.edu.ca-bundle

    cyrus.conf:
    # standard standalone server implementation

    START {
      # do not delete this entry!
      recover cmd="ctl_cyrusdb -r"

      # this is only necessary if using idled for IMAP IDLE
    # idled cmd="idled"
    }

    # UNIX sockets start with a slash and are put into /var/spool/cyrus-imap/socket
    SERVICES {
      # add or remove based on preferences
      imap cmd="imapd" listen="imap" prefork=0
      imaps cmd="imapd -s" listen="imaps" prefork=0
      pop3 cmd="pop3d" listen="pop3" prefork=0
      pop3s cmd="pop3d -s" listen="pop3s" prefork=0
      sieve cmd="timsieved" listen="sieve" prefork=0

      # at least one LMTP is required for delivery
    # lmtp cmd="lmtpd" listen="lmtp" prefork=0
      lmtpunix cmd="lmtpd" listen="/var/spool/cyrus-imap/socket/lmtp" prefork=0

      # this is only necessary if using notifications
      notify cmd="notifyd" listen="/var/spool/cyrus-imap/socket/notify"
    proto="udp" prefork=1
    }

    EVENTS {
      # this is required
      checkpoint cmd="ctl_cyrusdb -c" period=15

      # this is only necessary if using duplicate delivery suppression
      delprune cmd="ctl_deliver -E 3" at=0400

      # this is only necessary if caching TLS sessions
      tlsprune cmd="tls_prune" at=0400

    Thanks in advance,

    Mike

    ----
    Cyrus Home Page: http://cyrusimap.web.cmu.edu/
    Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
    List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
    

  • Next message: Elizabeth Schwartz: "Cyrus, Solaris 10, ZFS? (and NIS?)"





    Hosted Email Solutions

    Invaluement Anti-Spam DNSBLs



    Powered By FreeBSD   Powered By FreeBSD