On Sun, 25 Mar 2018, Lothar Paltins wrote:
But very often the login from thunderbird to the dovecot server takes a
very long time, even if thunderbird and dovecot are running on the same
machine. It can take more than a minute until I can read a message. I
dont't have this problem with the rem
On Mon, Mar 26, 2018 at 15:57:01 +0300, Apollon Oikonomopoulos wrote:
...
> I'd be happy to test the patch, thanks!
Ok, try the attached patch. (It is a first pass at the issue, so it may not
be the final diff that'll end up getting committed. It'd be good to know if
it actually fixes the issue
Hi Aki,
On 15:55 Mon 26 Mar , Aki Tuomi wrote:
> On 26.03.2018 15:49, Apollon Oikonomopoulos wrote:
> > Hi,
> >
> > The dovecot 2.3.0.1 Debian package currently fails to build on all
> > big-endian architectures[1], due to murmurhash3 tests failing. The
> > relevant output from e.g. s390x is
On 26.03.2018 15:49, Apollon Oikonomopoulos wrote:
> Hi,
>
> The dovecot 2.3.0.1 Debian package currently fails to build on all
> big-endian architectures[1], due to murmurhash3 tests failing. The
> relevant output from e.g. s390x is:
>
> test-murmurhash3.c:22: Assert(#8) failed: memcmp(result
Hi,
The dovecot 2.3.0.1 Debian package currently fails to build on all
big-endian architectures[1], due to murmurhash3 tests failing. The
relevant output from e.g. s390x is:
test-murmurhash3.c:22: Assert(#8) failed: memcmp(result, vectors[i].result,
sizeof(result)) == 0
test-murmurhash3.c:22
On 03/26/2018 02:03 PM, Vladimir Tiukhtin wrote:
> Do you have any document describing "special" names? Thanks
It's documented here.
https://wiki2.dovecot.org/Services#auth
I have to agree that it's kind of confusing. Would be clearer if it had a e.g.
type=userdb setting.
Hi guys,
I have an issue when I try to backup a remote mailbox, apparently it
exits with no errors, it creates the mailbox folders in local, but it
doesn't copy any email.
doveadm -Dv -o dsync_features=empty-header-workaround -o
imapc_host=secure.emailsrvr.com -o imapc_password='passwd' back
Nothing definitive. It's just that the socket expects certain type of
input, this is comparable of trying to configure postfix to speak to
imap-master socket. There is no reason why it should work.
Aki
On 26.03.2018 15:03, Vladimir Tiukhtin wrote:
>
> Hi
>
> And why it is not working with that n
Hi
And why it is not working with that name? Do you have any document
describing "special" names? Thanks
Vladimir
On 26/03/18 13:02, Aki Tuomi wrote:
Dovecot has some special socket names, auth-userdb is one of those.
Aki
On 26.03.2018 14:47, Vladimir Tiukhtin wrote:
Hi
What you have
Dovecot has some special socket names, auth-userdb is one of those.
Aki
On 26.03.2018 14:47, Vladimir Tiukhtin wrote:
>
> Hi
>
> What you have suggested works.
>
> service auth {
> unix_listener /var/spool/postfix/private/auth {
> user = postfix
> group = postfix
>
Hi
What you have suggested works.
service auth {
unix_listener /var/spool/postfix/private/auth {
user = postfix
group = postfix
mode = 0600
}
}
This works as well:
service auth {
unix_listener /var/run/dovecot/auth {
owner = postfix
group =
Hello list,
Here's how auth-worker logs :
Mar 26 10:56:38 auth-worker(1753): Info:
sql(someu...@mydomain.tld,202.107.34.250): Password mismatch
I would like to add the service used, like this :
Mar 26 10:56:38 auth-worker(1753): Info: service=smtp
sql(someu...@mydomain.tld,202.107.34.250):
Hi,
I've recently started using Dovecot as our main mail storage, and it's
performing great. But I have a question/problems with quotas.
First of we are using:
dovecot --version
2.2.32 (dfbe293d4)
Dovecot is a part of a pre set environment (mailcow-dockerized)
Aside the inbox namespace we h
To quote Night On Earth, huomenta Aki!
owner = postfix should be user = postfix
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf
line 4: Unknown setting: service { unix_listener { owner
Thanks and good luck!
Reio
On 26.03.18 11:55, Aki Tuomi wrote:
Ah i see.
try this
Ah i see.
try this:
dovecot.conf:
service auth {
unix_listener /var/spool/postfix/private/auth {
owner = postfix
group = postfix
mode = 0600
}
}
postfix.conf:
smtpd_sasl_path = private/auth
Aki
On 26.03.2018 11:25, Vladimir Tiukhtin wrote:
>
> Hello
>
> Yes, p
Hello
Yes, please find my postfix config:
smtpd_sasl_type = dovecot
#smtpd_sasl_path = /var/run/dovecot/auth
smtpd_sasl_path = /var/run/dovecot/auth-userdb
smtpd_sasl_auth_enable = yes
smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated,
reject_unauth_destination
As I ment
On 26.03.2018 10:42, Jan-Pieter Cornet wrote:
> I tried setting the "destuser" setting on the LMTP director as
> follows, to preserve the original envelope rcpt:
>
> protocol lmtp {
> auth_socket_path = director-userdb
> passdb {
> driver = ...
> override_fields = destuser=%{orig_user
I tried setting the "destuser" setting on the LMTP director as follows, to
preserve the original envelope rcpt:
protocol lmtp {
auth_socket_path = director-userdb
passdb {
driver = ...
override_fields = destuser=%{orig_user}
}
}
The passdb driver would return the appropriate "user
Did you tell postfix it's talking to dovecot?
Aki
On 25.03.2018 20:29, Vladimir Tiukhtin wrote:
>
> Hi guys.
>
> I am getting strange error:
>
>
> BUG: Unknown command in userdb socket: CPID?2625
>
>
> I am using service auth to authenticate users on postfix.
>
> *My OS*:
>
> # cat /etc/os-rele
19 matches
Mail list logo
