The main window of XkBiff displays one of three small images, signifying mail, no mail, or failure to check. When XkBiff finds new mail it can pop up a window with the From and Subject info from the mail. If the check fails, most probably because your Kerberos tokens expired, it can pop up a message telling you why it failed.
According to the Mime standard,
characters missing in
us-ascii (e.g. þåäö)
can appear in the header fields, encoded as quoted-printable. XkBiff
decodes this correctly.
XkBiff also understands plain POP3, but if you use unencrypted POP, you really shouldn't.
If you are picky about security you should not use plain Pop3, since it sends your password unencrypted over the network. XkBiff don't make this worse in theory, but in practice it means sending your password more often over the network, which might make it easier for a cracker to find it. On the other hand, both Netscape and Microsoft does periodical check for new mail over pop3, and neither of them mentions any security problems with that (as far as I have seen). So the message here is: If you want your mail to be safe, don't use plain pop3! If you use pop3, you might as well use XkBiff also.
XkBiff is free software, but Copyright © Rasmus Kaj 1996 - 1998. There is no warranty (but hey! Micro$oft don't give warranties either).
This is the things that was supposed to be fixed in a future version. Since the project is discontinued, I guess that wont happen now. None of this is what I consider 'serious' errors.
Better geometry management, for instance if the image window is on the lower and/or right edge of the screen the message window pops up off screen by default. Also, 'negative' geometry needs to be recalculated each time the popup pops up.
Different colors (foreground & background) for the different statuses.
Maybe a dialog to enter the password in non-kerberos mode. Right now I use the
getpass()function, which get a password from standard input.
Load color images (xpm, png, gif?) as well as xbm:s.
Some mailers seems to encode 8bit headers as Base64 instead of QP. Seems stupid, IMHO, but I should probably add support for it.
A whole load of clean-up.