Go-Yo is like a yo-yo for email. The goal is to be self-hosted, giving the user full control over the deployment, and avoiding potential privacy or security issues with third-party services.

You will need to create a dedicated email address for bouncing Go-Yo email. For the purposes of this workflow, we will assume that your Go-Yo email address is [email protected]

(Almost) any email address will do, as long as you can receive mail there, and as long as your email provider allows you to create variants of your email address, like [email protected]. (Google/Gmail follows this convention - if you use another mail provider, please verify this).

In an email client such as mutt, simply bounce (or forward) an email to [email protected] in order to have that thread bumped back to the top of your inbox in 3 hours. You can also do things like [email protected], and [email protected].

For the time being, Go-Yo will be very conservative with how it parses this email address. This is a good thing; you don't want Go-Yo to think you want a reminder in six months when you really meant six minutes. If there are any problems with parsing the bounce interval, Go-Yo will send an error message (via email) immediately, so you can deal with it right away. No surprises.

Go-Yo can also be used to schedule messages. The exact workflow for this is TBD.

Go-Yo uses the Maildir format for interoperability. Documentation about the Maildir format is available at http://cr.yp.to/proto/maildir.html

Use a service such as offlineimap to fetch new messages and write them to the Maildir. Once new emails appear in the /new subdirectory, they are ready for processing by Go-Yo.

Go-Yo finds new messages in /new and, after processing them and scheduling the 'bounce' message, moves them to the /cur directory, adding the info string to the filename (see documentation) - and, specifically, setting the message flag to S (seen).

Go-Yo uses the unique portion of the filename to identify which messages to bounce.

After delivery, Go-Yo does not delete (ie, set flag T - trashed) for messages. This allows easy debugging and poor-man's logging.