On 2021-02-07 7:32 pm, John Fawcett wrote:
> On 07/02/2021 20:15, @lbutlr wrote:
> On 07 Feb 2021, at 02:07, @lbutlr wrote: On 06 Feb 2021,
> at 11:06, John Fawcett wrote: 19.08.20 Is that a
> malformed ISO date 2019-08-20 or a truncated europeans style 19-08-2020?
Either way, I cannot fi
On 2021-02-08 1:29 pm, John Fawcett wrote:
> On 08/02/2021 18:40, deano-dove...@areyes.com wrote:
>
> On 2021-02-07 7:32 pm, John Fawcett wrote:
>
> On 07/02/2021 20:15, @lbutlr wrote:
> On 07 Feb 2021, at 02:07, @lbutlr wrote: On 06 Feb 2021,
> at 11:06, John Fawcett wrote: 19.08.20 Is
On 2021-02-07 7:32 pm, John Fawcett wrote:
> On 07/02/2021 20:15, @lbutlr wrote:
> On 07 Feb 2021, at 02:07, @lbutlr wrote: On 06 Feb 2021,
> at 11:06, John Fawcett wrote: 19.08.20 Is that a
> malformed ISO date 2019-08-20 or a truncated europeans style 19-08-2020?
Either way, I cannot fi
Some questions about mail_crypt setups
I have global mail enecryption working nicely, and replication works
nicely between two systems. The main problem is that the private and
public keys are *right there* on the server in /etc/dovecot/private ...
Fine for a completely controlled system, but
My own personal setup is a 3-node system using three cheap VPS'. I also
helped to set the same thing up for a previous company using proper
systems, this was handling customer email.
Everything possible is kept in mariadb with galera for master-master
replication. Two main mail nodes with
d
On 2020-01-22 8:42 am, Domenico Pastore wrote:
Hello,
I have Dovecot configured with Solr for the indexes.
I have need your support for upgrade solr 7.7.2 to 8.4.1.
Solr 7.7.2 has a security issue CVE-2019-12409.
It's possible upgrade of Solr?
Dovecot work correctly with Solr 8.x?
The Solr doc
I run a pair of dovecot servers for personal small domains with several
layers of backup in place ...
- The two dovecot servers replicate to each via a Tinc vpn mesh. That
gives email resiliency.
- All mail is replicated via offlineimap to a 3rd server over that Tinc
vpn. It's on the mesh, it
Shawn -
You had mentioned in another email (somewhere) that were hopefully going
to do a write-up of setting up Solr 9.x with Dovecot. Any chance you've
had time for that ?
Thanks -
On 2022-09-30 1:52 pm, Shawn Heisey wrote:
> On 9/27/22 19:32, Nathanael Anderson wrote:
>
>> I was tryin
On 2023-07-19 4:08 pm, Gerald Galster wrote:
> A 50-100 mailbox user server will run Dovecot CE just fine. Pro would be
> overkill. What is overkill? I always thought it had a bit more features and
> support.
For Pro 2.3, you need (at minimum) 7 Dovecot nodes + HA authentication
+ HA storag
Johannes -
I'm running 2.2.9 under Ubuntu 14.04. I gave up on using the pipe
backend, just could not get the damn thing to work. I would up using
spool2dir and incron, which works perfectly. The issue was that
sa-learn would cause a pthread_cancel error with libgcc_s.so.1
Below is an exce
Is it possible to get replication working in a virtual user setup
that uses a static userdb ? My environment is fairly simple and typical
- there's a single system user (vmail) that owns all the home dirs
(/var/mail/domain.com/user). The virtual users
(use...@domain.com:secretpassword) are kept
How does this affect the other packages and the dependencies ? For
example, my test system is an Ubuntu 14.04/trusty box ...
$ dpkg -l
dove* | fgrep ii
ii dovecot-antispam 2.0+20130822-2build1 Dovecot
plugins for training spam filters
ii dovecot-core 1:2.2.9-1ubuntu2.1
secure POP3/IMAP server
Ugh, stuff got mangled in formatting below. Anyway, I've had no luck
with
various permutations, so it's looking like a virtual-user setup can't
make
use of replication ?
I guess what I want is for it to activate replication upon ANY
notification
of updated emails.
On 2014-06-03 11:54, deano-
way, I've had no luck with
> various permutations, so it's
looking like a virtual-user setup can't make
> use of replication ?
>
>
I guess what I want is for it to activate replication upon ANY
notification
> of updated emails.
>
> On 2014-06-03 11:54,
deano-doveco
I'm trying to avoid switching the userdb from a nice simple static
setup to something else to enable replication. Is there anyone using
replication with a virtual user configuration ? How did you do it ?
Actually, anyone doing replication at all - what does your config look
like ?
Thanks -
D
For those of you using virtual users, and SQL, how are you managing
your users and their home dirs ? That is, what process do you use for
adding/deleting users, creating their home dirs etc ? I suppose it's
easy enough to do manually, inserting rows in the database, creating
dirs, chown/chmod ya
Just a quick update on the below ... The 3-node setup is working
cleanly now. One master/backup DB node, two dovecot nodes, using Percona
Xtradb Cluster 5.5. All replication (percona and dovecot dsync) is via
ipsec tunnels.
Adding a user or new domain is a matter of creating a
/var/mail/newuse
My current production system is running dovecot 2.1.7-7ubuntu1 on
Ubuntu 13.04, and I'm building a new setup based on Ubuntu 14.04 with
dovecot 2.2.9-1ubuntu2.1 - current standard in the repos. I'd like to
use replication to get the mailstore from the old system to the new. Are
there any caveats
I've done this a couple of times, and there are a couple of things you
can do to help make it go smoothly. I did it not too long ago to move
to a new single server, and am getting ready to do it again to a fully
redundant setup (3 nodes for percona clustering, 2 of the nodes as
dovecot with sy
On 2014-10-13 08:30, Jens Dueholm Christensen wrote:
Apart from the need to register an account in order to "purchase" an
-ee license, are there any cavats by switching to the -ee version
compared to compiling and running the regular releases?
I've got no problems with downloading, building and
On 2014-10-23 12:19, Alejandro Exojo wrote:
That most of my mail comes from 100% assured not spam sources: mailing
lists
that are already filtered or rss2email (the second probably can be
skipped
easily because it comes locally). I only have a small VPS, so I'm
trying to
save some resources if
21 matches
Mail list logo
