Greetings,
The iteration machinery uses the LDAP search base set with the "base"
directive (typically from dovecot-ldap.conf.ext); the same base used
during nominal operations (e.g., passdb/userdb searches). Consider a
directory:
dc=ROOT
|_ dc=foo,dc=com,dc=ROOT(foo.com subtree)
|_ dc=ba
>doveadm user mailtest
field value
uid 1002
gid 8
home/home/mailtest
mailmbox:~/mail:INBOX=/var/mail/mailtest
system_groups_user mailtest
Looks fine.
[log files] I'll try to locate them.
Your best hope. Maybe this helps
doveconf -n | grep log_
Or just
Op 10/18/2016 om 10:28 PM schreef Sven Roellig:
> Hi,dovecot is create an Fatal Panik Error.
> : Fatal: master: service(lmtp): child 3369 killed
> with signal 6 (core dumps disabled)
> <1jx3DhuCBlg1DQAAWm89Cw>: Panic: file lda-sieve-plugin.c: line 447
> (lda_sieve_execute_scripts): assertion fai
Hi,dovecot is create an Fatal Panik Error.
: Fatal: master: service(lmtp): child 3369 killed with
signal 6 (core dumps disabled)
<1jx3DhuCBlg1DQAAWm89Cw>: Panic: file lda-sieve-plugin.c: line 447
(lda_sieve_execute_scripts): assertion failed: (script != NULL)
<1jx3DhuCBlg1DQAAWm89Cw>: Error: Raw
This will be fixed on next release, 2.2.26. We won't backport it to
latest stable, sorry.
Aki
On 18.10.2016 15:36, Pierre Jaury wrote:
> Hello,
>
> I can confirm the issue is fixed. Do you have a policy to backport the
> patch at least to the latest stable?
>
> Regards,
>
> On 10/17/2016 11:45 P
Hello,
I can confirm the issue is fixed. Do you have a policy to backport the
patch at least to the latest stable?
Regards,
On 10/17/2016 11:45 PM, Aki Tuomi wrote:
> On 10/16/2016 11:16 PM, Pierre Jaury wrote:
>> Hello,
>>
>> I am using a dict proxy for my sieve
> Date: Tuesday, October 18, 2016 13:12:39 +0200
> From: Moi
>
> Thank you. It worked and I now have several log files to check.
>
> In the meantime, I've tried once again to send a message to
> "mailtest" from an outside address; this time, I got an error reply:
>
> This report relates to a m
On Monday 17 of October 2016, KT Walrus wrote:
> > On Oct 17, 2016, at 2:41 AM, Arkadiusz Miśkiewicz wrote:
> >
> > On Monday 30 of May 2016, Arkadiusz Miśkiewicz wrote:
> >> Is there a way to log SNI hostname used in TLS session? Info is there in
> >> SSL_CTX_set_tlsext_servername_callback, dove
> I always install "locate" and whenever I change anything do as root
"/usr/bin/updatedb"
> then you can type
> "locate *.log"
Thank you. It worked and I now have several log files to check.
In the meantime, I've tried once again to send a message to "mailtest" from
an outside address; this time,
On 18.10.2016 13:42, mick crane wrote:
> On 2016-10-18 07:55, Moi wrote:
>>> Two things to check:
>>>
>> ># What does dovecot think user "mailtest" has?
>> >doveadm user mailtest
>>
>> I get this:
>> field value
>> uid 1002
>> gid 8
>> home/home/mailtest
>> mailmbox:~/
On 2016-10-18 07:55, Moi wrote:
Two things to check:
> # What does dovecot think user "mailtest" has?
> doveadm user mailtest
I get this:
field value
uid 1002
gid 8
home/home/mailtest
mailmbox:~/mail:INBOX=/var/mail/mailtest
this looks wrong I don't think /var should
On 18.10.2016 11:47, Ximo Mira wrote:
> Hi,
>
> Last night we tried a traffic bypass in an existing mail environment before
> migration to new Dovecot backend platfom using Dovecot proxy. We are using an
> LDAP value for checking the proxy host of the user.
>
> POP traffic was running flawles
Hi,
Last night we tried a traffic bypass in an existing mail environment before
migration to new Dovecot backend platfom using Dovecot proxy. We are using an
LDAP value for checking the proxy host of the user.
POP traffic was running flawlessly, but IMAP connections started to drop when
few
13 matches
Mail list logo
