Ellie,
Thanks for checking. My doubt came from another documentation
(https://www.cyrusimap.org/docs/cyrus-imapd/2.5.9/faq.php):
plus addressing - Plus addressing allows direct delivery to a
particular mailbox (other than an INBOX). This is done in two ways.
The first way allows deli
Andrew,
> For a small system with a few hundred mailboxes, a simple unix
filesystem backup is sufficient. You can dump the Cyrus mailboxes.db to
a flat file every hour with cron (keep a few days worth). Backup
everything with your regular backup system (tar, rsync, etc).
> If you suffer a co
Looks like "postman" from a skim of the source, and I believe this is
the same user as when connecting via a UNIX socket:
https://github.com/cyrusimap/cyrus-imapd/blob/15c812df6a020414a2e8863fe1afdfa3273a7bad/imap/lmtpengine.c#L993-L1005
But I would welcome correction from someone who knows, I'm ju
Hi Ellie,
Chen's question made me recheck the docs and now I have a doubt. Could
you please clarify under what user the LMTP-delivered mails enters Cyrus
when "-a" option is used over TCP with lmtpd (i.e. lmtp cmd="lmtpd -a"
listen="127.0.0.1:2004")?
The documentation
(https://cyrusimap.org
On Fri, 11 May 2018, Anatoli wrote:
There may be an argument that could be made for 2 backup stratagies
That's the point. In the context of SME environments (Small and Medium-sized
Enterprises, i.e. from 5 to 50 employees normally, up to 250 in some
countries) that we were talking about, a r
> There may be an argument that could be made for 2 backup stratagies
That's the point. In the context of SME environments (Small and
Medium-sized Enterprises, i.e. from 5 to 50 employees normally, up to
250 in some countries) that we were talking about, a replication is an
overkill, IMO. But
Hi Chen,
> So, the question : is it possible to set specific ACLs on autocreated
> folders ? (i.e., ACLs, different from those defined by defaultacl in
> imapd.conf).
I believe the autocreate mechanism has no particular knowledge of ACLs all all.
It just uses the standard Cyrus policy for assi
On 05/10/2018 06:29 PM, Anatoli wrote:
Actually, mysqldump performs a lock on the records it's dumping. If
its for a MyISAM db, the entire table is locked. If it's for InnoDB
and similar, an internal snapshot is created and only the records the
dump is reading are unavailable for writing.
Mysql
All,
I have built a eighth (and hopefully last) release candidate of SASL
2.1.27 which can be downloaded from here:
* HTTP:
https://www.cyrusimap.org/releases/cyrus-sasl-2.1.27-rc8.tar.gz
https://www.cyrusimap.org/releases/cyrus-sasl-2.1.27-rc8.tar.gz.sig
* FTP:
ftp://ftp.cyrusi
Actually, mysqldump performs a lock on the records it's dumping. If its
for a MyISAM db, the entire table is locked. If it's for InnoDB and
similar, an internal snapshot is created and only the records the dump
is reading are unavailable for writing.
Cyrus could also implement a per-user lock,
> "A" == Anatoli writes:
A> What about mysqldump > dump.sql, then mysql < dump.sql? Also a wrong
A> way and didn't have to be implemented?
No, that's exactly my point. Thanks for making it for me! The analog
to the way you indicated that you would like it to work would be having
the mysql
> Well, sort of. It is a method that is actually focused around doing
backups. It happens to make use of the replication protocol because
that is actually the smart way to do it. I did detail the differences
in my message.
I suggest you try to use it in your deployments and then share with
> For me, if I put a replica in place it's get the role of backup.
Meanning I will put two replica and do not make another backup.
A replica is not a replacement for a backup. You may have your specific
needs, but replica per-se mostly serves to cover for master's hardware
failures. You are no
Le 10/05/2018 à 16:08:32-0300, Anatoli a écrit
Hi.
> In both cases, a copy of the master data is made, which requires twice the
> space of real usage (Cyrus Backups tries to apply compression on stored data,
> not sure how well it works).
In ZFS with lz4 (standard compression on ZFS) you got 1.1
Le 10/05/2018 à 10:38:28-0300, Anatoli a écrit
> > Not very sure to understand that. It's always true isn't ? If you have XTo
> > of
> data and you want n backups you will need X*(n+1) To ?
>
> The replication as it is designed means that you create an additional
> (replica)
> instance of Cyrus t
> "A" == Anatoli writes:
A> What you mention is highly related to the replication backup
A> we were talking about in the previous mails.
Well, sort of. It is a method that is actually focused around doing
backups. It happens to make use of the replication protocol because
that is actually
Jason,
What you mention is highly related to the replication backup we were
talking about in the previous mails. The idea is the same, they
replicate from master. Then, in a pure replica solution, the replica is
stopped, a copy of its files (in the native format) is made and it's
started agai
Cyrus does have an integrated backup system (see
https://cyrusimap.org/imap/reference/admin/backups.html) which I'm not
sure has been mentioned in this thread. But you still have to have
enough space to keep the compressed backups on disk in order to move
them to tape or whatever archival storage
One alternative, if you are running VMs (such as VMWare or Hyper-V) is resort
to a VM backup program that will uses native change tracking (VMWare CBT and
Hyper-V RCT). This allows for a consistent and incremental backup of the VM’s.
It’s quite fast and saves lots of space. The backup is increm
> Not very sure to understand that. It's always true isn't ? If you
have XTo of data and you want n backups you will need X*(n+1) To ?
The replication as it is designed means that you create an additional
(replica) instance of Cyrus that will be in sync with the master
instance, so when you ne
Le 10/05/2018 à 02:44:18-0300, Anatoli a écrit
Hi,
>
> The replication is reasonable only if you have more than one server in your
> deployment (and both servers with the same level of security, if not you risk
> to compromise the user data) or "spool size/available disk space" is low,
> otherwis
21 matches
Mail list logo
