Copy over your procmailrc from CS, but DON'T put it as '~/.procmailrc'.
Name it '~/.proc_cs' or similar so that it doesn't get used automatically.
Then edit at least the following two variables in that file to match the
coglib setup:

    MAILDIR=$HOME/mail
    DEFAULT=$HOME/mail/inbox

This will be the procmailrc file you'll use once everything is moved
over. Then, in '~/.procmailrc' put just the following line:

    DEFAULT=$HOME/mail/forwarded_mail_tmp

This will deliver incoming mail to a temporary folder. Make sure there
are no rules as you don't want to overwrite incoming forwarded mail when
copying folders from CS. At this point you are ready to start
redirecting CS to coglib. Create a '.forward' file in your home
directory on the CS network that contains one line with your coglib
address. (See considerations below.)

You can now scp over your mail folders from CS to coglib. No mail will
be delivered to the CS folders after creating the forward file, so you
won't have to repeat this. Remember that '~/.mail' on CS should become
'~/mail/inbox' on coglib. You may want to save your current inbox and
add it to your CS inbox like so:

    $ cd ~/mail
    $ scp dab.cs.stevens.edu:~/.mail ./inbox.cs
    $ cat inbox >> inbox.cs
    $ mv inbox.cs inbox

Alternatively you can make your CS inbox separate from your coglib
inbox, choosing to put it somewhere like '~/mail/guinness'.

Once all your mailboxes are moved over, you can replace the temporary
procmailrc file with your permanent one (the one with example name
'~/.proc_cs'). If any mail arrived while you were moving things over,
sort through '~/mail/forwarded_mail_tmp' and put the mail in the correct
folders. Once this is empty, you can then delete the file.

You should now be moved over without having lost any mail.

A few things to consider:

  - Your forwarded mail will still show a To: header of
    foo@cs.stevens.edu or foo@stevens.edu (from pipeline) This can be
    used for sorting incoming mail into different inboxes. One setup
    would be using 'inbox' for coglib.com emails, 'guinness' or 'cs' for
    cs.stevens.edu emails, and 'pipeline' for stevens.edu emails. The
    problem occurs when an address you are forwarding from is subscribe
    to a mailing/advertisement list. Since the list name is specified
    rather than the individual recipient, you wouldn't be able to sort
    based on the To header. One solution is to use address extensions
    for forwarded mail. Tell pipeline to forward stevens.edu emails to
    foo+pipeline@coglib.com and CS to forward emails to
    foo+guinness@coglib.com. You can then sort these mails on the
    X-Original-To header (see example at http://www.coglib.com/faq/).
    The rules that catch all mail for a forwarded account should go at
    the END of your procmailrc file so that more specific rules have a
    chance to catch the mail first.

  - Using address extensions can be very helpful for sorting. They are
    even more useful if you change the address at the source rather than
    allowing your CS or pipeline account to continue forwarding mail.
    Changing your email address with Amazon and others, not only allows
    you to set a per website extension for more fine grained filtering,
    it also cuts out the middle-man of either guinness or pipeline in
    mail delivery. If a website doesn't know your coglib email, then
    when CS goes down (and it will), you won't get those emails even
    though coglib is up.

  - Email forwarded from guinness will still be marked with ASSP's spam
    designation. To remove all traces of this, use the following
    procmail rule:

        :0f
        * ^X-Assp
        | sed -e '/^X-Assp-/d ; /^Subject:/ s/\[SPAM\] //g;'

    Make sure to put this at the TOP of your procmailrc file to make
    sure this crud is removed before any further processing.

One other note about moving over. If you still have your SpamAssassin
bayes files on CS, don't bother transferring them over to coglib. Since
coglib is running the newest version of SpamAssassin, it will not read
these older format files. Do, however, bring over the rest of your
'.spamassassin' directory including your 'user_prefs' file and any
whitelisting settings. Be sure to see the FAQ at
http://www.coglib.com/faq/ for more information on how to configure
procmail to use SpamAssassin as well as how to use and train
SpamAssassin.