Re: Issue with LMTP proxying and port number

{   executable = managesieve-login director } service pop3-login {   executable = pop3-login director } service quota-warning {   executable = script /etc/dovecot/quota-warning.sh   user = dovecot } ssl_cert = wrote:   On 31 Dec 2018, at 0.43, Laz C. Peterson wrote: Hello there, Everything was working

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. B

Re: Symbolic link for sieve script not created by dsync

for 14.04 are so far behind … ~ Laz Peterson Paravis, LLC > On Aug 15, 2016, at 12:12 PM, Laz C. Peterson wrote: > > Hello Dovecot ~ > > I know this bug has been discussed previously for other versions of dsync, > pigeonhole and dovecot … But we still can’t get dsync to c

Symbolic link for sieve script not created by dsync

Hello Dovecot ~ I know this bug has been discussed previously for other versions of dsync, pigeonhole and dovecot … But we still can’t get dsync to create the symbolic link for the sieve script after it is created on a replicated server. We are running Ubuntu 16.04.1 with the official Ubuntu do

Re: Slow auth

We had this issue as well - switch your primary authentication to LDAP and make sure it is attempting those auth sources first before any PAM sources. You also don’t need to have your Dovecot server joined to the domain by doing it this way, which is nice. We were previously using PAM auth thr

Re: dovecot proxy/director and high availability design

t > sounds reasonable. I admit its a fair amount of moving parts and areas for > failure but I think it maybe the balance needed to achieve the service level > availability I'm after while still allowing for maintenance on the systems > w/o clients noticing. > &g

Re: dovecot proxy/director and high availability design

I’m trying to do this too. But the goal would be simply for automatic failover to the other datacenter. Everything is working if the server’s unique hostname is entered, but I want to do something like round robin DNS that mail clients will automatically attempt to connect to the other IP if t

Re: Dovecot auth username mapping

AM, Laz C. Peterson wrote: > > 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

Re: Dovecot auth username mapping

um 01:41 schrieb Laz C. Peterson: >> >> I did attempt to switch the PAM/Kerberos authentication to Dovecot >> LDAP authentication, but now performance is unbelievably slow. >> Any thoughts to this? > > In case you have multiple passdb backends, it could be, that LDAP only

Re: Dovecot auth username mapping

n option though, as it does > serve the purpose. I just can’t figure out how to fix the performance issue. > Any thoughts to this? > > ~ Laz Peterson > Paravis, LLC > Ph: 951.319.3240 x201 > >> On Jul 1, 2015, at 3:24 PM, Axel Luttgens wrote: >> >> >

Re: Dovecot auth username mapping

how to fix the performance issue. Any thoughts to this? ~ Laz Peterson Paravis, LLC Ph: 951.319.3240 x201 > On Jul 1, 2015, at 3:24 PM, Axel Luttgens wrote: > > >> Le 1 juil. 2015 à 04:38, Laz C. Peterson > >> a écrit : >> >> I have an interesting

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@PARAVIS.LOCAL