search for: netregistri

Hi List, I am using the Dovecot 2.1.12 with NTLM authentication enabled. The Dovecot is set up in cluster with directors, 60 000 connections simultaneously. I have noticed that NTLM authentication is processed differently for Thunderbird and Outlook 2010 users. It actually makes Outlook 2010 clients query LDAP more often that Thunderbird ones which is not good potentially for overall performance.

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

Hi All, Has anyone had a similar problem with ext3? A 75 gig partition in 24x7 use for about 2 weeks - no problems. Today I ran bonnie++ on the partition to get a feel for the performance, with ext3 and quotas enabled. The box started swapping like crazy on and abruptly froze at at the 'Delete files in random order' step. There was no kernel error messages or the like. This partition

Hello, Please somebody suggest me how to remove the "*masteruser" appendix from the dovecot director database while using masteruser authentication. My situation is: - all users get authenticated in LDAP on the dovecot-director frontend - then they are forwarded to dovecot backend as username*masteruser ( this is a way how to proxy users with encrypted passwords). To enable it a added

Hi All, I have compared Dovecot performance to Courier and it appears that as a POP3 server Dovecot is slower in 2 times but as an IMAP server it is faster in 1.5 times. The same node (16CPUs), testing time is 30 min, please see results and dovecot configs attached. Benchmark software is MStone used by Sendmail Inc so is is quite reliable. I do not see anything else to tweak in Dovecot to

Hi, Dovecot 2.1.12 sends panic message when it tries to authenticate some users. Apparently because they use different authentication mechanisms on different email clients at the same time. For example, in debug logs this user uses CRAM-MD5, NTLM and PLAIN in account settings of his email clients. All passwords are stored in plain text (base64) in LDAP. Please advise me what I can tweak to fix

Hello guys, Would you be able to help me with this little issue. I bet someone has the same config so if you can copy-paste it I will very appreciate it. So main idea is to enable Dovecot director to authenticate a LDAP user with plain or encrypted password and send the user to back-end Dovecot server after the authentication. According to Wiki it is only possible if we use the master user to

Hi Guys, I am planning on upgrading an existing NFS exported filesystem to the ext3 htree patch on kernel v2.4.23. Will the patch index directories automatically after tune2fs -O dir_index or should I do an e2fsck -Dfy on the filesystem before remounting?

Hi All, Is http://thunk.org/tytso/linux/ext3-dxdir/patch-ext3-dxdir-2.4.21rc5 the latest htree patch for 2.4 or should I be using bitkeeper to extract the patch?

Can it be safely resized on the fly via tune2fs or am I asking for trouble? Using kernel v2.4.21 and ext2progs v1.32

Hi Guys, I have experienced a recent performance issue with an ext2 filesystem. Essentially I have had several files that get overwritten on average once per day. This has been happening for about a hear when the program accessing and reading those files started from several milliseconds to 15-20 seconds to open and read the file. Moving the directory to a new name and copying the contents

Hi Guys, I am quite keen to try out the new htree extensions to ext3 however I wish to use them under NFS. I have noticed comments from the developers saying that it doesn't work properly under NFS. What exactly is the current status of the issue?

Hi guys, Is there any way to mount an ext3 fs that is on ro media? I get an error: EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access unavailable, cannot proceed. Specifically this is with an LVM snapshot.

Hi Guys, When I try to create an ext3 journal on a new fs, I receive the following error. This is all under Kernel v2.4.17 and e2fs tools v1.25: File size limit exceeded Running e2fsck on it afterwords gives: e2fsck -y /dev/sdc1 e2fsck 1.25 (20-Sep-2001) Superblock has a bad ext3 journal (inode 8). Clear? yes *** ext3 journal has been deleted - filesystem is now ext2 only *** Superblock

Hi All, I am about to implement ext3 on a large nfs shared partition that is using quotas (around 2-3000 users) with kernel v2.2.19. Are there caveats that I should be aware of? Every time someone submits a bug report Stephen's first question is always 'Are you using Quotas?' :) TIA

Dear All, I have noticed that dovecot.index is not generated straight away if you have just a few emails in the mailbox. Instead of that dovecot.index.log is modified and accessed by clients. Only if the number of email reaches some level then it creates dovecot.index in user mailboxes. Can somebody please tell me when (in my understanding of the process) the index log file drops all data into

Hi Guys, I am running ext3 on kernel v2.6.5. I have an ext3 filesystem with dir_index and data=journal for /var/spool/exim Today I noticed in the exim logs a bunch of 'failed to unlink /var/spool/exim/input/P/1BRbSP-0006hy-Jp-D' I also noticed these in the kernel logs: EXT3-fs warning (device hda12): ext3_unlink: Deleting nonexistent file (612870), 0 EXT3-fs warning (device hda12):

Guys, I have recently applied the latest 2.4 htree patch on a heavily loaded nfs server. The nfs server serves around four very busy clients that deliver email in maildir format and pop3/imap clients. Being maildir I presumed that the htree patch would improve performance - but I was wrong. Load on the server went up by around 25-40%. After 3-4 hours of heavy use the clients load went up to

hi all, I've been tasked to add sieve/managesieve to an existing dovecot cluster running 2.1.7 on debian wheezy which is made up of 2 dovecot-proxy hosts as directors and some back end dovecot imap hosts all running the same version. My problem is that I thought to put the service on the director/proxy hosts since they wouldn't have too much load on it, but when I do I get the

Hello All, Have anyone met the problem I am struggling with at the moment ? The problem is when I run two instances of dovecot 2.1.8 which are one for proxy-director and another one is a regular one on the same server then I have big amount of strange entries in the /var/log/mail.err: Jul 26 11:51:20 dovecot-test-1 dovecot: director: Error: Empty server list Jul 26 11:51:20 dovecot-test-1