similar to: Issue with LMTP proxying and port number

Displaying 20 results from an estimated 11000 matches similar to: "Issue with LMTP proxying and port number"

2018 Dec 31
2
Re: Issue with LMTP proxying and port number
Hello Sami, yes, see below. We run Dovecot at a different versions, mainly 2.2.10 (CentOS), 2.2.22 (Ubuntu) and now 2.2.36 (CentOS). ?The issue is weird, because it only happened after the update from 2.2.10->36. ?Just to understand it would be great. I'm actually checking out the configs now ... Our SQL userdb does not specify port. ?So I'm guessing this may be to blame? (This was
2019 Jan 12
1
Issue with LMTP proxying and port number
Op 06/01/2019 om 17:05 schreef Stephan Bosch: > > Op 31/12/2018 om 06:32 schreef Laz C. Peterson: >> Hello Sami, yes, see below. >> >> We run Dovecot at a different versions, mainly 2.2.10 (CentOS), >> 2.2.22 (Ubuntu) and now 2.2.36 (CentOS). ?The issue is weird, because >> it only happened after the update from 2.2.10->36. ?Just to >> understand it
2015 Jul 01
4
Dovecot auth username mapping
Thank you for the response Axel. I will look into that. I did attempt to switch the PAM/Kerberos authentication to Dovecot LDAP authentication, but now performance is unbelievably slow. For example, with PAM/Kerberos, a user can log into webmail and have all of their emails/folders showing almost immediately. When using Dovecot LDAP, it takes literally 8-10 seconds to see the same thing. I
2015 Jul 01
2
Dovecot auth username mapping
I have an interesting case here ? Virtual mailboxes, domain/username/aliases stored in MySQL, authentication done using PAM. PAM authenticates through Kerberos, which are internal realms and not the email domains ? for example, my username would be laz at PARAVIS.LOCAL <mailto:laz at PARAVIS.LOCAL> and my email address would be laz at paravis.net <mailto:laz at paravis.net>. All of
2015 Jul 02
1
Dovecot auth username mapping
Peter, Yes that is a possibility. I will try disabling PAM (or switching the auth order) and see if that makes a difference. Thanks for the suggestion! ~ Laz Peterson Paravis, LLC Ph: 951.319.3240 x201 > On Jul 1, 2015, at 11:34 PM, Peter Chiochetti <pch at myzel.net> wrote: > > Am 2015-07-02 um 01:41 schrieb Laz C. Peterson: >> >> I did attempt to switch the
2015 Jul 21
3
dovecot proxy/director and high availability design
Round-robin DNS last I checked can be fraught with issues. While doing something else I came up with this idea: Clients --> Load Balancer(HAProxy) --> Dovecot Proxy(DP) --> Dovecot Director(DD) --> MS1 / MS2. When DP checks say user100 it'll find a host=DD-POD1 that returns two IPs, those of the two DD that sit in front of POD1. This DD pair is the only pair in the ring and
2015 Jul 20
3
dovecot proxy/director and high availability design
I'm trying to determine which dovecot components to use and how to order them in the network path from client to mail store. If I have say 1,000 users, all stored in MySQL (or LDAP) and have 4 mail stores, configured into 2, 2 node pods. MS1 and MS2 are pod1 and are configured with replication (dsync) and host users 0-500. MS3 and MS4 are pod2 and are configured with replication between
2013 Oct 02
2
Username issue with Dovecot LDA, IMAP and Winbind Authentication
Hi there Dovecot community -- I'll try to make this short. Here's the setup ? Ubuntu 12.04, Postfix, Dovecot, along with Amavis/Clamd/Spamassassin. Postfix is currently receiving emails for virtual users in multiple domains, all of which are authenticating through Winbind to Windows AD servers. The users log in to the POP/IMAP/SMTP services using the format user at domain.corp (the
2018 Dec 30
0
Issue with LMTP proxying and port number
> On 31 Dec 2018, at 0.43, Laz C. Peterson <laz at paravis.net> wrote: > > Hello there, > > Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but after updating to version 2.2.36, our director servers are not able to proxy LMTP. > > We are sending mail from exim to the local Dovecot LMTP socket, which then used to send it to our internal mail servers on
2015 Jul 21
2
dovecot proxy/director and high availability design
I think RR DNS is the only viable solution under these circumstances. If you can cope with the fact that failovers won't be seamless, I don't think there's anything wrong with that though. On 07/21/2015 11:54 AM, Laz C. Peterson wrote: > The consensus seems to say no to RR DNS ? I am going to take that into serious consideration. > > With this proxy setup you describe, what
2016 Jun 07
3
Slow auth
On Tue, 2016-06-07 at 11:45 -0500, Edgar Pettijohn wrote: > You have Pam as your passdb driver. Yes, because I have to. How else would I get Dovecot to authenticate users against my FreeIPA server? -- Ranbir -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: This is a digitally signed
2019 Jan 06
0
Issue with LMTP proxying and port number
Op 31/12/2018 om 06:32 schreef Laz C. Peterson: > Hello Sami, yes, see below. > > We run Dovecot at a different versions, mainly 2.2.10 (CentOS), 2.2.22 > (Ubuntu) and now 2.2.36 (CentOS). ?The issue is weird, because it only > happened after the update from 2.2.10->36. ?Just to understand it > would be great. > > I'm actually checking out the configs now ... Our
2019 Dec 04
3
Can't see a specific mail in thunderbird but with mobile mail client
Hi, please record IMAP rawlog from the client session to see what the client requests and what dovecot responds. https://wiki2.dovecot.org/Debugging/Rawlog <https://wiki2.dovecot.org/Debugging/Rawlog> Sami > On 4 Dec 2019, at 10.44, J. Echter via dovecot <dovecot at dovecot.org> wrote: > > > Am 03.12.19 um 12:32 schrieb J. Echter via dovecot: >> Hi, >>
2018 Nov 13
1
dovecot lmtp thinks that "disk quota exceeded" is "internal error"
> On 13 Nov 2018, at 21.06, Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote: > > On 13/11/2018 15:54, Arkadiusz Mi?kiewicz wrote: >> >> 2.2.36 (not migrated to 2.3 yet) reports such problem: >> >>> Nov 13 15:50:58 mbox dovecot: lmtp(xxx): session=<ACYRCtLk6ltiEQAALZVUYQ>, Error: open(/var/mail/xxx/mailboxes.lock1bf6ad16b7b8b703) failed: Disk quota
2018 Dec 31
2
Issue with LMTP proxying and port number
Hello there, Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but after updating to version 2.2.36, our director servers are not able to proxy LMTP. We are sending mail from exim to the local Dovecot LMTP socket, which then used to send it to our internal mail servers on port 24. Besides the update, nothing has changed in the config files.? The configuration has been working
2019 Jan 06
2
Issue with LMTP proxying and port number
Op 06/01/2019 om 11:50 schreef Stephan Bosch: > > Op 31/12/2018 om 23:59 schreef Steven Craig: >> Hello there, >> >> Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but >> after updating to version 2.2.36, our director servers are not able >> to proxy LMTP. >> >> We are sending mail from exim to the local Dovecot LMTP socket, which
2018 Nov 13
3
dovecot lmtp thinks that "disk quota exceeded" is "internal error"
2.2.36 (not migrated to 2.3 yet) reports such problem: > Nov 13 15:50:58 mbox dovecot: lmtp(xxx): session=<ACYRCtLk6ltiEQAALZVUYQ>, Error: open(/var/mail/xxx/mailboxes.lock1bf6ad16b7b8b703) failed: Disk quota exceeded > Nov 13 15:50:58 mbox dovecot: lmtp(xxx): session=<ACYRCtLk6ltiEQAALZVUYQ>, Error: Couldn't create mailbox list lock /var/mail/xxx/mailboxes.lock:
2019 Jan 06
1
Issue with LMTP proxying and port number
Op 06/01/2019 om 17:02 schreef Steven Craig: > Thanks, its a weird one. > > On 1/6/2019 8:00 AM, Stephan Bosch wrote: >> >> Op 06/01/2019 om 11:50 schreef Stephan Bosch: >>> >>> Op 31/12/2018 om 23:59 schreef Steven Craig: >>>> Hello there, >>>> >>>> Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but
2015 Jul 02
0
Dovecot auth username mapping
It?s actually unbelievable how much slower LDAP auth is than PAM. Does anyone have any suggestions how I can improve Dovecot LDAP auth? I have tried caching authentications and that doesn?t help either. ~ Laz Peterson Paravis, LLC Ph: 951.319.3240 x201 > On Jul 1, 2015, at 4:41 PM, Laz C. Peterson <laz at paravis.net> wrote: > > Thank you for the response Axel. I will look
2019 Jul 31
4
doveadm: Error: open(/proc/self/io) failed
> On 30 Jul 2019, at 22.53, Tom Diehl via dovecot <dovecot at dovecot.org> wrote: > > On Tue, 30 Jul 2019, Reio Remma via dovecot wrote: > >> On 30.07.2019 20:07, Tom Diehl via dovecot wrote: >>> >>> Does anyone have an Idea how to fix this? >> >> Perhaps see if there are any denials in SELinux audit log: > > Selinux is in