This is a useful tip for Hiptop/Sidekick covering how to overcome the weaknesses of its email client. The Hiptop/Sidekick treats everything as a POP3 server (even when you set your email account’s server to IMAP or IMAP-SSL). This makes things a little tricky if you rely on IMAP as I do. So instead this tip suggests that you can do a couple of things to work-around some of the limitations.
Firstly, to allow you to sync email sent from your Hiptop with your primary email account you can:
1. Change the “From” and “Reply-To” addresses on your Hiptop to your primary email account.
2. Add a bcc from your Hiptop to your primary email account, every email sent from your Hiptop then gets also sent to your primary email address
3. Add a procmail (or sieve – see below) rule on your primary email server filing everything bcc’ed from your Hiptop into your Sent folder.
Secondly, to send all email from your primary email account you can add a procmail or sieve rule to cc all email directly to your email address. This is best done for non-mailing list emails and after spam processing has taken place.
The tip in the link above uses a procmail recipe for some of this but I prefer sieve and I’ve included that recipe below.
if address “return-path” “email@hiptop.com.au” {
addflag “\\Seen”;
fileinto “Sent”;
stop;
}
*insert whatever filing/anti-spam stuff in here*
if size :under 100K {
redirect “email@hiptop.com.au”;
keep;
}
keep;
