[PERDITION-USERS] IMAP Authentication fails with Mailenable as real server

Hi, I'm trying to get Perdition to work as proxy for Mailenable IMAP server. Apparently Mailenable has a broken IMAP implementation which makes IMAP between Perdition and Mailenable unusable. POP3 works fine, though. A short description follows: Perdition tries to authenticate like this (the double quotes are added by me): "flim08 LOGIN {usernamelen}" and receives from Mailenable: "+ go ahead" It then sends the username like this: "adi2(a)aditestingwin.com.au {passwordlen}" and receives: "flim08 BAD LOGIN- Invalid username or password." then sends the password: "123qweasdzxc" and Mailenable replies with: "123qweasdzxc" At this point Perdition closes the TCP connection and logs: perdition.imap4[27975]: Fatal error authenticating user. Exiting child. Hence, the IMAP session looks like this (Mailenable responds): * OK IMAP4rev1 server ready at 07/18/12 10:04:13 flim07 CAPABILITY * CAPABILITY IMAP4rev1 IMAP4 AUTH=LOGIN AUTH=CRAM-MD5 IDLE CHILDREN flim07 OK CAPABILITY completed flim08 LOGIN {25} + go ahead adi2(a)aditestingwin.com.au {12} flim08 BAD LOGIN- Invalid username or password. 123qweasdzxc 123qweasdzxc BAD UNKNOWN Command The IMAP authentication works with Mailenable if I manually use this authentication string: aaa login adi2(a)aditestingwin.com.au 123qweasdzxc Is there a way to configure Perdition to use this authentication method rather than the one it currently uses? -- Adi Pircalabu, System Administrator Discount Domain Name Services Pty Ltd, a Total Internet Company PO Box 887, Hawthorn Vic 3122, Australia, T +61 3 9815 6868 Ask me about cloud hosting services