| By Nicolas Rougier
Released under the GNU general public license
|Ask your system administrator is certainly the quickest
Another way is to check options from your previous biff program.
|Suppose you are on computer A and your mailserver is on
a computer B that use SSL. You can use the stunnel command on computer A to
redirect packets from computer A to computer B.
Example for pop3 and spop3:
On computer A type stunnel -c -d 110 -r computerB:995
That will redirect packets from computer A:110 to computer B:995 (from pop3 on computer A to spop3 on computer B)
Now you can start gbiff on computer A and configure it to check mail using computer A:110 for address and pop3 for protocol.
|gbiff assumes you have a 'play' command to play a sound.
If you do not have this command, then gbiff will fail at playing a sound
when new mail has arrived.
|It depends if the feature is really useful or not. I have
already a long list of requested features but I have not enough time to consider
all of them.
|gbiff doesn't save your password because it is higlhy unsecure.
There exist some ways to add some security while saving your password but
in any case, if someone really wants to know your password, it is fairly
easy to do so. For these same reasons, it is even more insecure to give your
password on the command line options since a simple command like 'ps -fu'
can then display your password.
If you really want to have your password saved, you can do so by hacking the source but I really do not encourage this.
|Mainly, you have to contribute to gbiff one way or the
other. You can for example translate gbiff in your own language or provide
some code (for example making gbiff dockable in KDE and WindowMaker).
|I fixed a lot of bugs in gbiff since the first version
but it is likely that some bugs remains. If you have trouble with gbiff,
please tell me and try to precise what is the exact bug, gbiff behavior,
if the bug is reproductible... If you only send me an email telling me gbiff
doesn't work, I can hardly help you.