similar to: Index corruption with squirrelmail.

Hello everyone, I just wanted to see if anyone has experience running Xen on: Dell 2950 III 2 x Quad 2.0 Ghz 1333Mhz FSB 32 GB DDR2 (8x4GB) 2 Disk Perc RAID 1 (7200 RPM SAS) Broadcom Dual Gigabit Ethernet LOM & TOE The requirements of each VM are not that high (and are all identical). I just want to run remote desktop and 1 other application at any given time (either a web based IE

Hi! I'm trying to use an ACL to avoid deletion of messages that are inside .Trash folder, the ACL is already working very well, the problem that I'm facing is that even if the message is not deleted, mail_log logs that it has been deleted. Also, in some cases part of the lazy_expunge code is executed too, but sometimes I just dont know where the message is, thats weird. I erased

Hi! I'm using lazy_expunge to backup that are deleted/expunged, but I would like it to be visible to the user. I tried something like: namespace private { prefix = .EXPUNGED/ separator = / location = maildir:~/Maildir/.Apagadas } namespace private { prefix = .DELETED/ separator = / location = maildir:~/Maildir/.Apagadas } namespace private { prefix = .DELETED/.EXPUNGED/

Hi, Where can I find documentation for plugin writers? Now I see mail-log-plugin source, but I can't understand how entry points (functions mail-log-plugin-init and mail-log-plugin-deinit) are defined to execute some actions on load/unload/copy messages. Can anybody comments this?

Sorry, my previous message entered like a reply, so I'm sending again to keep the list in order. Hi, I'm using dovecot 1.0.5-1 (debian stable) and I'm trying to build a virtual host machine with ldap. In my dovecot-ldap.conf thats what I have: uris = ldap://<ldapserver>/ dn = cn=Manager, dc=domain, dc=com, dc=br dnpass = <ultra secret passwd> sasl_bind = no tls = no

Hello, I'm facing an issue where deleted emails keep re-appearing after my mailbox index gets recreated.??I'm running version 2.2.36 of dovecot, but I tested the same scenario under 2.3.10. I'm also using mdbox, autoexpunge, and using dovecot replication. I've had several instances now where some expunged emails show up again in a mailbox. I noticed this error: doveadm: Error:

But is that not adviced in the manual[1]? I am also in the process of setting up dovecot behind a haproxy. Still testing with this. I was wondering why one would choose haproxy and not eg dovecot proxy (with director) [1] https://wiki2.dovecot.org/HAProxy -----Original Message----- From: Zelic Bojan [mailto:bojan.zelic at kudelskisecurity.com] Sent: woensdag 26 augustus 2020 23:39 To:

http://dovecot.org/test/ Just mbox fixes since 1.0-test16. The logic is simpler and more correct now. Can anyone break it anymore? I actually tested it a while with Evolution and several mailboxes and it didn't break at least immediately. :) Now maybe a few more days and I dare trying this thing myself with my real mboxes (yes, I'm still using them). Dovecot mailing list archives could

An email came to several users but one user didn't receive it and we got 'Mail delivery failed' message. As I see from the log below, there were broken index file. Then dovecot repaired that index and we got the error: Panic: file mail-index-sync-update.c: line 1013 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index->indexid || map->hdr.indexid == 0) It was

Hi list, I have been using xen for a while with success on the following environment: Hardware: Dell PowerEdge 2950 / 2GB Ram / Intel(R) Xeon(R) CPU / 800 GB RAID 5 System: Debian etch Xen packages: # dpkg -l | grep xen libc6-xen linux-image-2.6.18-6-xen-686 linux-modules-2.6.18-6-xen-686 xen-hypervisor-3.0.3-1-i386-pae xen-ioemu-3.0.3-1 xen-linux-system-2.6.18-6-xen-686 xen-tools

http://dovecot.org/releases/dovecot-1.0.rc26.tar.gz http://dovecot.org/releases/dovecot-1.0.rc26.tar.gz.sig Most importantly this should fix mbox problems in recent RCs. * Changed --with-headers to --enable-header-install * If time moves backwards only max. 5 seconds, sleep until we're back in the original present instead of killing ourself. An error is still logged. - IMAP: With

http://dovecot.org/releases/dovecot-1.0.rc26.tar.gz http://dovecot.org/releases/dovecot-1.0.rc26.tar.gz.sig Most importantly this should fix mbox problems in recent RCs. * Changed --with-headers to --enable-header-install * If time moves backwards only max. 5 seconds, sleep until we're back in the original present instead of killing ourself. An error is still logged. - IMAP: With

Two nights ago I took a leap and extended my testing of dovecot 1.1 by replacing 1.0 for the approx 15 users I had on 1.0. At that time I also for the first time tried dovecot 1.1 in a load balanced 2 server configuration with indexes on NFS. I was hoping I did this right, using the mail_nfs params and 1.1 so fchown etc would flush the access cache, but I am getting a number of messages and

Hi there, I would like to enable the desktop user to create shared folders, for example using protocols like Samba, nfs and sftp. For the user to make this possible, the user needs (on a Linux machine configured with the defaults of most current Linux distributions) root privileges. However. In a desktop environment, in my humble opinion the possibility for a normal user to configure a simple

Silvia, I intend to release a binary on the 26th at most. Supporting at least 2 subtitle formats. Yes, I guess it would be nice to have a page and wiki at a place related to other xiph projects but if that is not possible, I have my own provider or even SF I can put things on. Other then that, I promise that on the next commit, a README file will be commited as well. Mesquita

Hi, I am seeing constant "Log synchronization error"s in my logs. See later for an example. This is dovecot 2.2.4, pigeonhole 0.4.1, and postfix 2.10.1 (with mailbox_command = /usr/libexec/dovecot/deliver) on a Fedora 19 system. I am using packages from Atrpms so there are some patches applied - ask for details. The mailboxes have resently been moved from a i386 system. I have

Hi! Is there a way to log the file that have been copied when a person move it from a folder to another using mail_log? Actualy this is what I get in logfile: dovecot: 2007-09-27 15:15:33 Info: IMAP(user at mydomain.com): copy -> Spam: uid=101, msgid=<46FBC6C9.1060301 at somedomain.com>, box=Dovecot What I would like to have is something like: dovecot: 2007-09-27 15:15:33 Info:

As of test-60 and test-61, running Squirrelmail 1.5.1[cvs] on FreeBSD 5.3-STABLE, messages are not marked as read after they are read. If I switch back to test-59, it works normally. When switching back to test-59, with log_path = /var/log/dovelog dovelog shows: dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed

Hi, another imap crash with latest dovecot. segmentation fault in fetch_bodystructure src/imap/imap-fetch.c static int fetch_bodystructure(struct imap_fetch_context *ctx, struct mail *mail, void *context ATTR_UNUSED) { const char *bodystructure; if (mail_get_special(mail, MAIL_FETCH_IMAP_BODYSTRUCTURE,

Hi, I would like to know if it's possible to avoid message deletion in a specific folder. I'm using lazy-expunge like a Trash folder and I don't want the user to enter there and try to erase the message again. Any help is appreciated. Thanks.