Re: [Dovecot] Sieve (randomly?) flagging messages as \\Seen \\Deleted
On 04/04/14 18:31, Stephan Bosch wrote:
> Sieve doesn't add flags unless it is explicitly told to do so. The
> behavior you describe is therefore quite bizarre, especially since using
> removeflag seems to provide a workaround.
I know, or I wouldn't be so puzzled...
> What does your full Sieve script look like?
Mine is relatively long, although quite straightforward: just foldering
stuff in several places based on List-Id and applying Thunderbird
tags/labels based on a few conditions.
But the other user's one is way shorter:
require ["regex","fileinto"];
# rule:[rule0]
if anyof (header :contains "To" "XXX", header :contains "From" "xxx",
header :regex "Subject" "xxx", [...])
{
fileinto "folder1";
stop;
}
# rule:[rule1]
if anyof (header :contains "To" "YYY", header :contains "From" "YYY",
header :contains "Received" "YYY")
{
fileinto "folder1";
stop;
}
> What is your full configuration?
Not much longer than what I already provided...
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4
auth_mechanisms = plain login
default_vsz_limit = 512 M
first_valid_gid = 8
first_valid_uid = 201
last_valid_gid = 8
last_valid_uid = 201
mail_plugins = mail_log notify
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date ihave vacation-seconds editheader
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
mail_debug = yes
mail_log_events = flag_change save
mail_log_fields = uid box msgid flags subject
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
sieve_extensions = +vacation-seconds +editheader
sieve_vacation_default_period = 2d
sieve_vacation_dont_check_recipient = yes
sieve_vacation_max_period = 30d
sieve_vacation_min_period = 2s
sieve_vacation_use_original_recipient = no
}
postmaster_address = postmas...@bofhland.org
protocols = " imap lmtp sieve pop3"
service auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0660
user = postfix
}
}
service imap-login {
inet_listener imap {
address = 127.0.0.1
port = 143
}
inet_listener imaps {
port = 993
ssl = yes
}
process_min_avail = 0
}
service imap {
idle_kill = 30 mins
process_limit = 1024
vsz_limit = 1 G
}
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
service managesieve-login {
inet_listener sieve {
address = 127.0.0.1
port = 4190
}
}
service pop3-login {
inet_listener pop3s {
port = 995
ssl = yes
}
}
ssl_cert = Do you perhaps return a sieve_before setting from userdb?
Nope.
Also, if there was one defined somehow/somewhere, I'd see something in
sieve's debug (when trying to open it, compiling, etc), but there's nothing.
I can tell more: searching for a global workaround, in the meanwhile I
added a sieve_before script (not shown in the config above) doing only this:
require ["imap4flags"];
removeflag "\\Deleted";
removeflag "\\Seen";
As a result, the problem disappeared for all users... :-|
(and yeah, the execution of this sieve_before appears in my debug logs, now)
Re: [Dovecot] Sieve (randomly?) flagging messages as \\Seen \\Deleted
On 4/3/2014 1:28 PM, Emanuele Balla (aka Skull) wrote: [...] > The problem in short: > > Messages I expected to find in certain folders were simply not there, > although sieve logs reported them as delivered in those same folders. > By manually inspecting the maildir, I actually found the messages, but > they were all flagged as \\Seen + \\Deleted and therefore not displayed > by the MUA (ThunderBird in my case). [...] > In order to try restricting what may be causing the issue, I added... > > removeflag "\\Deleted"; > removeflag "\\Seen"; > > ...to the rule sending messages to the dedicated folder cited above for > my mailbox. > The problem apparently disappeared for me as long as I kept those in place. > > This should mean (I suppose) that the decision of flagging messages that > way is taken before the users' sieve scripts are applied (sort of > "hidden sieve_before"). [...] > So, a question for people knowing pigeonhole's internals: does it ever > choose to mark messages as described above for any reason? If yes, I may > be triggering this behavior with something I recently added/modified, > and at least I'll have something to focus my investigation on. :-| Sieve doesn't add flags unless it is explicitly told to do so. The behavior you describe is therefore quite bizarre, especially since using removeflag seems to provide a workaround. What does your full Sieve script look like? What is your full configuration? Do you perhaps return a sieve_before setting from userdb? Regards, Stephan.
Re: [Dovecot] Unknown setting: plugin after fresh install
Hi,
Am 2014-04-04 17:34, schrieb Philipp Resch:
> Hi,
>
> without having any further information, it sounds as if for example a
> brace ( {} ) is
> not closed correctly. You may want to check that any block is complete.
you are right, forgot to uncomment a closing } in 20-managesieve.conf
Nice caught.
Thanks,
Patrik
--
PRIVACY IS NOT A CRIME! So please encrypt your emails using PGP/GnuPG.
My PGP Key-ID: 0x42D6DEA0 / 0x28B8F6E242D6DEA0
PGP Fingerprint: 4C1F ED51 047A D0E2 6C20 F3F7 28B8 F6E2 42D6 DEA0
signature.asc
Description: OpenPGP digital signature
Re: [Dovecot] Unknown setting: plugin after fresh install
Hi,
without having any further information, it sounds as if for example a
brace ( {} ) is
not closed correctly. You may want to check that any block is complete.
Cheers,
Philipp
Am 04.04.2014 16:10, schrieb Patrik Karisch:
> Hi guys,
>
> I've installed dovecot 2.1.7 on a Debian Wheezy, tweaked some parameters
> little bit, but I can't restart it (dovecot -n also fails) and get this
> error:
>
> doveconf: Fatal: Error in configuration file
> /etc/dovecot/conf.d/90-acl.conf line 11: Unknown setting: plugin
> doveconf: Error: managesieve-login: dump-capability process returned 89
>
> Wether I uncomment this plugin line, I get the error on another file
> (example 90-quote.conf). Seems a little bit weird. What have I done false?
>
> Thanks Patrik
Re: [Dovecot] dsync deleted my mailbox - what did I do wrong?
Hi - where did I fail (ignoring the backups, please. That's .. something I know) From the man page: "backup - Backup mails from default mail location to location2 (or vice versa, if -R parameter is given). No changes are ever done to the source location. Any changes done in destination are discarded." The last sentence describes what happened to you: all new mail on the new machine is a "change" and was discarded (by deleting new mail.) If I'm not mistaken, this is correct behaviour for backup mode - you get exact copy of the source side (maildir:/tmp/mail_backup) on destination side (d...@darklajid.de) - Can I use dsync ... for backups? I don't think that this is a good idea after yesterday night? AFAIK you can safely use it to make the backup. I'm not sure if it can be reliably used to restore data (don't think so but I'm not an expert.) I'd use doveadm import for that.
[Dovecot] Unknown setting: plugin after fresh install
Hi guys, I've installed dovecot 2.1.7 on a Debian Wheezy, tweaked some parameters little bit, but I can't restart it (dovecot -n also fails) and get this error: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-acl.conf line 11: Unknown setting: plugin doveconf: Error: managesieve-login: dump-capability process returned 89 Wether I uncomment this plugin line, I get the error on another file (example 90-quote.conf). Seems a little bit weird. What have I done false? Thanks Patrik -- PRIVACY IS NOT A CRIME! So please encrypt your emails using PGP/GnuPG. My PGP Key-ID: 0x42D6DEA0 / 0x28B8F6E242D6DEA0 PGP Fingerprint: 4C1F ED51 047A D0E2 6C20 F3F7 28B8 F6E2 42D6 DEA0 signature.asc Description: OpenPGP digital signature
[Dovecot] Use 1 userdb and LDAP passdb for mailbox without allow_all_users
Hello everybody,
I have a little pb with dovecot. I have been read on archive of dovecot mailing
list that it's possible to have 1 static userdb with LDAP passdb
(http://www.dovecot.org/list/dovecot/2010-November/055193.html) but when I
try it I have an error message and my message is on the queue with "temporary
failure"
auth: Debug: master in: USER#0111#011quentinv#011service=lda
auth: Debug: password(quentinv): passdb doesn't support credential lookups
auth: Error: static(quentinv): passdb doesn't support lookups, can't verify
user's existence
auth: Debug: userdb out: FAIL#0111
lda: Error: user quentinv: Auth USER lookup failed
lda: Fatal: Internal error occurred. Refer to server log for more information.
auth: Debug: master in: USER#0111#011quentinv#011service=lda
auth: Debug: password(quentinv): passdb doesn't support credential lookups
auth: Error: static(quentinv): passdb doesn't support lookups, can't verify
user's existence
auth: Debug: userdb out: FAIL#0111
lda: Error: user quentinv: Auth USER lookup failed
lda: Fatal: Internal error occurred. Refer to server log for more information.
My imap connexion havn't any pb but LDA yes.
Here is my dovecot.conf
# 2.2.10: /usr/local/dovecot/etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-5-686 i686 Debian 7.4 ext3
auth_debug = yes
base_dir = /var/run/dovecot/
disable_plaintext_auth = no
first_valid_gid = 8
first_valid_uid = 15
listen = *
login_greeting = Bienvenue sur courriel
login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c
mail_fsync = never
mail_gid = 8
mail_location =
maildir:/var/mail/%n:CONTROL=/var/mail/%n/control:INDEX=/var/mail/%n/index
mail_log_prefix = "%Us(%u): "
mail_privileged_group = mail
mail_uid = 15
passdb {
args = /usr/local/dovecot/etc/dovecot-ldap.conf
driver = ldap
}
plugin {
quota = maildir
quota_rule = *:storage=3145728
quota_rule2 = Trash:storage=+102400
quota_warning = storage=90%% /usr/local/dovecot/bin/quota-warning.sh 90
}
protocols = imap
service auth {
executable = /usr/local/dovecot/libexec/dovecot/auth
}
service imap-login {
chroot = login
executable = /usr/local/dovecot/libexec/dovecot/imap-login
process_limit = 400
process_min_avail = 3
service_count = 1
user = dovecot
vsz_limit = 32 M
}
service imap {
drop_priv_before_exec = no
executable = /usr/local/dovecot/libexec/dovecot/imap
process_limit = 512
}
service pop3-login {
chroot = login
process_limit = 256
process_min_avail = 3
service_count = 1
user = dovecot
vsz_limit = 32 M
}
service pop3 {
drop_priv_before_exec = no
process_limit = 512
}
ssl_cert =
ssl_cipher_list =
ssl_key = mailto:postmas...@coria.fr>
rejection_reason = Your message to <%t> was automatically rejected : %n%r
rejection_subject = Automatically rejected mail
sendmail_path = /usr/lib/sendmail
}
And my dovecot-ldap.conf
tls = no
uris= ldap://x.x.x.x:389
ldap_version= 3
auth_bind = yes
dn = userdn
dnpass = pass
base= ou=Users,dc=quentin,dc=local
scope = subtree
deref = never
pass_filter =
(&(SamAccountName=%n)(objectClass=person)(!(userAccountControl=514)))
pass_attrs =uid=user, userPassword=password
default_pass_scheme = CRYPT
Sincerly,
Quentin.
[signature]
<>
Re: [Dovecot] dsync replication questions
Hi On 04/04/2014 03:38 PM, Simon Fraser wrote: > It does help, thank you. Do you also know what the '-f' option does? According to the dsync-man page it: Makes dsync run in "full sync" mode rather than "fast sync" mode. In fast sync mode dsync might skip syncing a mailbox, if both locations had modified it equally many times (i.e. highest-modseqs were equal), but with different changes. br, Teemu Huovila
Re: [Dovecot] dsync replication questions
On Fri, 2014-04-04 at 15:34 +0300, Teemu Huovila wrote: > -d Use a default location for the replica. As far as I can tell this is > obtained from userdb variable mail_replica. > -N Sync all (visible?) namespaces (only makes sense when syncing with a > remote host, with potentially different namespaces) > (instead of either -n or -x ) > -l Use a dsync lock file when syncing and the timeout for locking. > -U Update replicator server on the status of the replication > > For replicating in a multiple server configuration, they sound like a good > idea to me. > > Hope this helps a little, It does help, thank you. Do you also know what the '-f' option does? Simon. -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
Re: [Dovecot] dsync replication questions
On 04/04/2014 12:42 PM, Nikolaos Milas wrote: > Anyone please? > > How can we determine whether we need to configure > "replication_dsync_parameters = -d -N -l 30 -U" as indicated on the wiki2 (or > some variation thereof) or not? I am definitely not Timo, but I will try a short answer based on my limited familiarity with the dsync replication functionality and code. -d Use a default location for the replica. As far as I can tell this is obtained from userdb variable mail_replica. -N Sync all (visible?) namespaces (only makes sense when syncing with a remote host, with potentially different namespaces) (instead of either -n or -x ) -l Use a dsync lock file when syncing and the timeout for locking. -U Update replicator server on the status of the replication For replicating in a multiple server configuration, they sound like a good idea to me. Hope this helps a little, Teemu Huovila
Re: [Dovecot] mdbox with mail_attachment_dir per user in 2.2.12
Hello Alex, overriding it from user database works perfectly. Thanks On Fri, 4 Apr 2014 11:22:37 +0200 Axel Luttgens wrote: > Le 3 avr. 2014 à 15:12, Pavel Stano a écrit : > > > Hello, > > > > we have 2 netapp arrays with 2 volumes and we need to store our mail > > data in one or other volume for every user. > > We want keep data for one user in one volume only. > > > > So we would like to have 2 separate mail_attachment_dir, one on > > every volume. > > But in latest version 2.2.12 it look like it is only possible to set > > one global mail_attachment_dir. > > > > I have an idea with 2 separate dovecot instances per machine with > > different mail_attachment_dir. Or it is possible to somehow specify > > it per user ? > > Hello Pavel, > > I don't know whether that setting may be customized or if must have a > single constant value. > > Anyway, have you tried to make use of variables for setting its value? > Or, if more relevant in your case, by overriding it from your user > database (see section "Overriding settings" at > http://wiki2.dovecot.org/UserDatabase/ExtraFields). > > Axel -- [ Ohodnotte kvalitu mailu: http://nicereply.com/websupport/Stano/ ] Pavel Stano | Troubleshooter http://WebSupport.sk *** BERTE A VYCHUTNAVAJTE *** signature.asc Description: PGP signature
Re: [Dovecot] imap / IPv6 problems?
On 4/4/2014 12:07 μμ, Egbert wrote: When sending an email it*sometimes* takes ages before the process finishes. The process seems to hang in moving the message to the sent items" folder". When I disable the IPv6 stack in the network config (this is MS Windows 7), the hanging process immedialetely completes! This makens me think that is has to do with the IP stacks. Another observed effect is a long "rotating wheel" when just klicking on an imap folder before the listing in the right pane updates. Here the same trick solves the problem. Something must be incomplete in your local IPv6 configuration. Have you configured IPv6 DNS servers? Are they working? Troubleshoot your IPv6 network connectivity (check configuration, firewalls, etc.). The behaviour you are describing is typical on systems which are struggling to use the IPv6 protocol (because it has higher priority) and they cannot due to some problem; when IPv6 connectivity attempts timeout, IPv4 is used. We are using Dovecot for years with IPv6 with various clients and we have no problems at all. Nick
Re: [Dovecot] dsync replication questions
On 4/4/2014 1:17 μμ, Alan McGinlay wrote: It does appear to be completely undocumented, We would appreciate if Timo can kindly provide us with -at least- some details! I tried looking in the source code but just ended up going in circles (i'm not familiar with it at all). I faced the same difficulties... :-( Nick
Re: [Dovecot] dsync replication questions
On 2014-04-04 11:42, Nikolaos Milas wrote: On 31/3/2014 12:03 μμ, Simon Fraser wrote: On Fri, 2014-03-28 at 11:58 +0200, Nikolaos Milas wrote: >Question 2a: What do options "-d -N -l 30 -U" signify in >"replication_dsync_parameters = -d -N -l 30 -U"? I'd also be interested to know the answer to this part. I found mention of the '-f' option, and adding '-f' to that list appears to have fixed a replication race condition I was having, but I can't find out a note of what it does. There is no one who knows that? Or no documentation whatsoever? Anyone please? How can we determine whether we need to configure "replication_dsync_parameters = -d -N -l 30 -U" as indicated on the wiki2 (or some variation thereof) or not? It does appear to be completely undocumented, I tried looking in the source code but just ended up going in circles (i'm not familiar with it at all). "doveadm sync" has no documentation that I can find at all. I would happily write it if I could find the options in the code lol /A
Re: [Dovecot] xz compression
Hello Timo, Why send a mail to the mailing list if you are addressing a single person?
Re: [Dovecot] dsync replication questions
On 31/3/2014 12:03 μμ, Simon Fraser wrote: On Fri, 2014-03-28 at 11:58 +0200, Nikolaos Milas wrote: >Question 2a: What do options "-d -N -l 30 -U" signify in >"replication_dsync_parameters = -d -N -l 30 -U"? I'd also be interested to know the answer to this part. I found mention of the '-f' option, and adding '-f' to that list appears to have fixed a replication race condition I was having, but I can't find out a note of what it does. There is no one who knows that? Or no documentation whatsoever? Anyone please? How can we determine whether we need to configure "replication_dsync_parameters = -d -N -l 30 -U" as indicated on the wiki2 (or some variation thereof) or not? Thanks, Nick
Re: [Dovecot] mdbox with mail_attachment_dir per user in 2.2.12
Le 3 avr. 2014 à 15:12, Pavel Stano a écrit : > Hello, > > we have 2 netapp arrays with 2 volumes and we need to store our mail > data in one or other volume for every user. > We want keep data for one user in one volume only. > > So we would like to have 2 separate mail_attachment_dir, one on every > volume. > But in latest version 2.2.12 it look like it is only possible to set > one global mail_attachment_dir. > > I have an idea with 2 separate dovecot instances per machine with > different mail_attachment_dir. Or it is possible to somehow specify it > per user ? Hello Pavel, I don't know whether that setting may be customized or if must have a single constant value. Anyway, have you tried to make use of variables for setting its value? Or, if more relevant in your case, by overriding it from your user database (see section "Overriding settings" at http://wiki2.dovecot.org/UserDatabase/ExtraFields). Axel
Re: [Dovecot] Crash in pop3 with version 2.2.12
Le 4 avr. 2014 à 10:37, Teemu Huovila a écrit : > Hello > > On 04/04/2014 11:18 AM, Axel Luttgens wrote: >> I'm still wondering... under which circumstances could the crash occur? > This issue occurs whenever the function > src/pop3/pop3-commands.c:client_uidls_save() is called. > The function is called when: > > The pop3 internal structure client->message_uidls_save is 1. This in turn > happens when any of these is true: > 1. pop3 logoutformat has %u > 2. config setting pop3_uidl_duplicates is not the default "allow" > 3. config setting pop3_save_uidl=yes > > The problem manifests in two different ways. > 1) When the zlib plugin is active the executable crashed due to a > segmentation fault. > 2) If there is no zlib, the data returned by the UIDL command is "off-by-one" > and the last data item is null. > > Without zlib the error might look something like this: > C:uidl > S:+OK > S:1 0002533553b6 > S:2 0003533553b6 > S:3 0004533553b6 > S:4 0005533553b6 > S:5 0006533553b6 > S:6 (null) > S:. > >> Hence the question: to patch or not to patch? > Patch, if your setup will need to meet any of the three criteria triggering > the issue, before 2.2.13 is released. Hello Teemu, Thank you very much for your kind and very detailed explanation. None of 1. to 3. apply here, so I guess I've just been lucky. On the other hand, I didn't notice that the patch applies to a very precise context (the client_uidls_save function); it should thus be safe to apply it in all cases (even if un-needed with some *current* configuration). Sincerely, Axel
[Dovecot] imap / IPv6 problems?
Hi, I have this intermittant problem. When sending an email it *sometimes* takes ages before the process finishes. The process seems to hang in moving the message to the sent items" folder". When I disable the IPv6 stack in the network config (this is MS Windows 7), the hanging process immedialetely completes! This makens me think that is has to do with the IP stacks. Another observed effect is a long "rotating wheel" when just klicking on an imap folder before the listing in the right pane updates. Here the same trick solves the problem. I use Thunderbird on W7 as client and have my mail (3 accounts) on a remote mailserver. I have full control over that server which can become handy... Th emailserver is Ubuntu 12.04 LTS with postfix and Dovecot (2.0.19) from the standard repo's. My IPv6 connections is a native IPv6 from my ISP (xs4all.nl). I have no reason to think that the IPv 6 connecition itself is the problem. Any advise to investigate this problem is welcome. Egbert Jan, NL
Re: [Dovecot] Crash in pop3 with version 2.2.12
Hello On 04/04/2014 11:18 AM, Axel Luttgens wrote: > I'm still wondering... under which circumstances could the crash occur? This issue occurs whenever the function src/pop3/pop3-commands.c:client_uidls_save() is called. The function is called when: The pop3 internal structure client->message_uidls_save is 1. This in turn happens when any of these is true: 1. pop3 logoutformat has %u 2. config setting pop3_uidl_duplicates is not the default "allow" 3. config setting pop3_save_uidl=yes The problem manifests in two different ways. 1) When the zlib plugin is active the executable crashed due to a segmentation fault. 2) If there is no zlib, the data returned by the UIDL command is "off-by-one" and the last data item is null. Without zlib the error might look something like this: C:uidl S:+OK S:1 0002533553b6 S:2 0003533553b6 S:3 0004533553b6 S:4 0005533553b6 S:5 0006533553b6 S:6 (null) S:. > Hence the question: to patch or not to patch? Patch, if your setup will need to meet any of the three criteria triggering the issue, before 2.2.13 is released. br, Teemu Huovila
Re: [Dovecot] Crash in pop3 with version 2.2.12
On 4/4/2014 11:18 πμ, Axel Luttgens wrote: I'm still wondering... under which circumstances could the crash occur? I was wondering the same thing. We are now running 2.2.12 in production for two weeks (unpatched) and we have not seen such an error (despite extensive use of POP3). Regards, Nick
Re: [Dovecot] Crash in pop3 with version 2.2.12
Le 28 mars 2014 à 17:12, Urban Loesch a écrit : > Hi, > > thanks for your fast help. > Now pop3 works again without error. > > Thanks > Urban > > > Am 28.03.2014 15:03, schrieb Teemu Huovila: >> Thats my bad. This commit should fix it >> http://hg.dovecot.org/dovecot-2.2/rev/b0359910ec96. Thanks for reporting it. >> >> Teemu Huovila Hello, I'm still wondering... under which circumstances could the crash occur? Trying here to reproduce it with an unpatched 2.2.12, without "success": LIST and UIDL always return consistent results, without crashes, and behave that way on several mailboxes. I'm asking, because the problem could thus be tied to some configurations/settings only (as Urban wrote: "I saw some people on the list [...]"); but the correction brought by b0359910ec96 is an unconditional one. On the other hand, the problem might be raised because of some particular combination of circumstances, which I can't reproduce now, but which I could face one day or another... Hence the question: to patch or not to patch? Many thanks in advance, Axel
[Dovecot] dsync deleted my mailbox - what did I do wrong?
Hi. Mostly annoying: I migrated from one machine to another, made sure the target host worked as expected, updated mx records and - after a couple of days - signed it off as good. This is just my private machine, no big deal if something goes wrong.. Everything's fine? Good, let's migrate my inbox from the old machine. There's no direct connectivity between those servers, so what I did was: (old server) sudo -u vmail dsync -u d...@darklajid.de backup maildir:/tmp/mail_backup/ Works fine, got my maildir. Tar'd it up, moved it to the new server. Now how do I import those mails? Ah, let's use the same command, with -R? (new server) sudo -u vmail dsync -u d...@darklajid.de -R backup maildir:/tmp/mail_backup Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. Wait. What? Sure enough, the last couple of days are gone, the target mailbox is completely empty. I read the man page over and over again, but failed to see the problem. I even thought for a moment that _maybe_ dsync backup is one-way only (even if that failed as well) and tried the same command with mirror. Exactly the same output, same result, empty target mailbox. In the end I succeeded to import the mails with doveadm import, completely lost a number of days of mails. My fault, sloppy not to back the up again, but I still don't think that this should happen. Ever. My question now is: - where did I fail (ignoring the backups, please. That's .. something I know) - Can I use dsync ... for backups? I don't think that this is a good idea after yesterday night? - Should dsync EVER try to delete mailboxes? Even 'special' mailboxes? Should it warn about that, asking for a --force switch or something? Any insights would be appreciated. At this point the damage is done, but I'd like to learn how to do better. Ben
