similar to: Fail2ban and logging

Saw the following in the log after shutting down my client. Feb 22 20:44:47 sbh16 dovecot: imap(mark): Disconnected: Logged out bytes=1755/9765 Feb 22 20:44:47 sbh16 dovecot: imap(mark): Panic: file istream-raw-mbox.c: line503 (istream_raw_mbox_get_start_offset): assertion failed: (rstream->seeked) Feb 22 20:44:47 sbh16 dovecot: imap(mark): Raw backtrace:

I have been running Dovecot 1.2.5 since Sept 14. Beginning at about 03:28 on Sept 21 for no apparent (to me) reason and continuing through the present, I am seeing log messages like the following and am experiencing delays logging in. Sep 22 19:07:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal:

I have just upgraded from 1.2.beta1 to 1.2.beta2. My configuration is: [root at sbh16 ~]# dovecot -n # 1.2.beta2: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/postfix/sbh16-cert.pem ssl_key_file: /etc/postfix/sbh16-key.pem login_dir: /usr/local/var/run/dovecot/login login_executable(default):

I have been running dovecot 1.2.10 without problems. I am trying to install 2.0.beta3. I have I think translated all my configuration customizations correctly, but I have problems. I can start dovecot, but I can't login, at least not with SSL. Here's my dovecot -n # 2.0.beta3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms

I am testing the version on FreeBSD 7.3-PRELEASE (I doubt it's the issue) and I am having a problem with pop3. Here is what I see in the log when I attempt to connect to port 110: Feb 22 18:15:03 master: Warning: SIGHUP received - reloading configuration Feb 22 18:15:08 pop3-login: Panic: file login-settings.c: line 216 (login_settings_read): assertion failed: (input.roots[count] == NULL) Feb

Here's my configuration. dovecot -n # 1.0.7: /usr/local/etc/dovecot.conf protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock The above setting was just added in an attempt to resolve the issue.

Since upgrading from Dovecot 2.0.beta4 + patches http://hg.dovecot.org/dovecot-2.0/rev/96496e1d3d12 and http://hg.dovecot.org/dovecot-2.0/rev/aefa279e2c70 to Dovecot 2.0.beta 5, I have started to see the subject error from Dovecot for SASL authentications. It doesn't happen every time, but it happens more often than not. It doesn't seem to affect Postfix's acceptance of the message.

Hi List, optimizing the configuration on one of our servers (which was hit by a brute force attack on dovecot) showed an odd behavior. Dovecot Version 1.0.7 (CentOS 5.2) The short story: On one of our servers an attacker did a brute force attack on dovecot (pop3). Since the attacker closed and reopened the connection after every user/password combination the logs showed many lines like

I just tried installing dovecot 1.1.8 as an upgrade to 1.1.7 and encountered Panics like the following with pop3 accesses Jan 8 10:55:31 sbh16 dovecot: Killed with signal 15 Jan 8 10:55:49 sbh16 dovecot: Dovecot v1.1.8 starting up Jan 8 10:57:01 sbh16 dovecot: pop3-login: Login: user=<user2>, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Jan 8 10:57:01 sbh16 dovecot: Panic:

I have just upgraded to dovecot 1.0.13. All the documentation I can find in the example .conf file and the NEWS and ChangeLog files seems to say that the mail_privileged_group = mail setting is all I should need to make dovecot use group mail to create dotlock files. My understanding from what I read is that mail_privileged_group is used to set the group used while creating dotlock files in (in

I have recently upgraded from Dovecot 1.2.10 to 2.0.beta3. I have Postfix 2.3.3 and use Dovecot to provide SASL auth for Postfix. # dovecot -n # 2.0.beta3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms = plain apop login auth_worker_max_count = 5 mail_location = mbox:~/Mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail

On Mon, Apr 27, 2020 at 10:13:37 +0200, Paul van der Vlis wrote: > Op 27-04-2020 om 09:02 schreef Peter Krempa: > > On Sat, Apr 25, 2020 at 16:40:35 +0200, Paul van der Vlis wrote: > >> Op 25-04-2020 om 16:00 schreef Paul van der Vlis: > >>> Hello, > >>> > >>> I have a qcow2 disk what needs to become increased. > >>> >

Hello, I would like to expunge all mail of a mailbox from a script. What's a good tool to do that? With regards, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl/

Hello, I use libvirt on machines without shared storage. My VM's have all one qcow2-disk, with the same name as the VM. When I want to migrate a VM, I check if there is an qcow2 image on the other host with that name. When that's not the case, I copy the image using rsync first. If the image excist, I don't do that, and I think that "--copy-storage-inc" will do it. But I

On Sun, Feb 10, 2019 at 12:11:42 +0100, Paul van der Vlis wrote: > Hello, > > I use libvirt on machines without shared storage. My VM's have all one > qcow2-disk, with the same name as the VM. > > When I want to migrate a VM, I check if there is an qcow2 image on the > other host with that name. When that's not the case, I copy the image > using rsync first. If

On Sat, Apr 25, 2020 at 16:40:35 +0200, Paul van der Vlis wrote: > Op 25-04-2020 om 16:00 schreef Paul van der Vlis: > > Hello, > > > > I have a qcow2 disk what needs to become increased. > > > > I don't have space on the location where it is now to have it two time, > > so I want to live-migrate it to another host. > > > > On the other

Op 27-04-2020 om 10:41 schreef Peter Krempa: > On Mon, Apr 27, 2020 at 10:13:37 +0200, Paul van der Vlis wrote: >> A point is that I have to create disk(s) on the other side with >> qemu-img, I did not found a way to do that automatically. My question > > We are able to pre-create the storage given that a full copy is > requested (copy-storage-all, not copy-storage-inc)

Hello, I cannot call my server over the internet with SIP anymore. Even when I do a maximum logging on my firewall, I don't see packets coming from outside. I've tried it from an ekiga.net account and an sip2sip.info account. What could be wrong? I would expect incoming traffic on port 5060 UDP... The account is "paul at vandervlis.nl". This should connect trought DNS to the

Hello, I see a Xen hypervisor package for AMD64 in Lenny and unstable, but no xen-kernel for AMD64. Is there a linux-image-2.6-xen-amd64 package planned for Lenny? With regards, Paul van der Vlis. -- http://www.vandervlis.nl/

Hello, I saw the Linux 2.6.18 kernel was removed from Lenny. So there is no dom0 in Lenny anymore. Maybe it would be an idea to leave the 2.6.18 kernel in Lenny to use them as dom0. Only the i386 and amd64 ofcause. Then it would also be possible to add the latest code from xen.org to it. I saw Linux 2.6.27 already has a 64-bit Xen dom0. So the code is ready... Maybe not well enough tested. I