}
}
~ # ls -la /var/run/dovecot/stats-writer
srw-rw 1 dovecot mail 0 Nov 21 17:00 /var/run/dovecot/stats-writer
Could anyone please shed an idea or tip of where more too can I look.
Many thanks
Regards
Brent Clark
...
Aki
Hi Aki
Your timing is perfect. Many thanks.
As a process of elimination. I *just* set the following.
stats_writer_socket_path=""
Ill look at your suggestion.
Many thanks again
Regards
Brent Clark
ook it would be appreciated. This one has my team and I stumped.
Kind regards
Brent Clark
NOT the best solution.
My question is, how do some of the fellow dovecot users,or other
companys, e.g. google etc, pull this off.
If you can assist in helping me fine a solution and too help me
understand, I would greatfully appreciate it.
Kind Regards
Brent Clark
password
and update the DB, then the mail client authenticates perfectly.
If anyone can help, it would be most appreciated.
Kind Regards
Brent Clark
Thanks Timo
Ill try again.
Regards
Brent Clark
On Sat, Mar 8, 2008 at 11:52 AM, Timo Sirainen <[EMAIL PROTECTED]> wrote:
> On Sat, 2008-03-08 at 11:27 +0200, Brent Clark wrote:
>
> > use Digest::SHA1;
> > use MIME::Base64;
> > $ctx = Digest::SHA1->new;
> &
Thanks again Timo.
Does work.
Typo my side.
Regards
Brent
On Sat, Mar 8, 2008 at 12:07 PM, Brent Clark <[EMAIL PROTECTED]>
wrote:
> Thanks Timo
>
> Ill try again.
>
> Regards
> Brent Clark
>
>
> On Sat, Mar 8, 2008 at 11:52 AM, Timo Sirainen <[EMAIL PROTECT
Hi
Im trying something new with my test dovecot.
I set my mail_location to to a new location
mail_location = maildir:/var/maildir/%u/Maildir
But with this new setup i too am authenticating against Mysql. This worked
fine till i decided to move the mail.
So now i have moved the mail, deleted th
Good day Guys
I have a user story have an imap reverse / proxy in front of our clients
servers.
Im currently using the following sources for information.
https://wiki.failover.de/Email/Dovecot/IMAP/Proxy/
https://gist.github.com/rplessl/dd56d05c84f988706418
https://wiki2.dovecot.org/PasswordDatab
happens, but more
importantly how to recover from this.
doveadm index -u INBOX do the trick?
I also would like to ask the community, is there any tips or tricks any
of you guys do to mitigate index / cache corruptions.
Many thanks
Regards
Brent Clark
Good day Guys
Just an update, my colleague and I came across this script.
https://www.dovecot.org/tools/maildir-size-fix.pl
We made a backup, ran it, but unfortunately the problem still persists.
Regards
Brent
On 2019/11/11 11:42, Brent Clark wrote:
Good day Guys
I have been met with a
11.11.2019 12.26, Brent Clark via dovecot wrote:
Good day Guys
Just an update, my colleague and I came across this script.
https://www.dovecot.org/tools/maildir-size-fix.pl
We made a backup, ran it, but unfortunately the problem still persists.
Regards
Brent
On 2019/11/11 11:42, Brent Clark wrote
Good day Guys
I forgot to add and mention a very important piece of the puzzle.
We are making use of dovecots compression plugin.
I.e. https://doc.dovecot.org/configuration_manual/zlib_plugin/#compression
Regards
Brent Clark
On 2019/11/11 14:49, Brent Clark wrote:
Good day Aki
Thanks ever
Good day Guys
We came across https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661008
maildir_broken_filename_sizes = yes
We tried and all worked.
A question, is this a setting that one would enable in a production
environment?
Regards
Brent
On 2019/11/11 16:17, Brent Clark wrote:
Good
, is anyone else using Dovecot Replication in a
medium to large enterprise?
Can you please share your experiences, pitfalls and if you have any tips
managing mail replication.
Kindest regards and thanks in advance.
Brent Clark
the proxy: URI in 2.4?
Are password_key and user_key still supported, or should I be using a
different mechanism?
Is iterate_disable = yes still relevant or required in this context?
Any guidance, examples, or pointers to migration resources would be very
helpful.
Thanks in advance,
B
what I have
passdb sql {
query = SELECT name AS username, password FROM mailboxes WHERE name =
'%{user | username}'
sqlite_path = /usr/home/.mail/%{domain}/mailconf.sq3
}
If I hard code the path, then the error message goes away
Regards
B
On 2025/06/04 14:53, Aki Tuomi wrote:
The correct syntax is %{user|domain}.
Aki
Good day Aki
Thank you, for taking the time to reply.
The reason, why it was %{domain}, for if I did what you proposing, I get
Failed to parse configuration: Failed to expand sqlite_path setting variables:
Unk
ters (or a minimal working example) would be greatly appreciated.
Kind Regards
Brent Clark
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
19 matches
Mail list logo