Ok, no problem. Thanks for the update. I noticed another user sent a message with the same error so I guess I'm not the only one. I couldn't get any versions of perdition to work with managesieve proxying. Hope you find the bug!

On Thu, Apr 7, 2011 at 7:55 PM, Simon Horman <horms@verge.net.au> wrote:
Sorry Jesse,

I haven't had time to look into it yet, but if you are getting a sig 11
then there is a bug.

On Thu, Apr 07, 2011 at 10:47:14AM -0400, Jesse Jarzynka wrote:
> Hello Simon, any updates on this? Is this a confirmed bug that you are still
> working on? Just want to make sure it's not something I'm doing wrong,
> thanks! -Jesse
>
> On Tue, Apr 5, 2011 at 1:38 PM, Jesse Jarzynka <jesse@jessejoe.com> wrote:
>
> > Simon,
> >
> > I apologize but this was wrong. For some reason I turned off managesieve on
> > the destination server, probably something I was testing. I am now
> > confirming that perdition still exits on signal 11 when trying to
> > authenticate managesieve same as before with the latest mercurial code. It
> > still seems to send me to the right server and I see the managesieve
> > response from the correct managesieve server, and then I get the exit 11:
> >
> > Apr  5 13:35:47 perdition-dev perdition.managesieve[21571]: Connect:
> >  10.30.40.197:49949->10.30.40.163:4190
> > Apr  5 13:35:48 perdition-dev perdition.managesieve[21571]: SELF:
> > "\"IMPLEMENTATION\" \"perdition\"\r\n\"SIEVE\" \"comparator-i;octet
> > comparator-i;ascii-casemap fileinto reject envelope encoded-character
> > vacation subaddress comparator-i;ascii-numeric relational regex imap4flags
> > copy include variables body enotify environment mailbox date\"\r\n\"SASL\"
> > \"PLAIN\"\r\n\"NOTIFY\" \"mailto\"\r\n\"VERSION\" \"1.19-rc4\"\r\nOK
> > \"perdition ready on perdition-dev.localnet.sys 0002b4d8\"\r\n"
> > Apr  5 13:35:50 perdition-dev perdition.managesieve[21571]: CLIENT:
> > "AUTHENTICATE \"PLAIN\"
> > \"AHRlc3RhY2NvdW50MDBAbG9jYWxuZXQuY29tAFRlY2g5OTk=\"\r\n"
> > Apr  5 13:35:50 perdition-dev perdition.managesieve[21571]:
> > username_add_domain: username_add_domain 0 1
> > Apr  5 13:35:51 perdition-dev perdition.managesieve[21571]:
> > username_add_domain: username_add_domain 0 4
> > Apr  5 13:35:51 perdition-dev perdition.managesieve[21571]: REAL:
> > "\"IMPLEMENTATION\" \"dovecot\"\r\n\"SIEVE\" \"comparator-i;octet
> > comparator-i;ascii-casemap fileinto reject envelope encoded-character
> > vacation subaddress comparator-i;ascii-numeric relational regex imap4flags
> > copy include variables body enotify environment mailbox date spamtest
> > spamtestplus virustest\"\r\n\"SASL\" \"PLAIN
> > LOGIN\"\r\n\"STARTTLS\"\r\n\"NOTIFY\" \"mailto\"\r\n\"VERSION\"
> > \"1.0\"\r\nOK \"Dovecot ready.\"\r\n"
> > Apr  5 13:35:51 perdition-dev perdition.managesieve[21571]: Exiting on
> > signal 11
> >
> > On Mon, Apr 4, 2011 at 10:52 AM, Jesse Jarzynka <jesse@jessejoe.com>wrote:
> >
> >> On Sat, Apr 2, 2011 at 6:09 PM, Simon Horman <horms@verge.net.au> wrote:
> >> > # apt-get build-dep perdition
> >>
> >> The build-dep must've grabbed something I was missing because I was
> >> able to compile it after that.
> >>
> >> I'm not getting the same error anymore, so that's good! I'm still not
> >> getting the right server from ldap with managesieve though. Here's and
> >> example of my IMAP auth working correctly and adding the right server:
> >>
> >> Apr  4 10:42:35 perdition-dev perdition.imap4[17368]: Starting
> >> perdition version=1.19-rc4 protocol=IMAP4
> >> Apr  4 10:42:35 perdition-dev perdition.imap4[17368]: add_domain="",
> >> authenticate_in=off, authenticate_timeout=1800, bind_address="",
> >> client_server_specification=off,
> >> config_file="/home/jjarzynka/perdition.conf", connection_limit=0,
> >> connection_logging=on, connect_relog=300, debug=on,
> >> domain_delimiter="@", explicit_domain="", group="root",
> >> imap_capability="IMAP4 IMAP4REV1", inetd_mode=off,
> >> listen_port="imap2", log_facility="mail", log_passwd="never",
> >> login_disabled=off, lower_case="",
> >> managesieve_capability=""IMPLEMENTATION" "perdition"  "SIEVE"
> >> "comparator-i;octet comparator-i;ascii-casemap fileinto reject
> >> envelope encoded-character vacation subaddress
> >> comparator-i;ascii-numeric relational regex imap4flags copy include
> >> variables body enotify environment mailbox date"  "SASL" "PLAIN"
> >> "NOTIFY" "mailto"  "VERSION" "1.19-rc4"",
> >> map_library="/usr/lib/libperditiondb_ldap.so.0.0.0",
> >>
> >> map_library_opt="ldap://ldap.localnet.sys/ou=accounts,dc=localnet,dc=com?mail,mailHost,port?one?(mail=%s)",
> >> no_bind_banner=off, no_daemon=off, no_lookup=off, tcp_keepalive=off,
> >> nodename="perdition-dev", ok_line="You are so in",
> >> outgoing_port="imap2", outgoing_server="",
> >> pid_file="/var/run/perdition.imap4s/perdition.imap4s.pid",
> >> pop_capability="UIDL.USER", protocol="IMAP4", server_resp_line=off,
> >> strip_domain="", timeout=1800, username="root",
> >> username_from_database=off, query_key="", quiet=off (mask=0x00000400
> >> 00000000)
> >> Apr  4 10:42:35 perdition-dev perdition.imap4[17368]: ssl_mode="",
> >> ssl_ca_file="", ssl_ca_path="/usr/etc/perdition/perdition.ca/",
> >> ssl_ca_accept_self_signed="off",
> >> ssl_cert_file="/usr/etc/perdition/perdition.crt.pem",
> >> ssl_cert_accept_expired="off", ssl_cert_not_yet_valid="off",
> >> ssl_cert_self_signed="off", ssl_cert_verify_depth=9,
> >> ssl_key_file="/usr/etc/perdition/perdition.key.pem",
> >> ssl_listen_ciphers="", ssl_outgoing_ciphers="",
> >> ssl_no_cert_verify="off", ssl_no_client_cert_verify="off",
> >> ssl_no_cn_verify="off" ssl_passphrase_fd=0,
> >> ssl_passphrase_file="(null)", (ssl_mask=0x00000000)
> >> Apr  4 10:42:35 perdition-dev perdition.imap4[17370]:
> >> vanessa_socket_daemon_setid: uid=0 euid=0 gid=0 egid=0
> >> Apr  4 10:42:41 perdition-dev perdition.imap4[17371]: Connect:
> >> 10.30.40.197:34045->10.30.40.163:143
> >> Apr  4 10:42:41 perdition-dev perdition.imap4[17371]: SELF:   "* OK
> >> [CAPABILITY IMAP4 IMAP4REV1] perdition ready on
> >> perdition-dev.localnet.sys 0002b0cf\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: CLIENT: "01
> >> login testaccount00@localnet.com PASSWORD\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]:
> >> username_add_domain: username_add_domain 0 1
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]:
> >> username_add_domain: username_add_domain 0 4
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: REAL:   "* OK
> >> [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT
> >> THREAD=REFERENCES SORT QUOTA IDLE] Courier-IMAP ready. Copyright
> >> 1998-2003 Double Precision, Inc.  See COPYING for distribution
> >> information.\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: SELF:   "flim07
> >> CAPABILITY\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: REAL:   "*
> >> CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT
> >> THREAD=REFERENCES SORT QUOTA IDLE\r\nflim07 OK CAPABILITY
> >> completed\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: SELF:   "flim08
> >> LOGIN {26}\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: REAL:   "+ OK\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: SELF:
> >> "testaccount00@localnet.com {7}\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: REAL:   "+ OK\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: SELF:
> >> "PASSWORD\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: REAL:   "flim08
> >> OK LOGIN Ok.\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: SELF:   "01 OK
> >> You are so in\r\n"
> >> Apr  4 10:42:51 perdition-dev perdition.imap4[17371]: Auth:
> >> 10.30.40.197:34045->10.30.40.163:143 client-secure=plaintext
> >> authorisation_id=NONE authentication_id="testaccount00@localnet.com"
> >> server="maildrop-dovecot-dev.localnet.sys:imap2" protocol=IMAP4
> >> server-secure=plaintext status="ok"
> >>
> >>
> >> So you can see it finds the correct mail server for this user as
> >> "maildrop-dovecot-dev.localnet.sys" and forwards my connection there.
> >> Here is my output when using managesieve on the latest mercurial code
> >> and the same config file now:
> >>
> >>
> >> Apr  4 10:47:24 perdition-dev perdition.managesieve[17401]: Starting
> >> perdition version=1.19-rc4 protocol=MANAGESIEVE
> >> Apr  4 10:47:24 perdition-dev perdition.managesieve[17401]:
> >> add_domain="", authenticate_in=off, authenticate_timeout=1800,
> >> bind_address="", client_server_specification=off,
> >> config_file="/home/jjarzynka/perdition.conf", connection_limit=0,
> >> connection_logging=on, connect_relog=300, debug=on,
> >> domain_delimiter="@", explicit_domain="", group="root",
> >> imap_capability="IMAP4 IMAP4REV1", inetd_mode=off,
> >> listen_port="sieve", log_facility="mail", log_passwd="never",
> >> login_disabled=off, lower_case="",
> >> managesieve_capability=""IMPLEMENTATION" "perdition"  "SIEVE"
> >> "comparator-i;octet comparator-i;ascii-casemap fileinto reject
> >> envelope encoded-character vacation subaddress
> >> comparator-i;ascii-numeric relational regex imap4flags copy include
> >> variables body enotify environment mailbox date"  "SASL" "PLAIN"
> >> "NOTIFY" "mailto"  "VERSION" "1.19-rc4"",
> >> map_library="/usr/lib/libperditiondb_ldap.so.0.0.0",
> >>
> >> map_library_opt="ldap://ldap.localnet.sys/ou=accounts,dc=localnet,dc=com?mail,mailHost,port?one?(mail=%s)",
> >> no_bind_banner=off, no_daemon=off, no_lookup=off, tcp_keepalive=off,
> >> nodename="perdition-dev", ok_line="You are so in",
> >> outgoing_port="sieve", outgoing_server="",
> >> pid_file="/var/run/perdition.imap4s/perdition.imap4s.pid",
> >> pop_capability="UIDL.USER", protocol="MANAGESIEVE",
> >> server_resp_line=off, strip_domain="", timeout=1800, username="root",
> >> username_from_database=off, query_key="", quiet=off (mask=0x00000400
> >> 00000000)
> >> Apr  4 10:47:24 perdition-dev perdition.managesieve[17401]:
> >> ssl_mode="", ssl_ca_file="",
> >> ssl_ca_path="/usr/etc/perdition/perdition.ca/",
> >> ssl_ca_accept_self_signed="off",
> >> ssl_cert_file="/usr/etc/perdition/perdition.crt.pem",
> >> ssl_cert_accept_expired="off", ssl_cert_not_yet_valid="off",
> >> ssl_cert_self_signed="off", ssl_cert_verify_depth=9,
> >> ssl_key_file="/usr/etc/perdition/perdition.key.pem",
> >> ssl_listen_ciphers="", ssl_outgoing_ciphers="",
> >> ssl_no_cert_verify="off", ssl_no_client_cert_verify="off",
> >> ssl_no_cn_verify="off" ssl_passphrase_fd=0,
> >> ssl_passphrase_file="(null)", (ssl_mask=0x00000000)
> >> Apr  4 10:47:24 perdition-dev perdition.managesieve[17403]:
> >> vanessa_socket_daemon_setid: uid=0 euid=0 gid=0 egid=0
> >> Apr  4 10:47:44 perdition-dev perdition.managesieve[17407]: Connect:
> >> 10.30.40.197:44134->10.30.40.163:4190
> >> Apr  4 10:47:44 perdition-dev perdition.managesieve[17407]: SELF:
> >> "\"IMPLEMENTATION\" \"perdition\"\r\n\"SIEVE\" \"comparator-i;octet
> >> comparator-i;ascii-casemap fileinto reject envelope encoded-character
> >> vacation subaddress comparator-i;ascii-numeric relational regex
> >> imap4flags copy include variables body enotify environment mailbox
> >> date\"\r\n\"SASL\" \"PLAIN\"\r\n\"NOTIFY\" \"mailto\"\r\n\"VERSION\"
> >> \"1.19-rc4\"\r\nOK \"perdition ready on perdition-dev.localnet.sys
> >> 0002b4d8\"\r\n"
> >> Apr  4 10:47:49 perdition-dev perdition.managesieve[17407]: CLIENT:
> >> "AUTHENTICATE \"PLAIN\"
> >> \"AHRlc3RhY2NvdW50QGxvY2FsbmV0LmNvbQB0ZXN0\"\r\n"
> >> Apr  4 10:47:49 perdition-dev perdition.managesieve[17407]:
> >> username_add_domain: username_add_domain 0 1
> >> Apr  4 10:47:50 perdition-dev perdition.managesieve[17407]:
> >> vanessa_socket_client_src_open: getaddrinfo dst: "deleted" "sieve":
> >> Name or service not known
> >> Apr  4 10:47:50 perdition-dev perdition.managesieve[17407]: main:
> >> vanessa_socket_client_open
> >> Apr  4 10:47:53 perdition-dev perdition.managesieve[17407]: SELF:
> >> "NO \"failed: Could not connect to server\"\r\n"
> >> Apr  4 10:47:53 perdition-dev perdition.managesieve[17407]: Auth:
> >> 10.30.40.197:44134->10.30.40.163:4190 client-secure=plaintext
> >> authorisation_id=NONE authentication_id="testaccount@localnet.com"
> >> server="deleted:sieve" protocol=MANAGESIEVE server-secure=plaintext
> >> status="failed: Could not connect to server"
> >>
> >>
> >> This time it gets the mail server as "deleted:sieve" instead of
> >> "maildrop-dovecot-dev.localnet.sys". Shouldn't it be using my mail
> >> server defined in my ldap lookup like IMAP does? It does appear you
> >> have fixed whatever bug was disconnecting me immediately though.
> >> Thanks for your continued help. -Jesse
> >>
> >
> >