scribe2: INBOX.Drafts
autosubscribe3: INBOX.Sent
dict:
expire: db:/var/lib/dovecot/expire.db
Thanks in advanced.
Thorsten Habich
Hi!
I don't think there's a good way to solve this currently.
I also think so, we "solved" the problem by putting the complete
homepath in LDAP.
pass_attrs =
uid=user,userPassword=password,mailMessageStore=home=%$/telefonica.de/%Ln,mailFilterStore=sieve_dir=%$/telefonica.de/%Ln
Do
Hi!
I'm pretty unsure this is only a TB3 problem. Saw the same result with
TB 2.0, but I'm unsure if this was after changing something on the
server. After 2 days of mailproblems we downgraded back to Dovecot 1.1
yesterday and no one reported this bug since this downgrade.
Greetings,
Thorste
Hi!
I upgraded some of our systems to dovecot 1.2.10
now I noticed that some of my messages are marked
as unread. This disappears after reopening the folder
again.
Greetings,
Thorsten
Timo Sirainen wrote:
What was the old version?
1.1.6
No, those only apply to TB 3.0.0 and 3.0.1 (apparently fixed for 3.0.2)...
glad to hear this is fixed
But the problem sounds really similar. Maybe Thorsten('s users) also
happened to recently upgrade to 3.0?
no, it was my own mail
Hi!
Something new about that?
We also checked the Loadbalancer config depending on the connection losts
using mutt, they are exactly the same as the one which works with 1.1.6
fine.
So I strongly believe it is a dovecot 1.2.10 problem.
Greetings
Thorsten
Hi!
I downgraded again and found the same result. Seems that this problem
occurs after
version change after first access the problem seems to be gone.
But there is still the disconnecting problem with mutt.
Greetings
Thorsten
Timo Sirainen wrote:
On Thu, 2010-02-04 at 14:28 +0100, Thorsten Habich wrote:
Hi!
I downgraded again and found the same result. Seems that this problem
occurs after
version change after first access the problem seems to be gone.
But there is still the disconnecting problem with mutt
Timo Sirainen wrote:
I've no idea. No one was complaining about these problems before TB3 was
released.. You could look at the IMAP traffic and see if Dovecot actually
replies something wrong.
It's just right after the upgrade. After this, the problem seem to
disappear.
Maybe the users