similar to: lmtp: Error: Temp file creation to /tmp/ ... failed: No such file or directory on incoming mails with attachments

Displaying 20 results from an estimated 5000 matches similar to: "lmtp: Error: Temp file creation to /tmp/ ... failed: No such file or directory on incoming mails with attachments"

2017 Jun 08
0
lmtp: Error: Temp file creation to /tmp/ ... failed: No such file or directory on incoming mails with attachments
On 07.06.2017 23:42, Lars-S?ren Steck wrote: > Dear list, > > I'm currently facing problems when receiving eMails with attachments, at > least sometimes. > > My mailserver is set up with the tool 'Mailcow', and hence is based on > Dovecot (2.2.22 (fe789d2)) and Postfix. > > Usually, there are no problems with receiving mails. If a mail has an > attachment,
2019 Oct 01
4
dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp
I set up system copying all mails to a backup system. This used to work without a hitch - now in the last few days mails would pile up in the Postfix Queue, waiting to be delivered using the lmtp transport into dovecot. So dovecot was being slow, but why? After all, nothing changed. After reading some articles on stackoverflow I found a way of finding out which file gets the most IO: % sysdig
2017 Nov 30
3
Plugin 'sieve_imapsieve' not found
Hello, when Dovecot launches (and pretty much at any action afterwards) it always throws following error: | managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib/dovecot/modules/sieve | config: Error: managesieve-login: dump-capability process returned 89 dovecot-sieve and dovecot-managesieved are both installed and the only plugin in the mentioned folder is
2017 Nov 03
0
stats module
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. > > 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
2017 Nov 03
0
stats module
On Fri, Nov 3, 2017 at 9:35 AM, Jeff Abrahamson <jeff at p27.eu> wrote: > 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
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 =
2014 Sep 15
1
migration from cyrus with dsync sieve problem
Hi all i'm migrating a cyrus imapd server to dovecot with dsync everyting seems working but sieve rules are not copied to dovecot server I searched for documentation but without any luck I use the configuration below with doveadm -v -o mail_fsync=never backup -R -u emailaddr imapc: Is sieve supported with dsync? How I can specify sieve server address and port? # 2.2.13.21 (606efd4a4f35):
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.
2017 Nov 10
0
Sieve global path?
Set the sieve_global_dir like this. /etc/dovecot/conf.d/99-mystuff.conf: . . plugin { ? sieve???????????????? = ~/Maildir/dovecot.sieve ? sieve_dir???????????? = ~/Maildir/sieve ? sieve_global_dir????? = /etc/dovecot/sieve/global/ ? sieve_before????????? = /etc/dovecot/sieve/before.d/ #? sieve_before2??????? = #? sieve_before3??????? = ? sieve_after?????????? = /etc/dovecot/sieve/after.d/ #?
2017 Jun 05
0
fts_solr: uid0?
I'm seeing the following: Jun 5 11:10:52 thebighonker dovecot: imap(ler): Error: fts_solr: received invalid uid '0' Is there something I can get for you to debug? doveconf -n: # 2.2.30.1 (eebd877): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.18 (29cc74d) # OS: FreeBSD 11.1-PRERELEASE amd64 auth_debug_passwords = yes auth_default_realm = lerctr.org auth_mechanisms
2015 Feb 12
0
Dovecot dsync not replicating ".dovecot.sieve -> .sieve/managesieve.sieve" / setactive
Am 12.02.2015 um 15:47 schrieb Martin ?tefany: > Hello, > > I've ran into problem with Dovecot and dsync replication. Everything > works perfectly, including replication of sieve scripts, except fact > that if user activates the 'managesieve' ruleset (I'm using currently > Roundcubemail) on "mail1" host, it wouldn't be activated on
2017 Jun 30
0
uid '0' from fts_solr?
I'm getting lots of: Jun 30 14:41:34 thebighonker dovecot: imap(ler/14135): Error: fts_solr: received invalid uid '0' in my logs. Ideas? doveconf -n: # 2.2.31 (65cde28): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: FreeBSD 11.1-BETA2 amd64 auth_default_realm = lerctr.org auth_mechanisms = plain login auth_realms = lerctr.org
2017 Jun 16
0
Error: fts_solr: received invalid uid '0'?
I'm getting a lot of: Jun 16 11:40:40 thebighonker dovecot: imap(ler/58755): Error: fts_solr: received invalid uid '0' Jun 16 11:40:40 thebighonker dovecot: imap(ler/58755): Error: fts_solr: received invalid uid '0' in my logs. What can I supply to help get to the bottom of it? doveconf -n: # 2.2.30.2 (c0c463e): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version
2017 Nov 03
3
stats module
On 03/11/17 17:43, Mark Moseley wrote: > > > On Fri, Nov 3, 2017 at 9:35 AM, Jeff Abrahamson <jeff at p27.eu > <mailto:jeff at p27.eu>> wrote: > > 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:
2017 Nov 09
2
Sieve global path?
Hello, I am building a new server on CentOS 7 and the global sieve filter can not be loaded. The debug shows: Nov? 9 15:23:09 mail dovecot: lmtp(11182, gao at mydomain.com): Debug: sieve: Pigeonhole version 0.4.2 initializing Nov? 9 15:23:09 mail dovecot: lmtp(11182, gao at mydomain.com): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global'
2017 Jul 18
0
passwd-file, getting invalid uid 0
On Tue, Jul 18, 2017 at 3:31 PM, Larry Rosenman <larryrtx at gmail.com> wrote: > That didn't change it :( > Jul 18 15:28:14 thebighonker dovecot: auth-worker(77908): Error: > passwd-file /etc/passwd: User root has invalid UID '0' > Jul 18 15:28:14 thebighonker dovecot: auth-worker(77908): Error: > passwd-file /etc/passwd: User toor has invalid UID '0' >
2017 Jul 18
0
passwd-file, getting invalid uid 0
Anyone? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx at gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 On 7/13/17, 2:42 PM, "Larry Rosenman" <larryrtx at gmail.com> wrote: Per my earlier post about system and virtual users, I have everything working, but I'm seeing the
2017 Jul 19
0
passwd-file, getting invalid uid 0
The alias works fine. It's just an auth request. I'll live with it. Sent from my Sprint Samsung Galaxy S8+. -------- Original message --------From: Bill Shirley <bill at KnoxvilleChristian.org> Date: 7/18/17 11:24 PM (GMT-06:00) To: dovecot at dovecot.org Subject: Re: passwd-file, getting invalid uid 0 Unless your userid is also zero, my guess is that Exim isn't using the
2017 Dec 25
0
Sieve 0.5.0/Dovecot 2.3.0
FTR, this is being delivered via LMTP from Exim using the recommended transport / director. headers from one of my tests: Return-Path: <ler at lerctr.org> Delivered-To: ler at lerctr.org Received: from thebighonker.lerctr.org by thebighonker.lerctr.org with LMTP id EW4ZBgV7QVoIDwAAu+mOrA (envelope-from <ler at lerctr.org>) for <ler at lerctr.org>;
2017 Jul 13
1
System users lookup via PAM: strip the domain name?
I have a need for the following: Real system users in /etc/{passwd,shadow} (actually PAM on FreeBSD) wirhOUT @domain in /etc/passwd Virtual Users in SQL (with full user at domain in the DB) When I have auth_username_format = %Ln I can?t auth the Virtual Users, and if I have auth_username_format = %Lu I can?t auth System users. Is there a compromise somewhere? Current doveconf ?n