[Bug 581718] Re: dovecot upgrade purposely breaks working configuration

2010-05-19 Thread Ante Karamatić
1) it was working by pure luck; it was never suposed to work 2) actually, there is; look at comment #6 3) for a reason - security 4) ?? It's not ignoring the issue. It's just that you are using 'mailbox' path, which starts with 'maildir:' as a home variable. That's just wrong, weather dovecot

[Bug 581718] Re: dovecot upgrade purposely breaks working configuration

2010-05-18 Thread Lionel Dricot
I don't set the home field manually. It's set by Mandriva Directory Server. I think that the error come from that mail and home are, on my config, un I find it very wrong to consider that as a user fault because : 1) it was working previously and al least one existing configuration (mine) was

[Bug 581718] Re: dovecot upgrade purposely breaks working configuration

2010-05-17 Thread Lionel Dricot
in my config, I've the location configured as : mail_location = maildir:/home/mail/%u -- dovecot upgrade purposely breaks working configuration https://bugs.launchpad.net/bugs/581718 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to

[Bug 581718] Re: dovecot upgrade purposely breaks working configuration

2010-05-17 Thread Lionel Dricot
chuck : the link is *not* a patch to solve the issue. The link is a patch that introduced the issue itself. The question is : what should people do if they have this error ? And why was this patch introduced ? -- dovecot upgrade purposely breaks working configuration

[Bug 581718] Re: dovecot upgrade purposely breaks working configuration

2010-05-17 Thread Chuck Short
Thanks ill see if I can get this backported for lucid. chuck ** Changed in: dovecot (Ubuntu) Importance: Undecided = Medium ** Changed in: dovecot (Ubuntu) Status: New = Confirmed -- dovecot upgrade purposely breaks working configuration https://bugs.launchpad.net/bugs/581718 You

Re: [Bug 581718] Re: dovecot upgrade purposely breaks working configuration

2010-05-17 Thread Ante Karamatić
On 17.05.2010 15:15, Lionel Dricot wrote: mail_location = maildir:/home/mail/%u Looking at the docs: Upgrading Dovecot v1.1 to v1.2 == * Relative home directory paths are giving errors now. They were never supported, but earlier they just didn't usually cause

[Bug 581718] Re: dovecot upgrade purposely breaks working configuration

2010-05-17 Thread Ante Karamatić
On 17.05.2010 15:12, Lionel Dricot wrote: Upgrading a working dovecot from karmic to lucid. http://wiki.dovecot.org/MailLocation Use only absolute paths. Even if relative paths would appear to work, they might just as well break some day. Unless we find that you are using only absolute

[Bug 581718] Re: dovecot upgrade purposely breaks working configuration

2010-05-17 Thread Lionel Dricot
I'm using absolute path. The problem is that the path was given by LDAP with : user_attrs = mailbox=home (this is what is recommended in the documentation) It seems that, for whatever reason this string is passed directly to the code and used as home. But because it starts with maildir:, it

[Bug 581718] Re: dovecot upgrade purposely breaks working configuration

2010-05-17 Thread Ante Karamatić
home isn't a mail_location path. It's home path. In your ldap mailbox should look like this: /home/mail/x...@xyz.com If it looks like: maildir:/home/mail/x...@xyz.com then you are using that wrong. http://wiki.dovecot.org/UserDatabase/ExtraFields - those are extra fields that are supported.

[Bug 581718] Re: dovecot upgrade purposely breaks working configuration

2010-05-17 Thread Ante Karamatić
Marking bug as invalid since it shouldn't have wored anyway. ** Changed in: dovecot (Ubuntu) Status: Incomplete = Invalid -- dovecot upgrade purposely breaks working configuration https://bugs.launchpad.net/bugs/581718 You received this bug notification because you are a member of Ubuntu