On 12.11.2019 9.49, Frank Elsner wrote:
> On Tue, 12 Nov 2019 09:22:56 +0200 Aki Tuomi via dovecot wrote:
>> Hi!
>>
>> Can you try follow this guide to get a core dump
>>
>> https://www.dovecot.org/bugreport-mail
>>
>> then provide
>>
>>
>> gdb /usr/lib/dovecot/auth /path/to/core
>>
>> bt full
>
On Tue, 12 Nov 2019 09:22:56 +0200 Aki Tuomi via dovecot wrote:
> Hi!
>
> Can you try follow this guide to get a core dump
>
> https://www.dovecot.org/bugreport-mail
>
> then provide
>
>
> gdb /usr/lib/dovecot/auth /path/to/core
>
> bt full
Sorry, I'm not familiar with gdb and can only provi
Hello,
I have FreeBSD 12 server with postfix + spamassassin. Old config work
fine.
-- old postfix master.cf
spamfilter unix - n n - - pipe
flags=R user=nobody argv=/usr/local/bin/spamc -e /usr/sbin/sendmail -oi
-f ${sender} ${recipient}
--
I try to add dovecot-lda (with sieve suppo
Hi!
Can you try follow this guide to get a core dump
https://www.dovecot.org/bugreport-mail
then provide
gdb /usr/lib/dovecot/auth /path/to/core
bt full
on it. Would help narrowing down that bug.
Also doveconf -n could be useful.
Aki
On 12.11.2019 9.19, Frank Elsner wrote:
> On Tue, 12
On Tue, 12 Nov 2019 00:17:28 +0100 Frank Elsner via dovecot wrote:
> On Mon, 11 Nov 2019 23:47:27 +0100 Frank Elsner via dovecot wrote:
[ ... ]
> I narrowed the probelem down to the warnings
>
> Warning: service auth { client_limit=128 } is lower than required under max.
> load (768)
> Warnin
On Mon, 11 Nov 2019 23:47:27 +0100 Frank Elsner via dovecot wrote:
[ ... ]
> I got dovecot-2.2.36.4 compiled but at start the log shows
>
> dovecot[342614]: master: Dovecot v2.2.36.4 (baf9232c1) starting up for imap
> dovecot[342617]: ssl-params: Generating SSL parameters
> dovecot[342614]: mas
On Mon, 11 Nov 2019 17:30:37 +0200 (EET) Aki Tuomi via dovecot wrote:
[ ... ]
> Is there some reason you want to use ancient dovecot? You should use 2.2.36
> at least.
I got dovecot-2.2.36.4 compiled but at start the log shows
dovecot[342614]: master: Dovecot v2.2.36.4 (baf9232c1) starting u
Hi Yarema, you are right, the mode setting enabled indeed the socket.
-Original Message-
Subject: Re: Login/director not created
I too assume this socket should be in the login dir.
I am suggesting that maybe the socket is not being created because of
permissions.
Therefore if
Good afternoon.
Shouldn't at least the wiki page be updated so that it avoids someone in
the future having to struggle like I did?
El 08/11/2019 a las 17:13, David Wells via dovecot escribió:
> Good afternoon.
>
>
> I'm configuring dovecot to authenticate users against a samba server
> running as
I too assume this socket should be in the login dir.
I am suggesting that maybe the socket is not being created because of
permissions.
Therefore if you explicitly set { group = dovenull } you may fix the
permissions issue.
I am not running director in my setup, just pointing out what jumped out
But if in the configuration of the director is stated login/director.
Than I assume this socket should be in the login dir not? You have also
the director activate with executable = imap-login director?
-Original Message-
Subject: Re: Login/director not created
On my install the lo
On my install the login/ dir is:
drwxr-x--- 2 root dovenull 8 Nov 10 18:14:00 login/
srw-rw-rw- 1 root dovenull 0 Nov 10 18:14:00 login/dns-client=
srw-rw-rw- 1 root dovenull 0 Nov 10 18:14:00 login/imap=
srw--- 1 dovenull dovenull 0 Nov 10 18:14:00 login/ipc-proxy=
srw
On Mon, 11 Nov 2019 17:30:37 +0200 (EET) Aki Tuomi via dovecot wrote:
[ ... ]
> Is there some reason you want to use ancient dovecot? You should use 2.2.36
> at least.
Migration from 32bit to 64bit. I want to avoid problems, so I used the version
I have
compiled and used on the 32bit system.
I have this[0] config, yet the /var/run/dovecot/login/director is not
created, what to check in the config?
dovecot: imap-login: Error: auth: connect(director) failed: No such file
or directory
[0]
service director {
unix_listener login/director {
#mode = 0666
}
fifo_listener login
> On 11/11/2019 17:22 Frank Elsner via dovecot wrote:
>
>
> Hi,
>
> I try to compile dovecot -2.2.24 on Fedora 31 and get the following error:
>
> iostream-openssl.c: In function ‘openssl_iostream_verify_client_cert’:
> iostream-openssl.c:118:37: error: dereferencing pointer to incomplete t
Hi,
I try to compile dovecot -2.2.24 on Fedora 31 and get the following error:
iostream-openssl.c: In function ‘openssl_iostream_verify_client_cert’:
iostream-openssl.c:118:37: error: dereferencing pointer to incomplete type
‘X509_STORE_CTX’ {aka ‘struct x509_store_ctx_st’}
118 | subject = X5
Am 11.09.19 um 22:09 schrieb Stephan Bosch via dovecot:
On 02/09/2019 15:05, Philipp Faeustlin via dovecot wrote:
The recipients in the vacation :addresses String list are matched
case-sensitive.
If the recipient gets a mail with wrong case, the message is discarded
with:
"discarding vacati
I managed to work around this by putting these in the Dockerfile
(umask 027 ; mkdir /var/dovecot/login) && chown $DOVECOT_USER.dovenull
/var/dovecot/login
(umask 027 ; mkdir /var/dovecot/token-login) && chown
$DOVECOT_USER.dovenull /var/dovecot/token-login
But now I am stuck with this socke
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 da
Set up fts_xapian over the weekend and re-indexed.
https://github.com/grosjo/fts-xapian
Tried to search my INBOX and got:
> dovecot: indexer-worker: Panic: file charset-iconv.c: line 83
(charset_to_utf8_try): assertion failed: (srcleft <=
CHARSET_MAX_PENDING_BUF_SIZE)
What could I possibly have
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 s
I added this to the 10-master imap-login, pop3-login and
submission-login, but keep this message
Doveconf still lists imap-urlauth-login with chroot = token-login, also
when changing this one to chroot = the error persists.
Fatal: fchown() failed for /var/dovecot/login: Operation not permitted
You should probably disable chrooting for login services if you are
running as non-root...
service imap-login {
chroot =
}
Aki
On 11.11.2019 14.59, Marc Roos via dovecot wrote:
> I am testing a bit with the proxy, and trying to run dovecot as a normal
> user. (with cap bind_service). I was
I am testing a bit with the proxy, and trying to run dovecot as a normal
user. (with cap bind_service). I was wondering what the minimum
configuration is for running like a proxy.
I am now getting issues like unable to chown on /var/dovecot/login, but
I do not need this in such a setup do I?
Good day Aki
Thanks ever so much for replying.
Interesting that you ask the version of dovecot. Any specific reason,
this question.?
To answer your question.
dovecot-core 1:2.2.27-3+deb9u5
Regards
Brent
On 2019/11/11 12:27, Aki Tuomi wrote:
What version are you running?
Aki
On 11.11.2019
On Mon, Aug 26, 2019 at 4:44 PM Mauricio Tavares wrote:
>
> On Mon, Aug 26, 2019 at 4:36 PM Joseph Tam via dovecot
> wrote:
> >
> > On Sun, 25 Aug 2019, Mauricio Tavares wrote:
> >
> > > Per [1] I decided to see what the response (base64-reply) I am
> > > submitting to dovecot looks like:
> > >
What version are you running?
Aki
On 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.
>
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 very
Good day Guys
I have been met with a very interesting set of error messages.
Here is the snippet(s)
https://pastebin.com/raw/nFf79Ebc
(Sorry for all the redacted REMOVED_*.)
Google is proving to be a bit challenging in helping and explaining.
Could anyone please share how something like this
29 matches
Mail list logo
