similar to: Broken auth-* sockets.

Keywords: dovecot, dict, quota, postgre sql, broken pipe, remote disconnected Having Dovecot 2.2.22 (fe789d2) with Postgre SQL 9.5 (9.5.5-0ubuntu0.16.04) as the backend. I do not understand why quota service is not working, not seeing it as a configuration error at least. My quotas are DICT/SQL based. OS: Ubuntu 16.0.4.1 32-bit (Linux XXX 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:36:54

hi, i've been running Exim & Dovecot together on the same box. Exim's been sharing Dovecot/SASL auth info over a local unix socket. works great. i'm now splitting Exim & Dovecot onto two different boxes. iiuc, Dovecot ONLY provides a UNIX (local) socket; *not* a TCP socket for over-the-network access. SUre, I could mount the Dovecot socket's volume over NFS ... but

Hello, just upgraded one of my testing machine from dovecot 1.2.15 to 2.0.7. After some trouble with permissions now all seems working, but when I stop dovecot I have these errors in log: Nov 9 17:08:07 in dovecot: master: Warning: Killed with signal 15 (by pid=20362 uid=0 code=kill) Nov 9 17:08:07 in dovecot: pop3-login: Error: read(anvil) failed: EOF Nov 9 17:08:07 in dovecot: imap-login:

Hi. I had working Exim 4.71 and Dovecot 1.2.9 SASL configuration on Ubuntu Lucid, but needed some features from dovecot2, so I installed 2.0.13 from https://launchpad.net/~carsten-uppenbrink-net/+archive/dovecot2 . Now I get Subj error while trying to authenticate via dovecot auth-client socket. However IMAP auth works fine with 2.0.13 and smtp auth worked fine until upgrade, so I think

Hi, I'm trying to set up exim (4.83) as a submission server, and need to set up the dovecot authentication in exim. I'm having an issue with that (documented at <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756258>) The problem is that exim doesn't follow the handshake as described here: <http://wiki2.dovecot.org/Design/AuthProtocol>. The wiki page says that the

Hello all. Just one quick stupid question. ;-( Im try to configure Exim + Dovecot 1.1.1 on FreeBSD 7.0 Then im try to send mail in logs im see this: deliver(admin at domain.off): Jul 02 13:52:22 Error: Can't connect to auth server at /var/run/dovecot/auth-master: No such file or directory %ls -al /var/run/dovecot/* srw-rw---- 1 exim wheel /var/run/dovecot/auth-client srw------- 1

Hello all, attached patch makes possible to use dovecot as an authentication backend for Exim 4. Reasons beyond this patch are simple: exim's authenticators require use of plaintext passwords and NTLM code in exim is quite outdated and hairy. Patch generated against Exim 4.43, but should apply to earlier versions too. Patch adds new 'dovecot' authenticator, which can be used as such:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi all, per the exim docs @: http://exim.org/exim-html-4.62/doc/html/spec_html/ch36.html a cyrus_sasl authenticator driveer is 'included' in exim core. given that Dovecot has become a very attractive alternative for an increasing number of folks, and there's a patch against exim 4.43 here:

Generically, yes, the hardware is supported. On Mon, Sep 18, 2017 at 11:42 PM, <ygrishin-lists at mail2.ca> wrote: > I will update the thread as soon as I get the hardware back. It was > something serious like artifacts or no video in X so that I had to resort to > proprietary drivers. > So the question is whether this hardware is supported or not. > > > On 2017-09-18

I'm seeing lots of: Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data (set_id=web) Jun 2 00:00:06 thebighonker exim[57439]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM IN)

Hi Heiko, Sorry for using your private email address. :/ I managed to get this working using local_user changes by adding ldap user verification there: local_user: debug_print = "R: local_user LDAP lookup for $local_part@$domain" driver = accept domains = +local_domains condition = CHECK_VIRTUAL_USER transport = dovecot_lmtp cannot_route_message = Unknown user Where

I am attempting to configure a dovecot 2.0 + exim + fetchmail (demon) combination on openSUSE 11.4, initially with the standard dovecot package (2.0.9-3.4-x86_64) and now with the later server:mail build service package (2.0.11-1.1-x86_64). I followed the instructions in http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL but despite the changes in conf.d/10-master.conf the permissions on

Hi, Heiko Schlittermann <hs at schlittermann.de> (Mo 21 Nov 2016 11:50:13 CET): > a) Routing stage > You need to interact with the user database dovecot uses. > Either you access the user database directory (flat file, LDAP, > whatever) or you use the ${readsocket?} feature of Exim to talk to > dovecot. The readsocket trick doesn't seem to work anymore. Using $

Hi, I installed a Emailserver based on Debian Sarge, exim (4.50-8sarge2) and dovecot (1.0.rc2-1bpo1). Delivering Mails with Exim to my Maildir works fine. Because I want to filter my messages with Sieve, I tried to deliver mails with deliver, but get the following error message (example with a testmail and user "Debian-exim", not delivered via Exim): --8<-- dovecot: 2006-09-19

On 04.06.2017 22:35, Larry Rosenman wrote: > On Fri, Jun 02, 2017 at 11:15:41AM -0500, Larry Rosenman wrote: >> I'm seeing lots of: > [snipped] >> Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM >> IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data

What seems to be the problem? I think you forgot to include a description of the issues you're seeing. On Sep 18, 2017 11:23 PM, <ygrishin-lists at mail2.ca> wrote: Hello looks like the device is not supported, the logs are as follows: --- # dmesg | grep nouve [ 2.789899] fb: switching to nouveaufb from VESA VGA [ 2.790060] nouveau 0000:01:00.0: NVIDIA GT218 (0a8d00b1) [

I've followed one of the pages on line specifically for installing fail2ban on Centos 7 and all looks fine. I've added a fail regex to /etc/fail2ban/filter.d/exim.conf as suggested on another page: \[<HOST>\]: 535 Incorrect authentication data which appears to be successfully matchnig lines in /var/log/exim/mail.log such as 2019-04-19 13:06:10 dovecot_plain

Hi to both adressed mailing lists, I followed the instructions in http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL exim.conf: | plain: | driver = dovecot | public_name = PLAIN | server_socket = /var/run/dovecot/auth-client | server_set_id = $auth1 | | login: | driver = dovecot | public_name = LOGIN | server_socket = /var/run/dovecot/auth-client |

> On 08 January 2019 at 19:39 Rupert Gallagher via dovecot <dovecot at dovecot.org> wrote: > > > Hello, > > I am mosty done with the upgrade, but there is a problem that keeps me awake at night: file ownership and permissions. > > It would be most helpful to have the following from Aki's live system: > > ls -halFR /var/run/dovecot My live config uses

> http://hg.dovecot.org/dovecot-2.2/rev/64c73e6bd397 ==> /var/log/dovecot/dovecot.log <== Aug 25 09:42:07 nihlus dovecot: imap(tlx at leuxner.net): Error: net_connect_unix(/var/run/dovecot/imap-hibernate) failed: Permission denied Aug 25 09:42:07 nihlus dovecot: imap(tlx at leuxner.net): Error: Couldn't hibernate imap client: Couldn't export state: Virtual mailboxes have no GUIDs