Re: Limitations on folder names?

--===============43719835868622559==
content-type: multipart/signed; boundary="=-Mo+305lH4EB0HoxUohbS";
	protocol="application/pgp-signature"; micalg="pgp-sha1"


--=-Mo+305lH4EB0HoxUohbS
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

You could look at it that way ;-)

I'm an email pack rat; there's no way I could cope with e.g. my personal
correspondance in a single mbox called 'friends'.

So in ~/mail I have top level mboxes.  Under ~/mail I created
subdirectories, e.g. friends, and in these sub-directories are mboxes
for a specific category, e.g. 'John Doe'.  I've used this with netscape,
mozilla, pine, evolution, and the CMU (?- from the creators of Pine)
imap server.  I also like 'natural & descriptive' file names- i.e.
sometimes include spaces.  I've found that it's best not to have spaces
for subdirectory names; at least a few of the above programs fail on
that.  But it appears to be ok to have spaces in mbox names.

So all I plan to do is alter Jack Bertram's scripts to recurse my tree
of directories under ~/mail, rather than just the mbox files in ~/mail.=20
I'll create a mapping to remove spaces; it sounds like non-white space
chars should be ok as far as ifile is concerned.

I'll also have to create a couple of glue scripts/rules for the procmail
rules to map between munged names and real names of folders.

NB- this is a back burner project... don't expect to hear from me about
this to soon :-)

Regards

Julian

On Fri, 2003-06-06 at 14:38, clemens fischer wrote:
> Julian Rendell <[email protected]>:
>=20
> > I'm basically going to extend Jack Bertram's scripts to cope with
> > multi-level (i.e. has sub-directory) mail archives.  If they work,
> > I'll let the list know.
>=20
> good idea!  so you will feed subsets of message to ifile, test more
> specifically and run ifile on subsets of the more general subsets?
>=20
>   clemens

--=-Mo+305lH4EB0HoxUohbS
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA+4RRQ+12v+m8QYXURArjrAJ9nTwupb4mbZplwesG9pEPpcUgWmQCfeqMZ
9cnMk9VQS1tdeDZKSwG9Jpw=
=qrhh
-----END PGP SIGNATURE-----

--=-Mo+305lH4EB0HoxUohbS--




--===============43719835868622559==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

_______________________________________________
Ifile-discuss mailing list
[email protected]
http://mail.nongnu.org/mailman/listinfo/ifile-discuss

--===============43719835868622559==--