Hello,
I'm in the process of moving users from an old dovecot setup with system
users to a modern virtual user setup.
I can't find good documentation on domain quota.
It is mentioned in the docs as
quota2 = dict:domain:%d:proxy::quota_domain
but not much more.
Searching the mailing list or Googl
Aki Tuomi wrote on Thu, 16 Aug 2018 21:03:44 +0300 (EEST):
> Can you provide doveconf -n please?
Thanks for the quick reply. I think I already provided the most relevant
portions of config. I ran a doveconf -n and it doesn't reveal important
information like sql setup. I'll do my best to sum up
Christy S wrote on Fri, 17 Aug 2018 18:05:47 -0500:
> I see the
> connection in the log, but no errors.
what do you see?
And, also, what exactly do you want to do? (e.g. with what do you send
which email from->to via what, how should this affect your server and what
do you check on your serve
I did that the last time one year ago, now on another machine with the
same software (Ubuntu 16.04) it fails.
openssl dhparam 4096 > /var/lib/dovecot/ssl-parameters.dat
dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam
-inform der > /etc/dovecot/dh.pem
last command fails w
Aki Tuomi wrote on Sun, 19 Aug 2018 18:21:31 +0300:
> Just generate new parameters on some machine with good entropy source.
So, if it fails to transform (although bigger) the machine hasn't enough
entropy (because it's quite new?)? I'm generating now on the original
machine from last year whic
Well, on that machine it took now more than an hour. But it created the
same 769 bytes file as on the other machines. And, foreseeable, that one
fails to transform as well.
-rw-r--r-- 1 root root 360 Aug 7 2017 ssl-parameters.dat
-rw-r--r-- 1 root root 769 Aug 19 19:25 ssl-parameters.new.d
Aki Tuomi wrote on Sun, 19 Aug 2018 20:56:28 +0300 (EEST):
> openssl gendh 4096 > params.pem
Ok. I then misunderstood what's written at
https://wiki.dovecot.org/SSL/DovecotConfiguration
I thought I need to create dh.pem in two steps:
1. openssl dhparam 4096 > /var/lib/dovecot/ssl-parameters.dat
I noticed that most of the time with dovecot 2.3 I get this output,
showing systemd listening on the port as well:
lsof -i TCP:993
systemd 1 root 38u IPv4 3388360574 0t0 TCP *:imaps (LISTEN)
systemd 1 root 41u IPv6 3388360575 0t0 TCP *:imaps (LISTEN)
dovecot 11607 root
So, is this config correct for domain quota dictionary-based and how
should it work?
Kai
Ok, thanks!
Kai
Kai Schaetzl wrote on Mon, 20 Aug 2018 13:32:59 +0200:
> So, is this config correct for domain quota dictionary-based and how
> should it work?
Hello,
resolving a problem and knowing that there is a problem are two different
things. I would still like to know if this config is correct a
I would like to transfer mail for some users from an old dovecot (with no
doveadm) to a modern dovecot (2.3.2). I've read up on
https://wiki2.dovecot.org/Tools/Doveadm/Sync
https://wiki2.dovecot.org/Migration/Dsync
and I'm not sure if I can use doveadm for this purpose.
I need doveadm to login t
Given the following:
mailboxes:
us...@example1.com
us...@example1.com
us...@example1.com
etc.
aliases:
whate...@example1.com -> us...@example1.com
whate...@example2.com -> us...@example1.com
whate...@example3.com -> us...@example1.com
Now the problem:
example1.com MX goes elsewhere (doesn't poin
Gerald Galster wrote on Tue, 11 Sep 2018 20:49:17 +0200:
> Is this a dovecot problem on your side? dovecot usually accepts mail
> from MTA like postfix, so it would be better to remove example1.com from
> postfix relaydomains (mailbox domains, alias domains, ...). Then there
> is no delivery to do
Thanks for all the replies. I didn't have time to reply earlier.
I went with my first proposed solution. Everything else is simply too much
hazzle. You would have to set this for every single exception/address/user
and so on and you cannot be sure that it doesn't bite you some time later
with a
Is there a way to split the auth logging (logins and failed logins) from
the other logging that goes to
info_log_path = /var/log/dovecot/dovecot.log
?
This log gets a lot of other info as well, most notably the lmtp
notifications about every filed mail (with no level stamping, btw).
This makes i
I hoped I don't have to switch to syslog logging. Well, anyway.
I changed
10-logging.conf:
syslog_facility = uucp
and commented out the other log lines.
rsyslog.d/50-default.conf:
uucp.debug -/var/log/dovecot/debug.log
uucp.info -/var/log/dovecot/doveco
Kai Schaetzl wrote on Wed, 26 Sep 2018 12:43:28 +0200:
> But it logs only to /var/log/syslog
It seems that "service rsyslog restart" doesn't correctly restart
rsyslogd. You have to stop and start it. Then it picks up the changed
config.
Kai
--
Get your web at Conactive
I'm not going to log dovecot to mail, that creates only the same mixup as
before, even worse, now postfix and dovecot mixed. I had to stop/start
(force-reload would also work) rsyslogd to pick up the changed config. A
restart doesn't change the config as with other daemons. Now I can filter
lmt
This works for splitting off lmtp traffic, for instance.
syslog_facility = uucp
rsyslog:
:msg, contains, "lmtp(" -/var/log/dovecot/lmtp.log
& stop
uucp.=debug -/var/log/dovecot/debug.log
uucp.=info -/var/log/dovecot/dovecot.log
uucp.=warn
I forgot to mention that you have to change owner for the /var/log/dovecot
directory before rsyslog can log.
Kai
I am testing a special setup on one machine where I want to put some local
users that get mail locally to /home user directories via postfix
transport map local: for historical and practical reasons. Other users are
setup as virtual users.
The local users are *also* setup as virtual users for do
I changed this now to a more standard setup using a mysql passdb/userdb
for virtual users and a passwordfile auth (auth-passwordfile.ext) as
described in doc/wiki/AuthDatabase.PasswdFile.txt for a few other users.
I'm still getting the same errors concerning dict access when running
doveadmin q
Btw, what sizes are we talking about here? I assume it would be really
huuuge?
What's the max size of the .cache file and how many mails might create
this size?
Kai
I'm in the process of rolling out new setups with dovecot on CentOS 5.2
and I notice that dovecot doesn't handle the brute-force attacks too nice.
I reduced the limit a bit to some reasonable looking value:
login_max_processes_count = 32
to stop them earlier and the number of processes stops at th
Charles Marcus wrote on Wed, 23 Jul 2008 10:30:30 -0400:
> The best answer is to use a tool made for this kind of job, like fail2ban.
I found a few fail2ban definitions on the web, but all seem to be either
very outdated or plain wrong for RHEL/CentOS. I've come so far as to this
with the regex
Bill Landry wrote on Wed, 23 Jul 2008 13:18:44 -0700:
> Kai, you can test your regex using "fail2ban-regex".
Thanks for the answer. Yeah, I found that in the meantime. Great little
helper. For some reason I cannot get any rule that ends in $ to work, so
I've now come up with
failregex = dovec
Jack Stewart wrote on Wed, 23 Jul 2008 10:29:06 -0700:
> We you run 'netstat -tan' (or equivalent), what state are the packets
> in? If it is just a bunch of processes with no active connections then
> it should not be a big deal.
Well, the point is they should not have been there ;-) The proce
Arkadiusz Miskiewicz wrote on Fri, 25 Jul 2008 23:42:09 +0200:
> This may be a silly question but how to correctly stop dovecot and be sure
> that it's possible to start it again?
depends on your operating system. /etc/init.d/dovecot stop should work on
most Linuxes.
> I have imap-login proces
Timo Sirainen wrote on Sat, 26 Jul 2008 19:45:20 +0300:
> It does kill everything.
Not for me, not with the 1.07 I have in CentOS 5.2.
Look at the thread I started a few days ago with
<[EMAIL PROTECTED]>
When I ran "service dovecot restart" (or stop) in that situation it did
*not* kill all the
Maarten Bezemer wrote on Sun, 27 Jul 2008 11:43:06 +0200 (CEST):
> It is normal for some services to terminate te main process, but leave
> active children alive.
That may be so, but Timo claimed the opposite (as I read his response). I'm
merely pointing out that I cannot see the behavior that T
Timo Sirainen wrote on Sun, 27 Jul 2008 17:14:29 +0300:
> The behavior is controlled by shutdown_clients setting. I suppose you
> have it set to "no"?
It's set to how dovecot.conf came:
#shutdown_clients = yes
If that indicates the default it is enabled. But it didn't work.
The thread I started
Matthias Andree wrote on Wed, 30 Jul 2008 09:59:33 +0200:
> setting pop3_lock_session=yes works as expected (ca. 1.1.2 from hg):
but it seems to be off by default. From my dovecot.conf (1.07):
#pop3_lock_session = no
I think it should be on by default.
Kai
--
Kai Schätzl, Berlin, Germany
Get
33 matches
Mail list logo
