Displaying 20 results from an estimated 11000 matches similar to: "dovecot: config: Error: BUG: Config client connection sent too much data"
2017 Aug 25
2
dovecot: config: Error: BUG: Config client connection sent too much data
Hello,
Absolutely. Here is the output of doveconf -n:
# doveconf -n
# 2.2.31 (65cde28): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.19 (e5c7051)
# OS: Linux 4.9.36-x86_64-linodexx x86_64 Arch Linux
auth_mechanisms = plain login
base_dir = /var/run/dovecot/
dict {
expire = ldap:/etc/dovecot/dovecot-ldap.conf.ext
quota = ldap:/etc/dovecot/dovecot-ldap.conf.ext
}
doveadm_password = #
2017 Aug 25
0
dovecot: config: Error: BUG: Config client connection sent too much data
> On August 25, 2017 at 9:11 AM Tony <tony at kode.email> wrote:
>
>
> Hello,
>
> Today I started noticing a very odd Dovecot error in the mail logs
> across 2 replicated Dovecot hosts via dsync. I have searched the Dovecot
> archives, Google, back tracked, downgraded Dovecot to earlier versions
> from earlier this year and
2017 Aug 26
0
dovecot: config: Error: BUG: Config client connection sent too much data
Did some additional testing with these results.
* Configured a new Dovecot host (copied over existing config from 1 of
the replicated hosts.
* Verified permissions on new host
drwxr-xr-x 3 root root 4096 Aug 26 00:05 /etc/dovecot/
drwxr-xr-x 5 root dovecot 800 Aug 26 02:50 /var/run/dovecot/
Made sure address matches new host:
service lmtp {
user = vmail
inet_listener lmtp {
address =
2017 Dec 30
3
Updated Dovecot 2.3.0 now getting 2 strange log errors
I did some more digging around and found this is reproducible on
multiple hosts running the same version of Dovecot/Pigeonhole/Postfix.
The problem resurfaces on any host to an account with enabled
Vacation/OOO response. The Vacation/OOO reply filter was created in
Roundcubemail, but has been fine for years. One thing to note is in
Dovecot 2.3.0 I did enable UTF8, but even if I disable UTF8
2017 Aug 22
2
store into mailbox 'Junk' aborted
Hi,
I've just switch from procmail to pigeonhole, and I'm seeing an issue
(twice in six hours).
I have spamassisn running via postfix milter, and dropping off via main.cf
"mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp"
The issue is that I get a sequence of these log messages:
Aug 21 19:43:59 lmtp(toppk): Debug: Junk: Mailbox opened because: lib-lda
delivery
Aug 21
2019 Feb 05
3
[Bug 109558] New: Plasma locks up after splash screen
https://bugs.freedesktop.org/show_bug.cgi?id=109558
Bug ID: 109558
Summary: Plasma locks up after splash screen
Product: Mesa
Version: 18.3
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau at
2008 Sep 11
2
alpm(4) I/O range is claimed by ACPI
Hi,
How can I load the alpm(4) module for SMBus support on my ASUS Vintage
AH-1 system?
It appears the I/O range it uses is claimed by the acpi(4) driver. Can I
override the mapping in some way i.e. tell ACPI not to claim the range?
I don't see anything obvious about this in the acpi(4) man page.
thanks,
BMS
2017 Dec 30
0
Updated Dovecot 2.3.0 now getting 2 strange log errors
On 2017-12-29 18:35, tony wrote:
> I did some more digging around and found this is reproducible on
> multiple hosts running the same version of Dovecot/Pigeonhole/Postfix.
> The problem resurfaces on any host to an account with enabled
> Vacation/OOO response. The Vacation/OOO reply filter was created in
> Roundcubemail, but has been fine for years. One thing to note is in
>
2017 Jun 01
3
v2.2.30 released
At least doveconf -n output would help. I guess related to authentication settings. Are there any errors in logs?
> On 1 Jun 2017, at 12.14, Odhiambo Washington <odhiambo at gmail.com> wrote:
>
>> On 30 May 2017 at 21:16, Timo Sirainen <tss at iki.fi> wrote:
>>
>> https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz
>>
2018 Jan 02
2
Updated Dovecot 2.3.0 now getting 2 strange log errors
Op 12/30/2017 om 6:47 AM schreef tony:
> On 2017-12-29 18:35, tony wrote:
>> I did some more digging around and found this is reproducible on
>> multiple hosts running the same version of Dovecot/Pigeonhole/Postfix.
>> The problem resurfaces on any host to an account with enabled
>> Vacation/OOO response. The Vacation/OOO reply filter was created in
>>
2017 Aug 16
1
dotlock causing crashes
OS: CentOS 7 x86_64
Dovecot version: 2.2.31 (65cde28) (GhettoForge RPM)
Filesystem: GlusterFS, but working on changing that. Only one server is receiving activity.
Was getting messages about corrupt dovecot.map.index files. Changed to dotlock from fcntl to try to fix that.
Reading symbols from /usr/libexec/dovecot/imap...(no debugging symbols found)...done.
[New LWP 74012]
Core was generated by
2017 Aug 03
1
rawlog
> On August 3, 2017 at 8:57 PM Alexander Dalloz <ad+lists at uni-x.org> wrote:
>
>
> Am 03.08.2017 um 01:04 schrieb Matt Bryant:
> > Hi,
> >
> > Trying to get rawlog working on dovecot 2.2.31 configured as per
> >
> > https://wiki2.dovecot.org/Debugging/Rawlog
> >
> > but
> >
> > a) it doesnt appear to be loggin anything
2008 May 07
15
Wine failure logs
I'm experimenting with Wine under Kubuntu Hardy Heron, on a former Vista laptop (boy, does it run noticeably faster on Linux). The deal is that my son wants to move to Linux on his desktop, but still have access to particular games that he plays. The laptop is the testbed. Before trying to install any of the games, I tried out three applications that I find useful, Orbitron, Country Codes and
2018 Apr 12
2
ACL for system users?
Hello all,
I'm setting up an IMAP server with dovecot. I've set up system users
with PAM authentication and Maildir maiboxes.
I'd like to share mailboxes among them, but regardless of what I try, I
bump into filesystem permissions.
I want to have Maildirs created for new users with the right
permissions. I even changed "UMASK" in file /etc/login.defs from 022 to
002,
2017 Jul 13
5
passwd-file, getting invalid uid 0
Per my earlier post about system and virtual users, I have everything working, but I'm seeing the
following message, and wondering:
1) does it matter?
2) is there a way to suppress it?
I have an Exim /etc/aliases entry that sends root to me.
Jul 13 14:38:47 thebighonker dovecot: auth-worker(13055): Error: passwd-file /etc/passwd: User root has invalid UID '0'
doveconf -n:
# 2.2.31
2009 Feb 13
2
extracting parts of words or extraxting letter to use in ifelse-func.
Hello
I want to make some variables with the ifelse-function, but i don't know how
to do it.
I want to make these five variables;
b2$PRRSvac <- ifelse(b2$status=='A' | b2$status=='Aa',1,0)
b2$PRRSdk <- ifelse(b2$status=='B' | b2$status=='Bb',1,0)
b2$sanVac <- ifelse(b2$status=='C' | b2$status=='sanAa',1,0)
b2$sanDk <-
2019 Nov 08
1
gssapi without passdb
Good afternoon.
I'm configuring dovecot to authenticate users against a samba server
running as an active directory domain controller. I followed the
instructions as stated in the page
https://wiki.dovecot.org/Authentication/Kerberos and considering the
sentence that states [...]The Kerberos authentication mechanism doesn't
require having a passdb, but you do need a userdb[...] I
2017 Jul 21
4
Corrupt index files
I am running Dovecot IMAP on Linux, on a LizardFS storage cluster with
Maildir storage. This has worked well for most of the accounts for
several months.
However in the last couple of weeks we are seeing increasing errors
regarding corrupted index files. Some of the accounts affected are
unable to retrieve messages due to timeouts.
It appeared the problems were due to the accounts being accessed
2017 Jan 09
1
panic when doveadm sieve put between multiple hosts
Dovecot version: 2.2.25 (7be1766)
I?m looking into an issue we?re having with a new setup. We have one fronted host with two backend hosts, and we?re attempting to use doveadm to allow us to administer sieve on the frontend and have it replicated to the backend hosts.
When I attempt to use doveadm sieve put on the frontend host, i get the following on the frontend host:
frontend-machine $ cat
2017 Jun 09
2
Dovecot stops with "Fatal: kevent(): Invalid argument"
On 05/21/2011 17:54, Timo Sirainen wrote:
> On 21.5.2011, at 2.51, Henrik Larsson wrote:
>
>>
>>>> That patch doesn't fix anything. It only changes the error message to be more informative so I could figure out what is causing it. If you haven't seen any more errors, it's just a coincidence.
>>>
>>> I have for some reason not seen the error