Dear Steffen,
Finally managed to test your suggestions ...
Am 2014-07-31 09:11, schrieb Steffen Kaiser:
On Thu, 31 Jul 2014, Steffen Kaiser wrote:
How about adding another userdb { driver = passwd-file args =
/.../%s/file
} as the first one, which disables the access to the one user's mail
Hi,
Sorry for warming up this thread, but
Am 2014-07-31 13:34, schrieb Michael Grimm:
In the meantime I use something like to block users during maintainance:
# temporary blocks
passdb {
driver = passwd-file
deny = yes
args = /path/to/deny-users
}
# regular
passwd {
driver
On 29 Jul 2014, at 16:48, Jogi Hofmüller j...@mur.at wrote:
Another question regarding migration. While migrating a mailbox with
dsync is it safe to deliver mail via LMTP to the new (target) mailbox or
is it wiser to deactivate LMTP delivery to this mailbox until it's fully
migrated?
And
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 30 Jul 2014, Jogi Hofmüller wrote:
Or better - disable LMTP service in Dovecot. Incoming mail will stay on
your MTA and when you're done, you just tell it to deliver everything
that piled up in the queue in the meantime
Better but still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 31 Jul 2014, Steffen Kaiser wrote:
On Wed, 30 Jul 2014, Jogi Hofmüller wrote:
Or better - disable LMTP service in Dovecot. Incoming mail will stay on
your MTA and when you're done, you just tell it to deliver everything
that piled up in
Hi Harald, all,
Am 2014-07-30 17:36, schrieb Reindl Harald:
normally you announce a mainantaince window for such migrations
That's what we do.
why do you need dsync at all for such a migration?
Migrating from cyrus to dovecot in a transparent manner.
Cheers,
--
j.hofmüller
On 31.7.2014 12:05, Jogi Hofmüller wrote:
Hi Harald, all,
Am 2014-07-30 17:36, schrieb Reindl Harald:
normally you announce a mainantaince window for such migrations
That's what we do.
why do you need dsync at all for such a migration?
Migrating from cyrus to dovecot in a transparent
Hi --
On 2014-07-31 12:05, Jogi Hofmüller wrote:
Am 2014-07-30 17:36, schrieb Reindl Harald:
why do you need dsync at all for such a migration?
Migrating from cyrus to dovecot in a transparent manner.
And additionaly, if one wants to switch mailbox formats whilst
migration. Dsync is
Hi Jiri, all,
Am 2014-07-31 12:33, schrieb Jiri Bourek:
As far as I know you can do the warm - cold with dsync too. First you do
backup on live (i.e. accessible for both imap and delivery) mailbox.
This takes a long time on big mailbox, but that should not be an issue
since the mailbox can
[sent to early, sorry]
On 2014-07-31 12:05, Jogi Hofmüller wrote:
Am 2014-07-30 17:36, schrieb Reindl Harald:
why do you need dsync at all for such a migration?
Migrating from cyrus to dovecot in a transparent manner.
And additionaly, if one wants to switch mailbox formats whilst
Jogi Hofmüller wrote:
We are not planning on multiple runs of doveadm backup. The question is
what to do with LMTP _while_ the doveadm backup migration is happening?
At the time when mailbox X get's migrated, the settings used for the
proxy will be removed, so user X cannot access the
Hi Jiri, all,
Thanks for your reply.
Am 2014-07-29 16:13, schrieb Jiri Bourek:
Considering you're planning to use doveadm backup, you can't deliver
into the new mailbox. From dsync man page:
Yes, this is the way we plan to migrate the mailboxes.
backup - Backup mails from default mail
Am 30.07.2014 11:10, schrieb Jogi Hofmüller:
We are not planning on multiple runs of doveadm backup. The question is
what to do with LMTP _while_ the doveadm backup migration is happening?
just shutdown the MTA so you don't receive new mail
senders will defer and deliver later
On 30.7.2014 11:27, Reindl Harald wrote:
Am 30.07.2014 11:10, schrieb Jogi Hofmüller:
We are not planning on multiple runs of doveadm backup. The question is
what to do with LMTP _while_ the doveadm backup migration is happening?
just shutdown the MTA so you don't receive new mail
senders
Hi all,
Thanks for your replies.
Am 2014-07-30 12:02, schrieb Jiri Bourek:
On 30.7.2014 11:27, Reindl Harald wrote:
just shutdown the MTA so you don't receive new mail
senders will defer and deliver later
I would like to stay away from this option since we plan on doing a
transparent
Am 30.07.2014 16:39, schrieb Jogi Hofmüller:
Am 2014-07-30 12:02, schrieb Jiri Bourek:
Or better - disable LMTP service in Dovecot. Incoming mail will stay on
your MTA and when you're done, you just tell it to deliver everything
that piled up in the queue in the meantime
Better but still
On 07/30/2014 10:39 AM, Jogi Hofmüller wrote:
I would like to stay away from this option since we plan on doing a
transparent migration that will take a few nights. Turning MTA off
every night seems a bit drastic.
What I do is I implement a delivery lock in the database. I like to use
exim +
Hi all,
Another question regarding migration. While migrating a mailbox with
dsync is it safe to deliver mail via LMTP to the new (target) mailbox or
is it wiser to deactivate LMTP delivery to this mailbox until it's fully
migrated?
And what methods could I use to stop delivery to a mailbox
On 29.7.2014 15:48, Jogi Hofmüller wrote:
Hi all,
Another question regarding migration. While migrating a mailbox with
dsync is it safe to deliver mail via LMTP to the new (target) mailbox or
is it wiser to deactivate LMTP delivery to this mailbox until it's fully
migrated?
And what methods
19 matches
Mail list logo
