4 Jun
2011
4 Jun
'11
1:45 p.m.
Hi Mark,
On Thu, Jun 02, 2011 at 04:02:16PM -0700, Mark Hamilton wrote:
I have a perdition server that is proxying for a
Roundcube webmail
as well as all the various other email clients out there. On
occasion while a user is moving around their mail folders or opening
emails perdition will disconnect from the dovecot servers.
I get this error in the dovecot servers log:
dovecot: IMAP(username): Connection closed
That is the only thing I can see anywhere that indicates something
wrong. Most clients complain about a connection problem of some
kind then go on with life. Roundcube is a pain because when it
happens it kills the session and logs the user out. I updated to
the latest perdition and the issue hasn't gone away.
I am using Centos 5 which comes with dovecot 1.0.7 installed. I
know that is an old version but I don't really want to mess with it
and make it break if I update other parts of the server using the
supported yum repos. I also am not sure it has anything to do with
the dovecot server since if I point roundcube or another client
directly at the dovecot server without going though perdition it
works with no issue. I would like to find a solution with perdition
since I have built a mail system around it using 9 different mail
hosts and one central point to check your mail. I will look into
updating the dovecot servers if that is what it takes but I would
like to avoid it if possible until they are updated by the usual yum
update.
I have looked for ip limits but I don't see any in that version of
dovecot. If I add the 'mail_max_userip_connections = 100' to the
config file dovecot will not even start so this version does not
support it. I moved the connection_limit in perdition up way past
what the number of connections that could possibly hit is and it
didn't change the behavior.
One thing that I noticed that is a little different is when the
client is connecting directly it logs in using "A0002 AUTHENTICATE
PLAIN somelongstringofnumbersandletters". When it is going through
perdition it logs in like this:
This is very likely related to the problem.
Perdition doesn't support PLAIN authentication for IMAP,
although I freely admit that it should.
To be more specific. I did implement SASL authentication
for managesieve but it still hasn't been wired up for IMAP.
I don't recall it there was a specific reason for that.
More likely it was just an oversight.
flim08 LOGIN {7}
+ OK
username {8}
+ OK
password
flim08 OK Logged in.
I don't know if that makes any difference.
Thank you for any assistance.
Mark
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users