similar to: Migration from v1 to v2 with hashed directory structure

Hi, I am trying to use separate configurations for ldap authentication thus providing users with the ability to only use username without domain part. Now according to documentation this should be possible http://wiki2.dovecot.org/AuthDatabase/PasswdFile but I keep getting error in my dovecot.log like this auth: Error: Can't open configuration file /etc/dovecot/%l/dovecot-ldap.conf: No such

In squid we use a double layer of hashed directories on the FS to allow storage of millions of files. I was reading the "Directory hashing" section but never understood it.. since it's written.. in a way I could not understand. I am using this line: mail_location = maildir:/home/vmail/%d/%n/Maildir/ and I want to migrate to a hash based directory scheme. While trying to understand

Hello, I have a small ISP and we have a dovecot for virtual mail hosting with a postfix and openldap as backend. Now the problem is that there is one primary domain (example.com) and many other virtual domains with different users. When user from primary domain logs in, he is using username as his username (without domain part) and when user from virtual domain logs in, he uses username at

> I would love to know why your ubuntu 14.04 system doesn't support sha512-crypt. I just tried SHA512-CRYPT and it is supported on Ubuntu 14.04. I think I was thinking about DBMail instead of Dovecot. I could really use support for BLF-CRYPT since my current password hashes generated by PHP are using Blowfish encryption. Maybe, Dovecot could just add support for BLF-CRYPT by using the

>> Maybe, Dovecot could just add support for BLF-CRYPT by using the open source implementation of Blowfish hashing found in https://github.com/php/php-src/tree/master/ext/standard <https://github.com/php/php-src/tree/master/ext/standard>. The implementation looks like a single function to generate the hash. I?m not much of a programmer, but it would seem to me that these .c/.h files

(I subscribed to a daily digest for this list and can?t figure out how to reply to a reply.) Anyway, Aki Tuomi replied to my feature request saying: > We support in latest 2.2 release > > MD5 MD5-CRYPT SHA SHA1 SHA256 SHA512 SMD5 SSHA SSHA256 SSHA512 PLAIN > CLEAR CLEARTEXT PLAIN-TRUNC CRAM-MD5 SCRAM-SHA-1 HMAC-MD5 DIGEST-MD5 > PLAIN-MD4 PLAIN-MD5 LDAP-MD5 LANMAN NTLM OTP SKEY

Hi all, in my settup i decided to set mail_home in 10-mail.conf, and let dovecot do the hashing to a 2-level directory structure. mail_location = mdbox:~/mdbox:ALT=/altstorage/%h/mdbox mail_home = /vmail/%1Mu/%2.1Mu/%u In my userdb ist homedirectory not set and everythink works as expected, except when i use rawlog i get only logs in ~/dovecot.rawlog if home is set in userdb. In wiki

On 3/9/2016 9:02 PM, Timo Sirainen <tss at iki.fi> wrote: > On 08 Mar 2016, at 01:50, Pavel Stano <stanojr at websupport.sk> wrote: >> >> sis attachment deduplication is broken in 2.2.16 upwards. >> It is caused by this commit. >> https://github.com/dovecot/core/commit/664bf3e236c214aee86294483c379e4fa66c2e63 >> >> in src/lib-fs/fs-sis.c function

I'm trying to understand the method dispatch in objc_MsgSend. At some point during compilation, ascii selectors are hashed into integer SEL's. Is this hash somehow guaranteed to be unique? If so, how? If not, how are collisions handled? Is this hashing done during the link phase? Any insights/pointers to the code/documentation related to this hashing would be greatly appreciated.

The MKsetup() in unique.c throws an error if the vector to be hashed is longer than (2^32)/8: if(n < 0 || n > 536870912) /* protect against overflow to -ve */ error(_("length %d is too large for hashing"), n); I occasionally work with vectors longer than this on 64-bit builds. Would it be too much to ask that R can take advantage of all 64 bits for hashing when

Hello, I'm doing some analysis on a rather large data set. In this case, some simple commands are failing. For example, this one: > x$eventtype <- factor(x$eventtype) Error in unique.default(x) : length 1093574297 is too large for hashing ...I think this is a bug, because "hashing" should not be required for the "factor" function. Am I right? The whole column

Here's my latest version of Hashing.h, which I propose to add to llvm/ADT. Comments welcome and encouraged. On Thu, Feb 9, 2012 at 11:23 AM, Talin <viridia at gmail.com> wrote: > By the way, the reason I'm bringing this up is that a number of folks are > currently working on optimizing the use of hash tables within LLVM's code > base, and unless we can come up with a

Is it possible to somehow send an email containing the user password if it is stored as a md5 hash in the database? Is it stupid to save the passwords as clear text strings in the db? Its a web shop. A workaround would be to generate a new password and send it to the user. If the user then want to, he may change to another password. Any other thoughts on this? //D -- Posted via

Hello! ? As posted on May 27th this year, dovecot 2.1.7 does not allow for the mailstore to be located in a virtio partition. I still receive fstat()-errors on the lock files in this combination: ? May 27 12:54:51 host dovecot: imap(test at mydomain): Error: fstat(/var/vmail/mydomain/test/.quotausage.lock) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test at mydomain):

Hi, I'm trying to write a general-purpose "lexicon" class and associated methods for storing and accessing information about large numbers of specific words (e.g., their frequencies in different genres). Crucial to making such a class practically useful is to get hashing working correctly so that information about specific words can be accessed quickly. But I've never really

Hi I need to store about 250.000.000 files. Files are less than 4k. On a ext4 (fedora 14) the system crawl at 10.000.000 in the same directory. I tried to create hash directories, two level of 4096 dir = 16.000.000 but I had to stop the script to create these dir after hours and "rm -rf" would have taken days ! mkfs was my friend I tried two levels, first of 4096 dir, second of 64

> Changing your php app will probably be the easiest solution. Since I?m using Docker, the easiest solution for me is to find a linux distro that can run Dovecot well and supports BLF-CRYPT as well. What Linux distros support BLF-CRYPT and are well tested and secure? > On Jun 5, 2016, at 8:54 PM, Edgar Pettijohn <edgar at pettijohn-web.com> wrote: > > On 16-06-05 20:36:35, KT

LLVM currently has a bunch of different hashing algorithms scattered throughout the code base. There's also a number of places in the code where a FoldingSetNodeID is created for the purpose of calculating a hash, and then discarded. From an efficiency standpoint, this isn't all that bad unless the number of individual items being hashed > 32, at which point the SmallVector overflows

By the way, the reason I'm bringing this up is that a number of folks are currently working on optimizing the use of hash tables within LLVM's code base, and unless we can come up with a common hashing facility, there will be an increasing proliferation of cut & paste copies of hash functions. So feedback would be nice. On Tue, Feb 7, 2012 at 10:58 PM, Talin <viridia at

On 13 February 2012 00:59, Talin <viridia at gmail.com> wrote: > Here's my latest version of Hashing.h, which I propose to add to llvm/ADT. > Comments welcome and encouraged. > /// Adapted from MurmurHash2 by Austin Appleby Just out of curiosity, why not MurmurHash3 ? This page seems to suggest that #2 has some flaw, and #3 is better all round: