> On 29. May 2020, at 23.43, Joseph Tam wrote:
>
> On Fri, 29 May 2020, Sami Ketola wrote:
>
>>> # echo plaintextpass | doveadm pw -s BLF-CRYPT
>>> doveadm(user): Fatal: Error reading configuration:
>>> stat(/etc/dovecot/dovecot.conf) failed: No such file or directory
>>>
>>> Is the
Am 29.05.2020 um 17:37 schrieb Francis Augusto Medeiros-Logeay:
Hi,
I want to do a simple backup of my maildir. I read here that
maildirlock is not to count on in the future and the recommended
option was to use doveadm backup. However, it seems that this requires
to setup another dovecot ser
Hello,
Thanks, the directory structure and files will all be the same so i'll
just rsync.
Thanks.
Dave.
On 5/29/20, Francis Augusto Medeiros-Logeay wrote:
> I did what Aki said. Actually I moved it all to a new server and to docker
> containers. From Dovecot 2.2 to 2.3. And it worked fine. Of
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
On Fri, 29 May 2020, Sami Ketola wrote:
# echo plaintextpass | doveadm pw -s BLF-CRYPT
doveadm(user): Fatal: Error reading configuration:
stat(/etc/dovecot/dovecot.conf) failed: No such file or directory
Is there a way to circumvent the need for a configuration file?
I don't
> On 29. May 2020, at 23.09, Joseph Tam wrote:
>
>
> It would be useful to run the "doveadm" utility on a non-dovecot server e.g.
> generating password hashes:
>
> # echo plaintextpass | doveadm pw -s BLF-CRYPT
> doveadm(user): Fatal: Error reading configuration:
> stat(/etc/dov
It would be useful to run the "doveadm" utility on a non-dovecot server e.g.
generating password hashes:
# echo plaintextpass | doveadm pw -s BLF-CRYPT
doveadm(user): Fatal: Error reading configuration:
stat(/etc/dovecot/dovecot.conf) failed: No such file or directory
Is there
# dovecot --version
2.3.10.1 (a3d0e1171)
Dovecot is unable to start, I see error " Fatal: fchown() failed for
/run/dovecot/login: Operation not permitted"
what could be the problem?
any help please
$ls -la /var/mail/
drwxr-xr-x1 root root 4096 May 29 17:32 .
drwxr-xr-x1 ro
I did what Aki said. Actually I moved it all to a new server and to docker
containers. From Dovecot 2.2 to 2.3. And it worked fine. Of course one always
forget something - the path for the certificates, the different directory for
mounting storage, etc.
But am surprise and happy that it worked
> On 29/05/2020 20:12 Ralph Seichter wrote:
>
>
> * David Mehler:
>
> > I'd ideally like to back up all the mails in the maildir location,
> > copy that over, load in my configuration files, and bring the system
> > back up.
>
> I don't think this qualifies as "ideal" for migration. My reco
* David Mehler:
> I'd ideally like to back up all the mails in the maildir location,
> copy that over, load in my configuration files, and bring the system
> back up.
I don't think this qualifies as "ideal" for migration. My recommendation
is to set up the new server and configure Dovecot replica
Hello,
I'm needing to migrate my dovecot installation it's 2.3 on FreeBSD
12.1 to a new server. I'd ideally like to back up all the mails in the
maildir location, copy that over, load in my configuration files, and
bring the system back up. I doubt it's that easy, any pitfalls I
should watch out f
On 25 May 2020, at 12:48, mj wrote:
> I would then ask them to move over to 993, and finally disable port 143
> altogether.
From personal experience the only way to do this is to stop listening to port
143. I dropped support for non-encrypted mail ports ages ago, and I didn't get
a single user
Hi,
I want to do a simple backup of my maildir. I read here that maildirlock
is not to count on in the future and the recommended option was to use
doveadm backup. However, it seems that this requires to setup another
dovecot server.
My questions are:
- How much to I need to configure this
Thanks to all who participated in the interesting discussion.
It seems my initial thought might have been best after all, and
discontinuing port 143 might be the safest way proceed.
Thanks again, valuable insights!
MJ
On 5/29/20 11:48 AM, Jean-Daniel wrote:
Le 29 mai 2020 à 11:17, Stuart
> Le 29 mai 2020 à 11:17, Stuart Henderson a écrit :
>
> On 2020-05-26, mj wrote:
>> Hi,
>>
>> On 25/05/2020 23:04, Voytek wrote:
>>> jumping here with a question, if I use 143 with STARTTLS, and, force
>>> TLS/SSL in configuration, that's equivalent from security POV, isn't
>>> it? and, same
On 2020-05-26, mj wrote:
> Hi,
>
> On 25/05/2020 23:04, Voytek wrote:
>> jumping here with a question, if I use 143 with STARTTLS, and, force
>> TLS/SSL in configuration, that's equivalent from security POV, isn't
>> it? and, same for 110 STARTTLS? Or am I missing something?
> Interesting point, a
17 matches
Mail list logo