Re: How to skip errors on doveadm backup for migration ?

[Christoph Adomeit]

Hi Farokh,

yes, imapsync is great. I tested it myself and it fetched all the mails.

Only Problem: Imapsync will loose the Email-UIDs so all Mail will be downloaded 
again by the clients after Server switch.

dsync is able to presere the Uids.

Thanks
  Christoph

On Sun, Jan 10, 2016 at 05:42:53PM -0500, Farokh Irani wrote:
> If both servers are using IMAP, maybe imapsync
> (http://imapsync.lamiral.info) would be an easier way to go...
> 
> Farokh
> 
> MCF Software...simply dependably engineered
> For all your computer and networking needs including hosting solutions
> for every need.
> Phone: 845-735-0210
> Cell: 914-262-1594
> 
> 
> 
> >Christoph Adomeit 
> >January 8, 2016 at 05:50
> >Hi there,
> >
> >I have to migrate data out of a very old (debian 4) and buggy cyrus
> >mailserver.
> >About 40 Users with 20 Messages each.
> >
> >Doveadm backup works quite well and gives me most of the mails. About
> >every 100.000 Mail
> >cannot be exported by cyrus. I do not want to bother about these errors.
> >Maybe it is filesystem, maybe it is memory leak, or cyrus bug or whatever.
> >
> >My problem is that doveadm backup exits with an error if it cannot read a
> >mail.
> >
> >
> >
> >Is there some way or option to make doveadm backup just skip the errors
> >and continue with the next message ?
> >
> >I want to use doveadm sync because it preserves the uids of the mails.
> >
> >Imapsync works great but does not prserve uids.
> >
> >cyrus2dovecot is not an option because it does not work incremental and
> >conversion would take far too long.
> >
> >Any ideas what I can do ?
> >
> >Thanks
> >Christoph

-- 
Christoph Adomeit
GATWORKS GmbH
Reststrauch 191
41199 Moenchengladbach
Sitz: Moenchengladbach
Amtsgericht Moenchengladbach, HRB 6303
Geschaeftsfuehrer:
Christoph Adomeit, Hans Wilhelm Terstappen

christoph.adom...@gatworks.de Internetloesungen vom Feinsten
Fon. +49 2166 9149-32  Fax. +49 2166 9149-10

sieve - content checks with special chars

[Hajo Locke]

Hello,

currently i try subject tests with special chars and german umlauts öäü etc.

if header :contains "subject" [" äää"] {
  fileinto "umlauts";
}

iam surprised, this is working out of the box. great! in procmail i had 
to add a second step by manual coding the needle with perl.

is sieve reliable at this kind of tests or are there some special cases?
iam worried about this, because it was to easy.  confusing... ;)

Thanks,
Hajo

Re: sieve - content checks with special chars

[Robert Schetterer]

Am 11.01.2016 um 11:24 schrieb Hajo Locke:
> Hello,
> 
> currently i try subject tests with special chars and german umlauts öäü
> etc.
> 
> if header :contains "subject" [" äää"] {
>   fileinto "umlauts";
> }
> 
> iam surprised, this is working out of the box. great! in procmail i had
> to add a second step by manual coding the needle with perl.
> is sieve reliable at this kind of tests or are there some special cases?
> iam worried about this, because it was to easy.  confusing... ;)
> 
> Thanks,
> Hajo

I mail fail, but i think working with special chars was fixed some time
ago and is now default on


i found some info here

http://wiki2.dovecot.org/Pigeonhole/Sieve/Troubleshooting#Mailbox_Names_with_non-ASCII_Characters_Cause_Problems



Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

Re: sieve - content checks with special chars

[Stephan Bosch]

Op 11-1-2016 om 11:24 schreef Hajo Locke:

Hello,

currently i try subject tests with special chars and german umlauts 
öäü etc.


if header :contains "subject" [" äää"] {
  fileinto "umlauts";
}

iam surprised, this is working out of the box. great! in procmail i 
had to add a second step by manual coding the needle with perl.

is sieve reliable at this kind of tests or are there some special cases?
iam worried about this, because it was to easy.  confusing... ;)


https://tools.ietf.org/html/rfc5228#section-2.7.2

Pigeonhole implements this. Any deviant behavior is a bug that will be 
fixed.



Regards,

Stephan.

Re: Dovecot code repository moved to Github (dovecot-cvs list revived)

[Stephan Bosch]

Op 12/9/2015 om 5:32 PM schreef Timo Sirainen:
> I'm not sure yet if we should continue pushing commit emails to dovecot-cvs 
> list or if Github's internal notifications are enough. In any case 
> dovecot-cvs list isn't working right now.

As you may have noticed, the dovecot-cvs mailing list is working again.

Regards,

Stephan.

password schemes when crypt() has no DES

[Stuart Henderson]

https://github.com/dovecot/core/commit/54a1b3574acab5f778843f7f1e04d2d26d61a852
fixed a 'doveadm pw' crash "when trying to use CRYPT scheme when crypt() doesn't
support DES" by testing to see if crypt would generate a DES password and, if
not, disabling the scheme.

I'm using Dovecot on OpenBSD with bcrypt passwords stored in LDAP as
"{CRYPT}$2b$...". OpenLDAP is built with --enable-crypt which takes the
same approach as Dovecot of just passing to crypt(), so before the above
commit, both programs were able to authenticate.

(Changing the scheme value stored in the ldap passdb to BLF-CRYPT would
fix Dovecot but break things for other programs including OpenLDAP itself).

For now I went with a dirty patch to get things working again, does
anyone have an idea for a nicer fix?  Thanks.


--- src/auth/password-scheme-crypt.c.orig   Fri Jan  8 01:04:13 2016
+++ src/auth/password-scheme-crypt.cFri Jan  8 01:23:35 2016
@@ -111,7 +111,12 @@ static const struct {
const char *salt;
const char *expected;
 } sample[] = {
+#ifdef __OpenBSD__
+   { "08/15!test~4711", "$2a$04$0123456789abcdefABCDEF",
+ "$2a$04$0123456789abcdefABCDE.N.drYX5yIAL1LkTaaZotW3yI0hQhZru" },
+#else
{ "08/15!test~4711", "JB", "JBOZ0DgmtucwE" },
+#endif
{ "08/15!test~4711", "$2a$04$0123456789abcdefABCDEF",
  "$2a$04$0123456789abcdefABCDE.N.drYX5yIAL1LkTaaZotW3yI0hQhZru" },
{ "08/15!test~4711", "$5$rounds=1000$0123456789abcdef",
@@ -124,8 +129,13 @@ static const struct {
 
 /* keep in sync with the sample struct above */
 static const struct password_scheme crypt_schemes[] = {
+#ifdef __OpenBSD__
{ "CRYPT", PW_ENCODING_NONE, 0, crypt_verify,
+ crypt_generate_blowfisch },
+#else
+   { "CRYPT", PW_ENCODING_NONE, 0, crypt_verify,
  crypt_generate_des },
+#endif
{ "BLF-CRYPT", PW_ENCODING_NONE, 0, crypt_verify,
  crypt_generate_blowfisch },
{ "SHA256-CRYPT", PW_ENCODING_NONE, 0, crypt_verify,

No SSL on some users

[Jonas Björklund]

Hello,

Is there a way to allow only certain users on IMAP/POP3 without SSL?
Im running MySQL backend.

/Jonas