similar to: Urgent - Inconsistent Inboxes

Hello, we use dovecot on a regular basis. Sometimes I end up with a user telling me he does not get mail. When I look after the problem, I always find leading blank lines in the mbox file. We are using postfix with dovecot and amavisd as spam scanner. Amavisd never accesses the mbox files directly so this can be ruled out. I suspected procmail but now it happened also with accounts where no

I am runninng rsync on Ubuntu. It was installed using apt-get install rysnc. I note that the package has not yet been updated to rysnc 3.0. I would like to update using the tar but I am confused how to update the existing installation. On this machine, I am mainly using rsync to send to a cwrsync server (which I have updated already). Can I just overwrite the rsync executable? Any help

I am using SuSE 10.1 and dovecot version 0.99.14-5. dovecot 6267 660 0 14:45 ? 00:00:00 imap-login dovecot 6285 660 0 14:45 ? 00:00:00 pop3-login dovecot 6371 660 0 14:45 ? 00:00:00 imap-login postfix 6454 12811 0 14:46 ? 00:00:00 smtp -t unix -u dovecot 6511 660 0 14:46 ? 00:00:00 pop3-login postfix 6550 12811 0 14:46 ? 00:00:00

Some days ago I wrote about an inaccessible mailbox after an upgrade from 0.99.14 to 1.0rc10. Today I get this problem with another mailbox but it seems to be it is not only related to the upgrade : - user comes back from holiday, does not see his inbox : dovecot: Oct 24 18:51:09 Error: IMAP(abcd): file mbox-sync-rewrite.c: line 405 (mbox_sync_read_and_move): assertion failed: (need_space ==

Hi, Environment: >10000 Users (LDAP) Solaris 10 / sparc imap: dovecot-1.1.10 (pam-unix, no direct LDAP access) pop: dovecot-1.0.14 on another server (pam-unix, no direct LDAP access) mta: postfix (pam-unix, no direct LDAP access) procmail (pam-unix, no direct LDAP access) Filesystems: Inboxes and IMAP-home are on two different SAM-FS volumes. Problem description: Inboxes of users are

I'm runninng samba 3.0.2a on a few machines, ADS security mode, domain member roles. I throw nessus at it, and it can fetch the SID and then list all of the users on the system. I view this as a security problem, is there a way to prevent this?

Am 05.03.2017 um 22:49 schrieb Peter: > On 04/03/17 00:22, Jakob Curdes wrote: >> Hello, we have a centos 6 server running dovecot 2.0 provided with the >> OS, currently 2.0.9. We would like to upgrade to the 2.2.19 package >> provided by the mailserver.guru repo. > > Why upgrade to such an old version? You can get 2.2.27 (2.2.28 in > testing) packages from

Hello, we are trying to monitor ssh logins on security-critical machines with a script that scans logfiles for the relevant entries. A problem ist that when the ssh connection is closed by a network interruption or by closing the window with the ssh client, we do not find a corresponding entry in the logs. "last" does not show this information either, at least on our systems which

> Jakob Curdes via samba<samba at lists.samba.org> wrote: > >> Hello, we have setup a SAMBA4 RODC in our setup where we have two >> exisitng RW Samba4 DC's. >> >> The RODC is joined correctly and can preload user accounts etc. It >> also can resolve its own name and the name of other DC's, also the >> SRV records needed. >> We created

SuSE 9.0 Pro - Kernel 2.4.21 - Samba 2.2.8a and 3.0.1-14 Here's my problem: On a box runninng XP, I have a shared folder which contains 130+ subdirectories. This share is mounted on my linux box from '/etc/smbfstab', but some directories do not show up in directory listings. It's never more than one, and which one varies, but generally seems to be in or near the last half of the

Hi, I stumbled on the dir_index option of recent ext2 implementation which would be interesting for our mailservers (running dovecot with maildir) and found out that the newer ext2progs are able to cope with it; the 2.6 kernels do also but for the 2.4 kernels I still require a patch. Is that correct? Which patch would be the correct one to apply to the current 2.4.27 kernel ? Can anybody

On Wed, 24 Jan 2024 15:54:38 +0100 Jakob Curdes via samba <samba at lists.samba.org> wrote: > Hello, we have setup a SAMBA4 RODC in our setup where we have two > exisitng RW Samba4 DC's. > > The RODC is joined correctly and can preload user accounts etc. It > also can resolve its own name and the name of other DC's, also the > SRV records needed. > We created

Hi Rowland, all, Am 25.04.2024 um 17:24 schrieb Rowland Penny via samba: > On Thu, 25 Apr 2024 16:55:55 +0200 > Jakob Curdes via samba<samba at lists.samba.org> wrote: > >> .. we setup 2 new DCs replacing older DCs and joined them to the >> domain, then decommissioned the old DCs. I now discover that I cannot >> edit the GPO objects anymore. >>

... Version from April 26, gives me the following errors in the imap log file : dovecot: May 04 09:56:58 Error: IMAP(m6933192-4): file mbox-sync.c: line 1262 (mbox_sync_do): assertion failed: (sync_ctx->ibox->mbox_sync_dirty) dovecot: May 04 09:56:58 Error: child 10721 (imap) killed with signal 6 This occurs sporadically and vanishes after some time. Is this something to worry about or

Hello, I just migrated to 2.0.2 and see some <xx at localhost.redirectme.net> (expanded from<xx at localhost>): Command died with signal 6: "/usr/local/libexec/dovecot/dovecot-lda -c /etc/dovecot2.conf". Command output: doveconf: Panic: file settings-parser.c: line 1838 (settings_copy_deflist_unique): assertion failed: (dest_count == ccount) doveconf:

.. we setup 2 new DCs replacing older DCs and joined them to the domain, then decommissioned the old DCs. I now discover that I cannot edit the GPO objects anymore. "sysvolcheck" shows no errors. I read through some documentation but it sounds outdated to me. Any hints where I would start looking? Who should normally be the owner of the sysvol directory itself? What I find strange

We upgraded our imap server hardware and went from dovecot 1.1.3 to 1.2.3 in the process and have been having a critical problem since. I believe I've tracked it down to X-UID reordering that dovecot seemed to do to the mbox format (I know, I know...) inboxes. The problem has manifest itself in several ways with different mail clients but the general problem is that the mail clients have

I upgraded my dovecot installation from something <<1.0 to 0.99.14 today. I wasn't exactly planning to but it just came along for the ride when I upgraded the rest of my system. I was using postgresql for the authentication. Nothing works. the debug logs show that I'm able to make a connection to the database table well enough: auth(default): pgsql: Connected to dbmail

06.04.2023 01:05, Jakob Curdes via samba wrote: > Hello, this morning we had the unpleasant experience of two DCs breaking at the same time, no logins, no DNS resolution, any call to samba binaries > fails with an error message similar to : > > libldbsamba.so.0 : ldb_msg_element_is_inaccessible > (cannot copy&paste as I disabled network access to this server). This is a

Hi all, If you don't care about Debug Info or PDB files you can stop reading now. Just wanted to give a heads up that I'm planning to add a new folder under DebugInfo called Msf. MSF stands for Multi-Stream File and is the container format used by PDB debug info files. However, MSF by itself is generic enough that it need not contain PDB data, and in fact I can think of at least one