The idea is that you e-mail yourself a message with a subject starting with “tickle##” where ## is a number from 01 (can be 1 as well) to 31 and procmail will automatically file it AND mark it read in your tickler folders on your IMAP server. You then use my cronjob above to move those into your inbox on the appropriate day.

=====
:0
* ^Subject:[ \t]*\/tickle([0-9]|[0-9][0-9]):.*
{
# Grab the string that brought us here
TICKLE=$MATCH

# If it was a single-digit day, grab it and pad it with a 0
:0
* TICKLE ?? ^tickle\/[0-9]:
* MATCH ?? ()\/[^:]+
{ TICKLEDAY=”0$MATCH” }

# Otherwise grab the two-digit day
:0
* TICKLE ?? ^tickle\/[0-9][0-9]
{ TICKLEDAY=$MATCH }

# Calculate the week using bc
TICKLEWEEK=”`echo \”($TICKLEDAY - 1)/7 + 1\”|bc`”

# Grab the subject that came after the tickle header
:0
* TICKLE ?? ^tickle([0-9]|[0-9][0-9]):\/.*
{ TICKLESUBJECT=$MATCH }

# Make a note in header showing that this rule ran
:0 f
| ${FORMAIL} -A”X-MyProcmailRC: GTD Handler caught TICKLER (White listed)”

# Update the subject to just have “tickler” up front. If you want to refile it later,
# just move the message. Notice that -i is used, so the old subject will be saved to
# Old-Subject: in the header
:0 f
| ${FORMAIL} -i”Subject: tickler:$TICKLESUBJECT”

# Move the message to appropriate tickler folder for this day
:0 wc
“$MAILDIR/.@TICKLER.Week$TICKLEWEEK.$TICKLEDAY/”

# Mark it read
:0 A hi
| mv “$LASTFOLDER” “$LASTFOLDER:2,S”
}
=====

If you cut out a lot of the stuff in the middle that does the tickler stuff, then you can use this as a template for more auto-filing stuff.

For example, I have a rule that routes messages with subjects starting with “todo:” or “defer:” to a DEFER folder of mine and those starting with “action:” to an ACTION folder.

Because my IMAP server is on GMT time, I set my cronjob to run at 5:01AM GMT every night. That corresponds to 12:01AM for eastern standard time and 1:01AM for eastern DST. That’s fine with me.

Also note that I use mailutil to do the message shuffling. mailutil is made by the same people who make pine. There is a non-standard patch that they release for the most recent versions of pine and mailutil that supports the maildir mailbox format (which uses a hashed directory structure). That patch is available at:

http://www.math.washington.edu/~chappa/pine/info/maildir.html

If your server uses a simpler type of mailbox, you might be able to get away with just concatenating one mailbox onto the other. In that case, you won’t need mailutil at all (however, note that mailutil is a very general utility. You can use it to transfer messages from basically any mailbox format to any other mailbox format. It can even connect to remote mailboxes and let you shuffle messages from here to there. It does everything that any IMAP client can do (and more)).