My e-mail knowledge is still stuck in a mid-'90s mentality. I miss the days of xbiff and being told when I have mail as opposed to my client having to ask (and very likely missing Thunderbird's beep). On principle, the reduction of traffic and server load appeals. In college, I had Exceed running on my NT box and the mail server ran XBiff so when mail came in, I was informed immediately. My roommate found a hack to emulate the function on his Performa (a 636 I think) -- a small script and an entry (a tee if I recall) in the .forward file in his Unix home directory and each mail delivery would trigger a little icon near the clock in the upper right of the screen at the same time it was stored on the server.
Is there MacOSX functionality that does something similar? A program to sit on the client and listen for e-mail servers receiving e-mail, accompanied by a program to sit on the server only to be executed on e-mail arrival? Now that I'm more seasoned with procmail recipes, I could be notified only when the inbox is hit with e-mail below a certain spamassassin score and cut way down on mental interrupts.
I'd be tempted to run xbiff on my e-mail host with the X connection tunneled over the ssh, but 1) it would be the only reason to run X (seems a waste) and 2) Dreamhost disapproves of persistent processes (maybe xbiff wouldn't count?).
Is there MacOSX functionality that does something similar? A program to sit on the client and listen for e-mail servers receiving e-mail, accompanied by a program to sit on the server only to be executed on e-mail arrival? Now that I'm more seasoned with procmail recipes, I could be notified only when the inbox is hit with e-mail below a certain spamassassin score and cut way down on mental interrupts.
I'd be tempted to run xbiff on my e-mail host with the X connection tunneled over the ssh, but 1) it would be the only reason to run X (seems a waste) and 2) Dreamhost disapproves of persistent processes (maybe xbiff wouldn't count?).