similar to: Trouble mounting a second drive

Just two changes: - Beta4's SSL proxying rewrite worked worse than I thought. Reverted it back to original code. - Filesystem quota plugin now looks up the mount path correctly. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part Url :

Just two changes: - Beta4's SSL proxying rewrite worked worse than I thought. Reverted it back to original code. - Filesystem quota plugin now looks up the mount path correctly. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part Url :

Hi Ignacio, I'm running Centos 4.2 on some machines and just wonder which is the correct procedure to build one of your packages i've fonund in the fedora.ivazquez.net for FC4 but for CentOs for kernel-modules: http://fedora.ivazquez.net/yum/4/i386/SRPMS.ivazquez/kernel-module-qc-usb-0.6.3-0.iva.1.src.rpm

Sorry, the authentication problem still wasn't actually fixed in beta6. Now, this time I tested every possible authentication case that it really works. I'll soon create a CVS branch which is going to stabilize into the 1.0 release. I won't add new features there so it shouldn't really get broken anymore, at least because of new features.. So, two changes in this release:

Sorry, the authentication problem still wasn't actually fixed in beta6. Now, this time I tested every possible authentication case that it really works. I'll soon create a CVS branch which is going to stabilize into the 1.0 release. I won't add new features there so it shouldn't really get broken anymore, at least because of new features.. So, two changes in this release:

Fixes, mostly: * The login and master usernames were reversed when using master_user_separator (now the order is UW-IMAP compatible). * Killing dovecot master process now kills all IMAP and POP3 processes also. + -a parameter to dovecot prints now all settings that Dovecot uses. -n prints all settings that are different from defaults. + Added pop3_lock_session setting + %M modifier

Fixes, mostly: * The login and master usernames were reversed when using master_user_separator (now the order is UW-IMAP compatible). * Killing dovecot master process now kills all IMAP and POP3 processes also. + -a parameter to dovecot prints now all settings that Dovecot uses. -n prints all settings that are different from defaults. + Added pop3_lock_session setting + %M modifier

I haven't had yet time to read all the mails in this list which I skipped in the last few of weeks. I'll try to get to them eventually. This release contains several new features which haven't been fully tested yet, such as ACLs, master users and Maildir++ quota. If you intend to use them, test them properly first. This is the first Dovecot release where it's supposed to work

I had originally thought that I'd do a complete audit of the Dovecot's sources this weekend, but looks like I didn't. Hopefully I've been writing good enough code that the "1000 EUR for security hole" offer lasts for a long time. :) This release should fix the SSL parameter regeneration problem. There were two changes that were needed to fix it, but I had forgotten the

Since there have been so many requests, I guess it's time for beta3 now. There are a couple of issues that I'm still concerned about, but those probably happen with beta2 as well. If you're beginning to see more connection hangs/timeouts with this release, please tell me. * Dotlock code changed to timeout faster in some situations when the lock file is old. + Added support for

As promised, here it is finally. v1.0 is getting nearer and I want people to start looking at Dovecot's sources. Getting some more help with development would be nice, but I'd also like to hear if there are any hidden bugs in the code. So, one week from now I'll start offering 1000 EUR for the first person to point out a remotely exploitable security hole in Dovecot. See

Dear friends, I am trying to upgrade dovecot 1.0-alpha3 to dovecot 1.0-beta 5, but I have some problems to do that. When I install its rpm I get a message which indicates I have to install some dependences such as openssl-0.9.7f-7.i386, sqlite-3.2.8-1.9.el4 and libk5crypto.so.3. I haven't had any problems with openssl and sqlite but I always get a message that I need to have the libraries

I just downloaded dovecot 1.0b3 and running "make install" gives me an error This seems like a fairly simple bug in the Makefile ... but I'm not sure if maybe its a symptom of something more complex. I've tried "make uninstall" , "make install" and removing the entire /usr/local/lib/dovecot tree and same thing. dovecot does run ... but for other reasons

Hello, I have a FC4 x64 server that I am configuring/testing. It had dovecot 0.99 loaded after I did a yum update. That worked great with mbox, the passwd file, and test users in /home/users/username. I would like to be able to authenticate virtual users by 'username at domain.com' and have them be able to use squirrelmail or Outlook/Outlook Express to access their email. Users have

I have literally beat my brains out trying to get my XP machine to talk to my samba server on my linux machine. MY PROBLEM: The samba server (version 2.2.7a) is running on Redhat Linux 9.0. I can successfully connect to the XP machine and copy files from the XP machine to my Linux machine. But I cannot access my linux box from my XP machine (The samba server shows up in the browse list on

I have VMPlayer 12 running a CentOS 7 disk. Works fine. However I wish to change the disk from UUID booting (fstab) to the old style LABEL. (so I can export it and use on another machine). fdisk -l /dev/sda Disk /dev/sda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes

Hey all, I know you all saw the topic and let out a groan. However, I understand how to get an overhead paging system to work with respect *, however I am now looking for a small(?) paging amp, that I could hook 3 or 4 horns to. I would like to just have the * extention be routed to a soundcard and out an output, so I would like an amp that is voice signal activated. Has anyone found anything

Hi, I do have an iscsi storage with two raidsets. I'm logged in to the target and get two devices: /dev/sdb and /dev/sdc. After formatting the devices with ext4 I realised, that I had used a wrong label, so I tried to relabel the devices. But now I'm confused: doing a e2label /dev/sdb or /dev/sdc returns always the same label name for both devices. so I did "e2label /dev/sdb

This lays the groundwork for setting Root and RootBackup onto individual partitions for multiple disk installations in the future. Install, removal, upgrade testing has been performed and all seems to work at this point. --- scripts/ovirt-config-boot | 15 ++++++++------- scripts/ovirt-config-storage | 28 +++++++++++++++------------- scripts/ovirt-config-uninstall | 2 ++

I am trying to create a CF card that boots 686 CentOS 6.3 On boot I get a message about /dev/disk/by-label/\x2f where \x2f is "/" cannot be found. Adding rdshell to the boot line and booting up sure enough the /dev/disk directory does not exist. What "creates" that early on in the boot process? My CF card was changed from UUID to LABEL. So I edited grub.conf and make