Displaying 20 results from an estimated 10000 matches similar to: "Fatal: Error in configuration file /etc/dovecot/dovecot.conf: protocols: Unknown protocol: sieve"
2019 Nov 08
3
MariaDB database for users and passwords?
On 07 Nov 2019, at 23:00, Ken Wright <wizard at bnnorth.net> wrote:
> I'm getting an error message saying "user unknown" when I send test
> emails to my server.
You need to look at the logs.
--
Everybody wants a rock to wrap a piece of string around
2017 Mar 01
2
dovecot lda bouncing postfix aliases
Recently configured postfix to use the dovecot lda as I wanted to use
sieve. Got that working a few days ago but noticed that I wasn't getting
any emails to aliases. Checked the logs and saw messages like:
Mar 1 08:19:59 carson postfix/lmtp[16949]: 0DCD22016BE: to=<
sales at example.com>, relay=carson.example.com[private/dovecot-lmtp],
delay=0.07, delays=0.01/0.01/0/0.04, dsn=5.1.1,
2016 Jul 03
2
Postfix/dovecot: user unrecognized, file permissions being misread
On Sun, 2016-07-03 at 15:56 -0500, Edgar Pettijohn wrote:
> doveconf -n would be helpful
Thank you:
lavarre:/var/mail/vhosts/privustech.com # doveconf -n
# 2.2.18: /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.8 (0c4ae064f307+)
# OS: Linux 4.1.26-21-default x86_64 openSUSE 42.1 (x86_64) ext4
auth_mechanisms = plain login
auth_verbose = yes
listen = *
log_path = /var/log/dovecot.log
2016 Jul 03
3
Postfix/dovecot: user unrecognized, file permissions being misread
Hello all. Have spent several days following the excellent tutorial:
http://www.binarytides.com/install-postfix-dovecot-debian/
but still fail to have the user recognized and am getting log entries
that the mail directories are 0755 when I can clearly see that they are
0774.
Very puzzling, any help would be deeply appreciated.
Best regards, Andy
=========== Details ===========
? I can add
2017 Feb 18
2
doveadm: Fatal: All your namespaces have a location setting
Hi,
I am trying to migrate mail from an old server and am receiving the
following error :
doveadm(user at example.com): Fatal: All your namespaces have a location
setting. Only namespaces with empty location settings are converted.
(One namespace should default to mail_location setting)
I found an old thread
(http://www.dovecot.org/list/dovecot/2012-September/068269.html) that
referred to
2017 Mar 02
1
dovecot lda bouncing postfix aliases
Oh wait, you crossposted to the postfix list. Please keep the discussion
there going, you have a postfix issue, not a dovecot one ;)
Tom
On 02-03-17 09:40, Tom Hendrikx wrote:
> Hi,
>
> Typically, postfix should resolve the aliases into user accounts that
> dovecot knows before you even start delivering to dovecot. You probably
> messed something up in the postfix config that
2016 Mar 22
2
Upgrade Dovecot from 2.1.17 to 2.2.13 lmtp child killed with signal 6
After upgrade Debian (Wheezy to Jessie) Dovecot version 2.1.17 is
upgraded to 2.2.13.
I have random crash of lmtp-a and I got lot message in queue. Any
solution for this problem?
---------- Postqueue ----------
7A5B77F72B 1160457 Tue Mar 22 10:10:15 ivan at jurisic.org
(delivery temporarily suspended: lost connection with
mail.jurisic.org[private/dovecot-lmtp] while sending end of data --
2015 Apr 30
0
timed out while receiving the initial server greeting
Am using ubuntu 14.04 and get a lot of errors like this
A84952061AC4 1457 Thu Apr 30 19:46:11
theeducationchannel at astarmathsandphysics.com
(delivery temporarily suspended: conversation with
astarmathsandphysics.com[private/lmtp]
timed out while receiving the initial server greeting)
postconf -n returns
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain
2019 Apr 11
2
auth-worker unknown user
pam(foobar at example.com,192.0.1.1,<9zMTUUCGNfHZzMpL>): unknown user (SHA1 of given password: ff75068c2f4d700a49dae204d56477a5ffa5d23d)
The password is correct, i.e. 'echo -n 'passed' | openssl dgst -sha1' matches.
The user is setup correctly in /etc/dovecot/users (the /etc/dovecot/users was copied from another known-good server, so the syntax is correct and appropriate
2015 Oct 30
2
updating and wsitching repo to yum.dovecot.fi - Unknown protocol: sieve
Hi,
winter is coming and so I start to clean up some left overs of the year.
One thing is to use the yum.dovecot.fi repository.
After installing the current availabel dovecot and dovecot-ee-pigeonhole
package and restarting dovecot I do get the error:
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf:
protocols: Unknown protocol: sieve
Is the sieve protocol an extra
2019 Jan 16
2
auth-worker: Error: double free or corruption (fasttop)
Dear list,
since the distri upgrade to glibc 2.28, i can't build working dovecot
binary's.
Older with glibc 2.27 are working. The distri is LFS based.
MariaDB 10.2.18 and 10.3.11 makes no difference. Having this on
different systems.
Messages Log:
Dec 19 17:10:38 test kernel: traps: auth[30189] general protection
ip:7f4b96d6598c sp:7ffef1f31710 error:0 in
2013 May 31
1
dovecot-lmtp does not work
Dear Community,
I've got a weird problem regarding lmtp setup with dovecot 2.0.19 on ubuntu
12.04.2 LTS. My reference of the configuration is at
https://library.linode.com/email/postfix/postfix2.9.6-dovecot2.0.19-mysql ,
and my configuration is identical to it with the exception of opening the
110 pop3 port, and enabling plain text auth. Everything from imap, smtp,
pop3 (including auth) works
2015 Oct 30
2
updating and wsitching repo to yum.dovecot.fi - Unknown protocol: sieve
Am 30.10.15 um 11:49 schrieb Teemu Huovila:
>
>
> On 30.10.2015 12:18, G?tz Reinicke - IT Koordinator wrote:
>> Hi,
>>
>> winter is coming and so I start to clean up some left overs of the year.
>>
>> One thing is to use the yum.dovecot.fi repository.
>>
>> After installing the current availabel dovecot and dovecot-ee-pigeonhole
>> package
2017 Nov 03
2
stats module
Thanks for your suggestions, Steffen.
Running doveconf -n shows no errors and also, sadly, no mention of the
stats listener:
?? (master=)??
? [T] jeff at nantes-1:p27 $ doveconf -n
# 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.13 (7b14904)
# OS: Linux 4.4.0-97-generic x86_64 Ubuntu 16.04.3 LTS
auth_mechanisms = plain login
auth_socket_path =
2017 Feb 13
3
sieve file backend: invalid option `active=~/.dovecot.sieve'
Hi,
I am seeing the followin error in my logs (doveconf -n at the bottom of
this mail):
Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error:
cs3NOQ7moVj4sQXXXXX: sieve: sieve file backend: invalid option
`active=~/.dovecot.sieve'
Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error:
cs3NOQ7moVj4sQXXXXX: sieve: failed to access user's Sieve script
2017 Nov 03
2
stats module
Sorry, Aki, I don't follow you.? Did I do it wrong in the file 91-stats
that I shared in my original mail (attached here)?
Jeff
On 03/11/17 16:50, Aki Tuomi wrote:
> You need to add the stats listener, by yourself.
>
> Aki
>
>> On November 3, 2017 at 5:19 PM Jeff Abrahamson <jeff at p27.eu> wrote:
>>
>>
>> Thanks for your suggestions, Steffen.
2019 Nov 18
2
Doveadm replicator ssl issues
Hello, I have 2 Dovecot 2.3.8 servers running SSL with valid wildcard
certificates.
Email clients connect fine, https://www.immuniweb.com/ssl/ tests show
certificates are ok.
However I can't make replication work when I add ssl = yes.
Without ssl it works ok.
I added verbose_ssl in config and error log shows:
dovecot: doveadm(149.x.x.x): Error: SSL handshake failed: SSL_accept()
2018 Dec 10
2
Replication fatal error
Dear suscribers.
I just dont understand this error. Don't know where to look first. If
someone have already meet this problem...
Dec 10 16:06:17 prudence dovecot: dsync-server(address at domain.fr):
Panic: file dsync-brain-mailbox.c: line 370
(dsync_brain_sync_mailbox_deinit): assertion failed: (brain->failed)
Dec 10 16:06:17 prudence dovecot: dsync-server(address at domain.fr):
2019 Feb 28
2
dovecot[1511]: auth-worker: Fatal: master: service(auth-worker): child 17009 killed with signal 11
This bug report is similar to this issue:
https://www.dovecot.org/list/dovecot/2017-May/108116.html
<https://www.dovecot.org/list/dovecot/2017-May/108116.html>
I know it is not enough info, but every kill follows with this info:
Feb 28 16:57:50 server dovecot[1511]: auth-worker: Fatal: master:
service(auth-worker): child 17009 killed with signal 11 (core dumps
disabled -
2019 Mar 18
4
LDAP users issue
Hi Team,
I have enabled LDAP authentication with webmail client and it works
successfully. But I found an error with LDAP user's mail. Email is not
loaded when I log with an LDAP user. Login phase is successful and mail box
is the issue. I created a mail user without including LDAP and that user
works fine.
Issue comes only with LDAP users.
*Anushka Bandara*
Research Engineer
Lanka Software