[PERDITION-USERS] Managesieve segfault bug. Test case and work around included

Hi, I've tried perdition_1.19~rc4-3 but I still get a segfault. I'm running cyrus 2.4.8, and I can avoid the segfault under two scenarios: 1) With "sasl_mech_list: LOGIN PLAIN" and "allowplaintext: no" in my cyrus config 2) With "sasl_mech_list: PLAIN" and "allowplaintext: yes" in my cyrus config In my environment, we have a client which can't do TLS, so a special sieve daemon which allows plaintext listens on local host for it. Originally #2 also offered LOGIN and I that's how I ran into the segfault. It seems to be something in the sieve banner parsing. I've made a python script to act as a sieve server (see attached): ./server.py Then I run perdition: perdition.managesieve -d --no_daemon --listen_port=2006 -C --outgoing_server=127.0.0.1:2005 -f '' --pid_file /tmp/sieve.pid Then I telnet to 2006 and paste : AUTHENTICATE "PLAIN" "<real auth string>" I either get an OK or a segfault in perdition. server.py will cycle through the specified banners, so you can continue to telnet to try each banner test case out. Let me know if you need any further information. Thanks. -- Steven Kurylo