headers
Albert Dengg | 1 Apr 2008 02:11
Picon
Picon

Re: authentication troubles

On Sun, Mar 30, 2008 at 05:20:55PM +0200, Albert Dengg wrote:
> hi
> 
> i have a strange problem with my dovecot installtion:
> i configured it to accept digest-md5 authentication only but for some
> reason mailclients (i tried mutt and thunderbird so far) want to log
> with PLAIN (which fails of course).
> authentication basically works, e.g. if i explicitly set
> set imap_authenticators="digest-md5
> in .muttrc everything works...
> any idea what is going wrong?
> 
> config attached below

i forgot to add:
i tried with both dovecot 1.0.rc15 from debian etch as well as a newer
version (1.0.13 from backports.org) with the same result in both cases.

yours
albert
Permalink | Reply | 0 comments |
headers
Mark Nienberg | 1 Apr 2008 02:57
Favicon

Re: public folders fchown error

junk <at> mc1.mccarthy.ac wrote:
> At first glance, that appears to have worked.  I made a new group
> mailpublic, I've chown'd all dovecot-shared and the entire public mail
> folder to root.mailpublic, set the mail_access_groups to mailpublic, and
> that seems to have worked.
> 
> Just out of curiousity, is there a place this is documented that I should
> have found?  I coulnd't find it in the wiki, and if there was more info on
> it, I'd be happy to put something together for the shared mailboxes page.

Did you see this one?
http://wiki.dovecot.org/SharedMailboxes

Mark
Permalink | Reply | 0 comments |
headers
Chris Richards | 1 Apr 2008 03:29

Re: DoveCot IMAP and "inconsistent state" messages

Scott Silva wrote:
> on 3-31-2008 1:31 PM Chris Richards spake the following:
>> Charles Marcus wrote:
>>> On 3/31/2008, Chris Richards (gizmo <at> giz-works.com) wrote:
>>>> Dovecot is version 1.0.rc15 
>>>
>>> Upgrade please - rc15 is very old...
>>>
>>
>> Err, that's the newest thing in the yum repository, and if I go 
>> compiling code that isn't 'official' (i.e. doesn't come from the yum 
>> repository), I'll get myself in an awful lot of trouble.  Management 
>> seems to be under the strange belief that only code from the 
>> repository it is 'safe'.
>>
>> So, the question is, how hard do I need to fight in order to get this 
>> done?
>>
>> Later,
>> Chris
>>
> If you are using a RHEL or clone, atrpms.net has a newer version in 
> their repository.
>
Oh bloody hell.  WHY am I fighting with a dovecot version that is 1 1/2 
flippin' years old?!?!

Suits.  I HATES 'em, I tells ya!

I'll be back when I've figured out how to convince the CTO that this
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bill Cole | 1 Apr 2008 04:14

Re: DoveCot IMAP and "inconsistent state" messages

At 3:31 PM -0500 3/31/08, Chris Richards wrote:
>Charles Marcus wrote:
>>On 3/31/2008, Chris Richards (gizmo <at> giz-works.com) wrote:
>>>Dovecot is version 1.0.rc15
>>
>>Upgrade please - rc15 is very old...
>>
>
>Err, that's the newest thing in the yum repository, and if I go 
>compiling code that isn't 'official' (i.e. doesn't come from the yum 
>repository), I'll get myself in an awful lot of trouble.  Management 
>seems to be under the strange belief that only code from the 
>repository it is 'safe'.
>
>So, the question is, how hard do I need to fight in order to get this done?

That's a question about the competence of the people maintaining that 
repository. Presumably these would be the people who blessed a 
pre-release version of Dovecot almost 18 months ago, in a period when 
such versions were being released every few days *due to bugs*, and 
who have not updated their build at any time since. It seems to me 
that these are not people who should be tasked or trusted with being 
the gatekeepers of software deployment, as that seems to be 
demonstrably beyond their competence.

I don't say that as a slur on the people running the CentOS project, 
but rather to note that the packaging service they offer is unsuited 
to the role your management has given it in your company's 
environment.
(Continue reading)

Permalink | Reply | 5 comments |
headers
Ron Avriel | 1 Apr 2008 08:46
Picon
Favicon

Wrong UIDs returned from mailbox_transaction_commit_get_uids()

Hi,

Wrong UIDs are returned from mailbox_transaction_commit_get_uids() in dovecot-1.1.rc3.

The problem is in:

int mailbox_transaction_commit(struct mailbox_transaction_context **t)
{
    uint32_t tmp;

    return mailbox_transaction_commit_get_uids(t, &tmp, &tmp, &tmp);
}

It should be:

int mailbox_transaction_commit(struct mailbox_transaction_context **t)
{
    uint32_t tmp1, tmp2, tmp3;

    return mailbox_transaction_commit_get_uids(t, &tmp1, &tmp2, &tmp3);
}

After this fix it works OK.

Thanks,
Ron

      ____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.  
http://tc.deals.yahoo.com/tc/blockbuster/text5.com
(Continue reading)

Permalink | Reply | 1 comment |
headers
Joseba Torre | 1 Apr 2008 08:58
Picon
Picon
Favicon

Re: DoveCot IMAP and "inconsistent state" messages

Hi,

El Martes, 1 de Abril de 2008 a las 04:14, Bill Cole escribió:
> That's a question about the competence of the people maintaining that
> repository. Presumably these would be the people who blessed a
> pre-release version of Dovecot almost 18 months ago, in a period when
> such versions were being released every few days *due to bugs*, and
> who have not updated their build at any time since. It seems to me
> that these are not people who should be tasked or trusted with being
> the gatekeepers of software deployment, as that seems to be
> demonstrably beyond their competence.

RedHat (and CentOS) has his own policy about releases, and more or less it 
is: "no update will break a working instalation". So they try to port any 
security patches to their running versions -and this is a lot of work, they 
have their own forked version of almost any package!-, but almost never add 
any new funcionality. This policy has one great point: it's easy to 
understand, and it gives few surprises. And this is great most of the times.

Pre-1.0 Dovecot is the kind of software that doesn't fit well in that policy: 
a lot of changes, and no standard stable version. So they chose one 
version -1.0rc15 in this case-, because their other option was not including 
dovecot. That's exactly why I'm compiling dovecot from source, but I usually 
like the default policy.

Aaaaaaaaaagur.
--

-- 
Joseba Torre. CIDIR Bizkaia.
Permalink | Reply | 4 comments |
headers
Jack | 1 Apr 2008 09:38
Picon

Confusion of Sieve filter scripts and the file separator. (Amatuer Siever)

Hello,

I have just been playing around with sieve filters to split up all my 
incoming mail into the correct directories. I have created some 
subdirectories to put mailing list emails in and just want to check if 
my thinking is correct. I am using namespaces with the '/' character as 
the separator. When creating the fileinto line on my sieve scripts I 
thought I would have to use the '/' character to separate the folders 
(as horde mail also does), but that doesn't work (and produces a 
"Invalid folder" error) instead I must use the '.' character. I am using 
the dovecot deliver module and managesieve for my sieve stuff (dovecot 
1.0.13). I am just wondering if this is the correct behaviour or if it 
is a bug of sorts.

Cheers.

From,
Jack
Permalink | Reply | 1 comment |
headers
Timo Sirainen | 1 Apr 2008 10:20
Picon
Picon
Favicon

Re: DoveCot IMAP and "inconsistent state" messages

On Mon, 2008-03-31 at 15:10 -0500, Chris Richards wrote:
> Dovecot is version 1.0.rc15

I agree with others that it would be a good idea to upgrade from rc15,
but..

> Mar 31 14:00:58 myserver dovecot: IMAP(me): Maildir /home/me/.Maildir 
> sync: UID inserted in the middle of mailbox (85953 > 85053, file = 
> msg.XL7B:2,)

This is a procmail configuration problem:
http://wiki.dovecot.org/MailboxFormat/Maildir#procmail
Permalink | Reply | 8 comments |
headers
Timo Sirainen | 1 Apr 2008 10:24
Picon
Picon
Favicon

Re: Wrong UIDs returned from mailbox_transaction_commit_get_uids()

On Mon, 2008-03-31 at 23:46 -0700, Ron Avriel wrote:
> Hi,
> 
> Wrong UIDs are returned from mailbox_transaction_commit_get_uids() in dovecot-1.1.rc3.

Where do you see this causing problems?

> The problem is in:
> 
> int mailbox_transaction_commit(struct mailbox_transaction_context **t)
> {
>     uint32_t tmp;
> 
>     return mailbox_transaction_commit_get_uids(t, &tmp, &tmp, &tmp);
> }
> 
> 
> It should be:
> 
> int mailbox_transaction_commit(struct mailbox_transaction_context **t)
> {
>     uint32_t tmp1, tmp2, tmp3;
> 
>     return mailbox_transaction_commit_get_uids(t, &tmp1, &tmp2, &tmp3);
> }

How/where does this help? The tmp values are ignored in any case, so I
don't think this is the right fix for it.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Timo Sirainen | 1 Apr 2008 10:45
Picon
Picon
Favicon

Re: Bug in db-ldap.c with Dovecot1.1rc3

On Thu, 2008-03-13 at 17:00 -0700, richs <at> whidbey.net wrote:
> When db_ldap_result_iterate_next_all() runs, "quotaKb" is encountered, 
> which causes "ctx->template" to be set.
> 
> On the next iteration, "uidNumber" is encountered, but "ctx->template" 
> is still set, causing the "uid" value to be prepended with "*:storage=".
> 
> This is reflected by an error in the log as:
> 
> 	Invalid UID value '*:storage=121212'
> 
> This can be fixed by adding a line after 1118 to src/auth/db-ldap.c:
> 
> 	ctx->template = NULL;

Thanks, fixed: http://hg.dovecot.org/dovecot-1.1/rev/15fbff736ab9
Permalink | Reply | 0 comments |

Gmane