Homepage | Products | OX Knowledge Base | Support | Try Now | Contact | Company
OX Logo
Results 1 to 4 of 4

Thread: Sieve error

  1. #1

    Default Sieve error

    I get this error on the filter config page:

    09.05.2009 05:54-->Fehlermeldung: Error while communicating with the sieve server 127.0.0.1 at port 2000 for user admin in context 1 (MAIL_FILTER-0015, 1463450843-144)
    Sieve seems to be working correctly when calling manually:

    ox6:/var/log # telnet localhost 2000
    Trying 127.0.0.1...
    Connected to localhost.
    Escape character is '^]'.
    "IMPLEMENTATION" "Cyrus timsieved v2.2.12"
    "SASL" "LOGIN"
    "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex"
    "STARTTLS"
    OK
    Doing an strace on a preforked copy of timesieved, I got this:

    write(1, "\"IMPLEMENTATION\" \"Cyrus timsieved v2.2.12\"\r\n\"SASL\" \"LOGIN\"\r\n\"SIEVE\" \"fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex\"\r\n\"STARTTLS\"\r\nOK\r\n", 193) = 193
    time(NULL) = 1241842464
    select(1, [0], NULL, NULL, {1800, 0}) = 1 (in [0], left {1800, 0})
    time(NULL) = 1241842464
    read(0, "LOGOUT\r\n", 4096) = 8
    write(1, "OK \"Logout Complete\"\r\n", 22) = 22
    munmap(0xb6573000, 16384) = 0
    close(6) = 0
    munmap(0xb657c000, 32768) = 0
    munmap(0xb7b0a000, 98304) = 0
    munmap(0xb6584000, 22568960) = 0
    munmap(0xb7b22000, 663552) = 0
    munmap(0xb7fa6000, 24576) = 0
    open("/dev/null", O_RDWR) = 6
    shutdown(0, 0 /* receive */) = -1 ENOTCONN (Transport endpoint is not connected)
    dup2(6, 0) = 0
    shutdown(1, 0 /* receive */) = -1 ENOTCONN (Transport endpoint is not connected)
    dup2(6, 1) = 1
    shutdown(2, 0 /* receive */) = -1 ENOTCONN (Transport endpoint is not connected)
    dup2(6, 2) = 2
    close(6) = 0
    exit_group(0) = ?
    Doing the same with master, there's no attempt by OX to do anything further ...

    What am I missing here?

    Using sieveshell worked ... at least I was able to authenticate and got the appropriate message in the logfile about the user being logged in ... something I haven't yet seen from the OX login process ...

  2. #2

    Default

    Is the error message you provided the only thing you can see in the log? Normally there should be more information what exactly happen, like errors during login etc.

    Also it might help if you could provide a tcpdump of the communication between OX and Sieve, but be aware that passwords will be contained in the dump so choose another one before creating the dump.

    Regards,

    Dennis

  3. #3

    Default

    did the dump, from what I can tell, all OX does at the moment is:

    - 3way handshake
    - Sieve sends out its Hello message
    - OX ACKs the hello packet
    - OX sends "LOGOUT"
    - Sieve ACKs the logout packet
    - 3way disconnect

    Guess the problem is this:

    Caused by: com.openexchange.jsieve.exceptions.OXSieveHandlerE xception: The server doesn't suppport PLAIN authentication
    Can't find the cause for that, though ... I have another Install that I did on Debian that works fine, can't find any essential differences ATM ... (sasl_mech_list has both PLAIN and LOGIN)

    Edit: Fixed it ... problem was that I didn't have the cyrus-sasl-plain package installed in the SLES setup ... Works fine now ...
    Last edited by Garry; 05-12-2009 at 11:27 AM.

  4. #4

    Default [Resolved] Sieve error

    Nice to hear that it works for you now...

    Regards,

    Dennis

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •