Hi
I just installed the Elastix 2.0 and try to set up the mail server as I did in 1.6, but when I try to add an account, it tells me an error that " IMAP login error " and won't continue! I activated the email dashboard in the "System" page, it says that "IMAP: Connection Error," seems like the same problem, I run the postfix check command, no error detected.

Also when I try to delete a domain, I clicked the "Delete" button but nothing happens!?

Does anyone has solutions for these? Why can it work in 1.6 but not 2.0?!

Best Regards
Michael Lu

Same Problem for me elastix 2.0 stable

Unfortunately Elastix 2.0 (stable) was in fact only considered stable for two days, and even then only by a very few involved, try upgrading to 2.0.1 (which IMHO is still not actually stable), PLEASE file a bug report in the bug-tracker at the bottom of this page, maybe someone will listen, but then again, maybe not

regards

dicko

Go to folder /var/www/html/configs edit file email.conf.php - change HOST to 'lo' - it works:)

And if that works effectively vkacisco , then it remains a bug, please file it and its resolution for the sake of everyone else.

thank you


dicko

Continue of trouble - it create accounts, but i can`t login to imap..Any ideas?

Continue - i changed system name from system to system.ru in Network Network parameters - now i also can`t create account with any interface, and also i can`t login to imap from cyradm. What i need to change in config?

I have been using Elastix 2.0.1 since it was made awaiable. All the modules are working well except the email section. I can use postfix as pop3 & imap bu itself. The webmail module of elastix also works partly ie if i login as user only it works. but a user@abc.com gives imap error. cannot create any account you get imap error:
Maillog reports sucess for login of user, for user@abc.com gives imap: badlogin ....plaintext cyrus SASL(-13) authentication failure check pass failed
Messages gives imap : auxpropfunc error invalid parameter supplied sql_select option missing no mechanism availabe.

I too am experiencing the same issue. Any ideas for a workaround? I tried the ones listed above, but with no luck.

To my knowledge, it is apparently an ongoing bug in 2.0.? and in MHO a very serious one, to this point in time it is unacknowledged by PaloSanto, there will be no work around until PaloSanto fixes it, please post your concern in the bug-tracker link available below, until you (and everyone else) does, it won't be fixed, the developers just don't come here, you are basically unheard until you add you voice to the many who have this problem. Any bitches and whines are just wasted in these fora, as I have suggested before, nobody from PaloSanto cares to monitor these fora, go figure . . .


(you are not the only one)


(Bob, did you read this (I assume so) ?, you intrinsically put yourself here. . . , but I'm glad you are back your diplomacy is sorely needed)

dicko