similar to: Bug (?) while listing imap folder

Yes I have done it, it is the third command I have run, without any change. a. On 02/04/2015 09:53 ??, Urban Loesch wrote: > Did you "purged" the deleted mails for this user? > On mdbox you must run "doveadm purge -u $USER" to whipe out any as deleted marked mails etc. > > Details: http://wiki2.dovecot.org/Tools/Doveadm/Purge > > I use a nightly cronjob wor

Alexandros Soumplis <soumplis at ekt.gr> schrieb: > If you allow anonymous search on AD maybe you can try to set auth_bind = > no . I'm sorry, but I think, the AD does NOT allow anonymous search... I'm new in this company and I don't know exactly the server, but every try I did without any authentication, failed... Any other idea? Thanks Luca Bertoncello (lucabert at

This is log from dovecot 2.2.10: 2014-01-11T09:55:14+01:00 server/a.b.c.d dovecot: imap(user at domain): Error: Corrupted transaction log file /pracmail/domain/user/mail/.sent-mail/dovecot.index.log seq 16777216: log file shrank (868 < 6144) (sync_offset=6144) 2014-01-11T09:55:14+01:00 server/a.b.c.d dovecot: imap(user at domain): Panic: file buffer.c: line 307 (buffer_set_used_size):

Talking to myself again ;-) Samba-tool is working a little bit different then the silo/policy management on a Windows-DC. On a Windows-DC after assigning the user and host to the silo you have to assign the silo to the user and the host. When assigning the user and host to the silo with samba-tool, the assignment to the user and the host will be done at the same time. So now my policy looks

I haven't seen this before 1.1b16, it happened to two users today while they were searching using fts. Feb 18 16:41:36 hill dovecot: IMAP(username): file buffer.c: line 288 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc) Feb 18 16:41:36 hill dovecot: child 53560 (imap) killed with signal 6 I can probably narrow it down to an example mail if needed. GNU gdb 6.1.1

Thanks Rob for chiming in. Stefan, I do want to be very clear, one of the big challanges that we as developers face building these kind of tools is that we don't run AD domains day-to-day. So we really value good feedback on the ergonomics. If you can test with our work in progress, we are keen to adapt the tooling where possible to be more in line with what is 'naturally expected, so

Hi Stefan, We had a long weekend in New Zealand, I'm catching up now to your emails. Some of the slight differences between Windows tools I've already picked up on and are in my PR Andrew Bartlett mentioned on Friday, but I'm always open to learning what things are missing or different etc. On 23/10/23 02:58, Stefan Kania via samba wrote: > Talking to myself again ;-) > >

Why things happen is one of the great mysteries and joys of being a sysadmin... As for cleaning up SIS, I believe the "doveadm purge" command takes care of it. I have a daily cronjob which includes: #!/bin/sh # Permanently expunge old Trash doveadm expunge -A mailbox Trash savedbefore 2w # Optimize mdbox storage doveadm purge -A # Update fts indexes doveadm fts rescan -A -- Daniel

Daniel thank you for the advice, I have done this exact procedure to clean up some space and I reduced the used space by more than 60% (huge gain!). Yet it is still a mystery why this happened first place and more important if it will occur again, time will tell. I have kept one mailbox out of this procedure (the "live" size is 8,8G, the backup size is less than 1GB) to do some

Shot in the dark here...haven't tried it myself so no promises. There's probably a much better way to do this but sometimes a little "brute force" helps. Theoretical steps: 1. Stop all mail processes - both SMTP and IMAP. 2. Use "doveadm sync" to backup the user mailbox, e.g., doveadm backup -u user mdbox:/tmp/usermail 3. Verify /tmp/usermail looks reasonable

Hi, We have a crash in dovecot 2.2.7 2013-12-11 10:38:44 imap(xxx at example.com): Panic: file buffer.c: line 307 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc) 2013-12-11 10:38:44 imap(xxx at example.com): Error: Raw backtrace: /opt/dovecot- 2.2.7/lib/dovecot/libdovecot.so.0(+0x672a2) [0x7f576b9742a2] -> /opt/dovecot- 2.2.7/lib/dovecot/libdovecot.so.0(+0x67306)

Hello, I am running a Debian Testin/Unstable system with ii samba 3.0.1-2 a LanManager-like file and printer server fo ii samba-common 3.0.1-2 Samba common files used by both the server a And lately (more or less since the first 3.0 Samba i have been getting a _lot_ of segfaults.. Does someone have any clue as to what the below might be caused by? Isnt SIG11 usually

We are working on migrating Dovecot 1.2.17 running on AIX 5.3 (believe it or not!) to Dovecot 2.0.13 running on Ubuntu. We have hundreds of users mboxes we will be migrating. My question is regarding the index files. Should we remove those after the migration, but before we open it up to users so Dovecot can create new ones? I did a test migration of a single user, and Dovecot detects the

My housemate has formalized a sortof new attack against unix-style operating systems. He''s a BSD fan, so that''s where he developed the attack. He asked me to check Linux, which I did. It seems Linux is not vulnerable to it. This attack is going out to BUGTRAQ tonight. The attack isn''t too serious because it requires physical access to the console, but it

Nobody any suggestions ? On 02/04/15 10:09, Alexandros Soumplis wrote: > Yes I have done it, it is the third command I have run, without any > change. > > a. > > > On 02/04/2015 09:53 ??, Urban Loesch wrote: >> Did you "purged" the deleted mails for this user? >> On mdbox you must run "doveadm purge -u $USER" to whipe out any as >>

Linux libc5.4.33''s mk[s]temp() functions require 6 X''s at the end of a filename (the BSD versions I''ve seen are a bit more flexible). This alone is enough to break any claims to real BSD compatability, but wait, there''s more: Only 1 of those 6 X''s are really unique. The rest are simply pid. So you can create exactly 62 temp files using mk[s]temp()

I was playing around again with Windows and when you add members to silos, or remove them, it should not set/unset assigned silo on the user. So I've got a new pull request in Draft state still where I remove that functionality, as well as add some new commands to samba-tool user command. It turned out to be easier to add sub commands to user, as edit user wasn't quite what I thought

Pci_dev_msi_enabled() is used to check whether device MSI/MSIX enabled. Refactor this function to suuport checking only device MSI or MSIX enabled. Signed-off-by: Yijing Wang <wangyijing at huawei.com> --- arch/cris/arch-v32/drivers/pci/bios.c | 2 +- arch/frv/mb93090-mb00/pci-vdk.c | 2 +- arch/ia64/pci/pci.c | 4 ++--

Trying to learn Puppet, given a cfengine background. Am trying to understand the Puppet way of accomplishing the following: I have a lot of servers, that are organized into clusters (we call them silos). Each silo has a specific set of parameters (like IP addresses). I''d like to organize the silo information in some way that each server is associated with that information, and can

Hi everyone, I'm trying to print a table justified to the left, but it doesn't work. Any hints? KennArt <- data.frame(NR=c(171,172,174,175,176,177,181,411,980), TYP=c("K?rnermais", ?"Corn Cob Mix", "Zuckermais", "Mischanbau (Silo)Mais/Sonnenblumen", ?"Mais mit Bejagungsschneise in gutem landwirtschaftlichen und ?kologischen Zustand",