[34221] in North American Network Operators' Group
Re: Scalable Mail solution with NAS
daemon@ATHENA.MIT.EDU (Eric Sobocinski)
Wed Jan 31 13:43:10 2001
Message-Id: <4.3.2.7.2.20010131133135.00bed2d0@lint.cisco.com>
Date: Wed, 31 Jan 2001 13:40:38 -0500
To: Sebastien Berube <sberube@zeroknowledge.com>
From: Eric Sobocinski <sobo@cisco.com>
Cc: nanog@merit.edu
In-Reply-To: <Pine.LNX.4.21.0101311057250.26915-100000@localhost.localdo
main>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Errors-To: owner-nanog-outgoing@merit.edu
At 11:06 AM -0500, 01/31/2001, Sebastien Berube wrote:
>One way to fix this
>issue would be to use a hashing scheme to split the amount of actual
>mailboxes into a subdirectory structure. You could get something like
>
>johndoe@yourdomain.com would have his mailbox in
>
>/export/mailboxes/j/o/h/n/johndoe.mbox
>
>so in /export/mailboxes, in order to find the j directory, you only have
>about 36 directories entries or so.
>
>Although this example is not good in the case where you accept usernames
>with 3 or less characters.
It's not hard to right-pad any short usernames before hashing. For
instance, the username "bo" might hash as "bo__" and thus would end up in
the directory "/export/mailboxes/b/o/_/_/bo.mbox". If you allow
non-alphanumerics you'll want to translate those to something innocuous as
well, or a name such as "bo.lee" will cause problems.
