Re: 2.2.18: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted.
Hello An update: I managed to sync mailboxes between the 2 servers using imapsync, which worked perfectly. I suspect there's a bug lurking in the imapc code, because why would an external utility work flawlessly with 2 dovecot servers, but dovecot's own syncing client won't? Regards Dale On 6 August 2015 at 12:10, Dale Gallagher wrote: > Hello > > Could my previously reported error above have something to do with the > IMAP path prefix? It's not configured on either of the previously mentioned > servers. > > I see a similar error, which may be related, when trying to sync using > offlineimap.py: > > Folder INBOX [acc: test_account]: > ERROR: ERROR in syncfolder for test_account folder INBOX > > Thanks > Dale > > > On 5 August 2015 at 16:59, Dale Gallagher > wrote: > >> Hello >> >> I have 2.2.18 built with: >> >> ./configure \ >> --prefix="$prefix" \ >> --bindir="$prefix/bin" \ >> --sbindir="$prefix/bin" \ >> --sysconfdir="/etc" \ >> --with-storages="maildir,imapc,pop3c" \ >> --without-vpopmail \ >> --without-ldap >> >> I'm attempting to sync (backup) from another Dovecot server running >> version 2.0.21: >> >> Both servers don't have no explicit namespaces configured and both are >> using the Maildir storage plugin. >> >> doveadm -Dv -o imapc_user=remote_user -o imapc_host=source.host -o >> imapc_port=993 -o imapc_ssl=imaps -o imapc_password=remote_pass -o >> imapc_features="rfc822.size fetch-headers" backup -R -u local_user imapc: >> >> All seems to go well, showing local and remote mailbox syncing without >> errors, then finally: >> >> dsync(mcg): Debug: brain M: Deleting mailbox 'INBOX' (GUID >> 59023c2a911dc255842bd09efc50): UIDVALIDITY changed (1355416734 -> >> 1438784913) >> dsync(mcg): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't >> be deleted. >> >> No mail is synced to the local server (2.2.18) after this error halts >> execution. >> >> What should I be looking for, in terms of possible causes of this error? >> >> I've tried syncing on a completely fresh mailbox, which hasn't been >> accessed by a mail client and the same error occurs. >> >> I've seen similar reports of this error before, without clear solutions / >> suggestions. >> >> Help would be greatly appreciated. >> >> Thanks >> >> >> >> >
Re: 2.2.18: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted.
Hello Could my previously reported error above have something to do with the IMAP path prefix? It's not configured on either of the previously mentioned servers. I see a similar error, which may be related, when trying to sync using offlineimap.py: Folder INBOX [acc: test_account]: ERROR: ERROR in syncfolder for test_account folder INBOX Thanks Dale On 5 August 2015 at 16:59, Dale Gallagher wrote: > Hello > > I have 2.2.18 built with: > > ./configure \ > --prefix="$prefix" \ > --bindir="$prefix/bin" \ > --sbindir="$prefix/bin" \ > --sysconfdir="/etc" \ > --with-storages="maildir,imapc,pop3c" \ > --without-vpopmail \ > --without-ldap > > I'm attempting to sync (backup) from another Dovecot server running > version 2.0.21: > > Both servers don't have no explicit namespaces configured and both are > using the Maildir storage plugin. > > doveadm -Dv -o imapc_user=remote_user -o imapc_host=source.host -o > imapc_port=993 -o imapc_ssl=imaps -o imapc_password=remote_pass -o > imapc_features="rfc822.size fetch-headers" backup -R -u local_user imapc: > > All seems to go well, showing local and remote mailbox syncing without > errors, then finally: > > dsync(mcg): Debug: brain M: Deleting mailbox 'INBOX' (GUID > 59023c2a911dc255842bd09efc50): UIDVALIDITY changed (1355416734 -> > 1438784913) > dsync(mcg): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't > be deleted. > > No mail is synced to the local server (2.2.18) after this error halts > execution. > > What should I be looking for, in terms of possible causes of this error? > > I've tried syncing on a completely fresh mailbox, which hasn't been > accessed by a mail client and the same error occurs. > > I've seen similar reports of this error before, without clear solutions / > suggestions. > > Help would be greatly appreciated. > > Thanks > > > >
2.2.18: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted.
Hello I have 2.2.18 built with: ./configure \ --prefix="$prefix" \ --bindir="$prefix/bin" \ --sbindir="$prefix/bin" \ --sysconfdir="/etc" \ --with-storages="maildir,imapc,pop3c" \ --without-vpopmail \ --without-ldap I'm attempting to sync (backup) from another Dovecot server running version 2.0.21: Both servers don't have no explicit namespaces configured and both are using the Maildir storage plugin. doveadm -Dv -o imapc_user=remote_user -o imapc_host=source.host -o imapc_port=993 -o imapc_ssl=imaps -o imapc_password=remote_pass -o imapc_features="rfc822.size fetch-headers" backup -R -u local_user imapc: All seems to go well, showing local and remote mailbox syncing without errors, then finally: dsync(mcg): Debug: brain M: Deleting mailbox 'INBOX' (GUID 59023c2a911dc255842bd09efc50): UIDVALIDITY changed (1355416734 -> 1438784913) dsync(mcg): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. No mail is synced to the local server (2.2.18) after this error halts execution. What should I be looking for, in terms of possible causes of this error? I've tried syncing on a completely fresh mailbox, which hasn't been accessed by a mail client and the same error occurs. I've seen similar reports of this error before, without clear solutions / suggestions. Help would be greatly appreciated. Thanks
[Dovecot] dovecot-lda delivery to Maildir/cur as 'seen'?
Hi I've added a server-side feature where authenticated customers sending through our SMTP server have their outbound mail copied to their Sent folder (like Gmail does). The delivery script called by qmail calls dovecot-lda to deliver it to the user's Sent folder. The problem now, is that the Sent folder shows the mail as unread, which MUAs flag (and notify, in the case of some). I've searched the docs and mailing list, but can't find an option to tell dovecot-lda to mark the mail being delivered, as seen/read. If I've missed something, please let me know. If not, then I think it might be a good idea to add a feature to dovecot-lda permitting one to specify delivery to the ./cur subfolder of a Maildir, instead of ./new. Thanks
Re: [Dovecot] Questions regarding Dovecot's POP3 implementation
2009/1/21 Brandon Lamb : > Oh, I also setup the dovecot LDA and configured exim to deliver to it > so that it will write out the W= flag and updates the dovecot indexes > on delivery (im pretty sure im correct here). Thanks Brandon. It seems I should try it out, especially given that using the dovecot LDA includes W= in the filename. I'll report back on this thread once testing is done.
[Dovecot] Questions regarding Dovecot's POP3 implementation
Hi all I'm considering moving over my POP3 service from qmail-pop3d to Dovecot for the following reasons: - Support for Maildir++ which I have yet to implement - Already using Dovecot for IMAP, so makes sense i.t.o Maildir++ - Support for SQL based user authentication My primary concerns are performance and security. Before I go down that route of migrating away from qmail-pop3d, I'd appreciate some answers and feedback on the following. There is mention of the Maildir filename extension W= for virtual file size here: http://wiki.dovecot.org/POP3Server However, I can't find any MDAs which support writing the filename in this format. Maildrop seems to support S= only? If Dovecot is only able to read W= in the filename, I would imagine that it might make sense to have an MDA like Maildrop write the message to disk, replacing all LF with CR+LF and finally write the filename with identical S= and W= filename extensions included? Example: Maildrop replaces all LFs with CR+LF in incoming message. Maildrop writes message as: 1035478339.27041_118.foo.org,S=1000,W=1000 (where 1000 is the file's RFC822.SIZE) Then Dovecot doesn't have to calculate virtual message sizes. I've also found this thread: http://markmail.org/message/oznf2f7m7hvsxqn6 ... which suggests changing mail_get_virtual_size to mail_get_physical_size in src/pop3/client.c Would this read the size from S=, or do a stat()? 5. Does anyone use Dovecot pop3 service on thousands of mailboxes and if so, what specific tweaks / setup do you use? Thanks Dale
Re: [Dovecot] logging IMAP username rather than UNIX username
Hi Timo
2008/10/22 Timo Sirainen <[EMAIL PROTECTED]>:
> That means your authentication changes the username.
>
>> passdb checkpassword {
>> args = /var/qmail/bin/qmail-vauth
>> }
>
> Most likely qmail-vauth changes USER environment to vmail. If you can't
> edit qmail-vauth directly, create a wrapper script that unsets the USER
> environment before calling Dovecot's checkpassword-reply.
Yes, you're spot on! USER is changed. Thanks for the heads-up, I'll
see if writing a wrapper works, without messing with the fact that the
process has to run as the vmail user.
Thanks
Dale
Re: [Dovecot] logging IMAP username rather than UNIX username
My auth section config is:
auth default {
mechanisms = plain
passdb checkpassword {
args = /var/qmail/bin/qmail-vauth
}
userdb prefetch {
}
user = auth
}
2008/10/22 Dale Gallagher <[EMAIL PROTECTED]>:
> Hi there
>
> I'd like to change my setup to log the _actual_ IMAP user's login,
> rather than the UNIX username. My system uses a virtual uid setup with
> qmail, where the mailboxes are owned by the 'vmail' user and
> authentication is via checkpassword using user%domain (ie email, just
> with % instead of @). So dovecot is recording _all_ logins as:
>
>imap-login: Login: user=, method=PLAIN, rip=127.0.0.1,
> lip=127.0.0.1, secured
>
> I have the following log format specified:
>
>login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c
>
> I have also tried:
>
>login_log_format_elements = user=<[EMAIL PROTECTED]> method=%m rip=%r
> lip=%l %c
>
> However, this results in a log file entry of:
>
>imap-login: Login: user=, method=PLAIN, rip=127.0.0.1,
> lip=127.0.0.1, secured
>
> How do I configure dovecot to log the _actual_ username which the
> client supplies during authentication?
>
> Thanks
> Dale
>
[Dovecot] logging IMAP username rather than UNIX username
Hi there I'd like to change my setup to log the _actual_ IMAP user's login, rather than the UNIX username. My system uses a virtual uid setup with qmail, where the mailboxes are owned by the 'vmail' user and authentication is via checkpassword using user%domain (ie email, just with % instead of @). So dovecot is recording _all_ logins as: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured I have the following log format specified: login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c I have also tried: login_log_format_elements = user=<[EMAIL PROTECTED]> method=%m rip=%r lip=%l %c However, this results in a log file entry of: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured How do I configure dovecot to log the _actual_ username which the client supplies during authentication? Thanks Dale
[Dovecot] IMAP vs system username logging with checkpassword auth
Hi
After upgrading to dovecot 1.0.7 I noticed that the actual username is
no longer logged, but rather the system user (in my case 'vmail')
under which my virtual set-up runs. Now I'm unable to see which
virtual users log in. Any pointers on how to configure dovecot to log
the actual username given during the IMAP dialogue would be
appreciated.
My dovecot.conf includes the following:
auth default {
mechanisms = plain
passdb checkpassword {
args = /var/qmail/bin/qmail-vauth
}
userdb prefetch {
}
user = auth
}
An example logfile entry:
2007-11-03 15:41:56.027191500 dovecot: Info: imap-login: Login:
user=, method=PLAIN, rip=192.168.0.141, lip=192.168.0.10, TLS
