On Tue, 13 Feb 2007, Sebastian Hagedorn wrote:
that's true if you use UW-imapd.
(http://www.faisal.com/docs/mbx.html)
This breaks any familiarity I would have with things like using procmail
to deliver to ten different folders (since after all, what would be the
difference, they're *all* inbound folders that will be delivered to).
But the URL you quote gives you an example about how to do that:
"Delivering Mail
If you do not use mail filters, you don't need to worry about this section.
If you use a mail filter, you have the problem that the mail agent will
attempt to deliver the mail by appending it to the end of the target folder.
This will not work with mbx. Instead you will need to use the dmail command,
as with the following .procmailrc example:
:0
* [EMAIL PROTECTED]
|/usr/bin/dmail +mail/foo
I've said it before, but I'll say it again: it would be really REALLY nice
if there was some global way to tell procmail "when I specify a folder,
just use dmail for it", so all old recipes just kinda work (as I've got
tools, such as those integrated into squirrelmail) that generate
procmailrc lines in a certain format (or better still, some c-client like
autodetection of all mailbox formats)...just as I'm able to tie sendmail
to procmail for superior filtering and sorting, it would be cool to marry
procmail to dmail for superior DELIVERY.
The dmail command understands normal unix mailboxes as well as mbx files, so
it's probably wise to migrate all your procmail recipies to using dmail
before converting to mbx format files."
I've been a pine whore for years, but it's been my understanding that
pine should also work that way in theory -- but for me it's not. When I
move things out of my .mail folder, they're "off the radar".
That depends on the way you compiled and set up pine. If you compile it from
pristine source it *will* behave that way.
It's built from BSD ports, but my pine.conf is special:
inbox-path=~/.mail
I'm told there's also a way to set the $MAIL environment variable to do
the same, but it never worked for me with PINE.
At any rate, pine opens ~/.mail as INBOX but doesn't move stuff out of it
to anywhere else -- if there's some special file I need to create to do
that, let me know (at this point it's a c-client and pine issue far more
than imap, at least on that issue).
Given, this is my personal flow of work, but since pine only showed
one folder at a time, I wanted to be able to work within a reasonable
timeframe (say, three months) all without having to wait for pine to
chunka-chunka-chunka another folder open.
I think that's a technical term, by the way.
If it's that slow, something isn't right. With mbx or mix it would be much
faster.
%ls -al mail|grep aved
-rw------- 1 danm danm 3589911 May 12 2005 saved-messages-2000
-rw------- 1 danm danm 63359907 Jul 2 2004 saved-messages-2001
-rw------- 1 danm danm 114176590 Oct 7 2005 saved-messages-2002
-rw------- 1 danm danm 470261563 Dec 16 2005 saved-messages-2003
-rw------- 1 danm danm 639041917 Jun 6 2006 saved-messages-2004
-rw------- 1 danm danm 638784909 Aug 3 2005 saved-messages-2004-OLD
-rw------- 1 danm danm 847728694 Jul 20 2006 saved-messages-2005
-rw------- 1 danm danm 120838290 Feb 5 23:39 saved-messages-2006
Once I started getting a decent amount of mail, it got kinda
unwieldly...it's not uncommon for me to have to wander off to do something
else while searching, resorting, or whatnot on these behemoths. Opening
some of them is known to take a few minutes.
So, based on the above, is what I've been doing all these years "Wrong"
by the usual standards?
Is there a best-practices concept?
The URL you quote has most of them.
Just making sure, I don't want to take an off-the-beaten path site as
"canon" without some kind of approval :)
-Dan
--
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Site: http://www.gushi.org
---------------------------
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
