I've been pounding away at a pair of mail conduits, one mostly new and one a hacked up send-mail. The goal has been to get fairly seamless two-way e-mail working from coldsync, something that it doesn't appear to do out of the box. Since I seem to have nailed it down in my environment I though I'd see if anyone else wants to lose some e-mail... Er, try them out and provide feedback. First, I've hacked send-mail into a proper sync conduit. I think that actually nails down a TODO item. The only functional difference is that items are no longer in the Outbox after a sync. The code, however, bears little resemblance to the original. Second, I whipped up a fetch conduit (okay, gutted imap-inbox) that sucks in the contents of a mbox(5) format mailbox into the Inbox. That basically encompasses everything from /var/spool/mail/<mbox> to procmail output files. It's not smart. There's no flidding around trying to see if the message is already on that Palm (which I don't think is really feasible without storing a new header in the mbox messages). I also had a go at a Mail::Box (uber perl e-mail module) fetch conduit, which would allow for synching from mbox, maildir, pop3, imap, and even (eventually) Exchange. The conduit looks like it should mostly work, but Mail::Box just doesn't want to work properly on my Red Hat 8.0 box and the bits that do work are excruitiatingly slow. If anyone has a sane Mail::Box install and wants to play with it further, let me know. c.
Attachment:
mbox-inbox
Description: Perl program
Attachment:
send-mail
Description: Perl program