From: Harry G. M. J. <w5...@wo...> - 2005-12-02 17:50:37
|
I downloaded fetchmail-6.3.0 and things went very nicely except for a couple minor issues. There may be other things I find later, but I've been using it today with only the following minor problems. First: I upgraded from fetchmail-6.2.5.4 with 6.3.0. When I downloaded fetchmail-6.2.5.4 and did the gpg --verify on the signature I got: gpg: Signature made Sun Nov 13 06:58:22 2005 MST using DSA key ID 052E7D95 gpg: Good signature from "Matthias Andree <mat...@gm...>" But, when I downloaded fetchmail-6.3.0 and did the gpg --verify on the signature I got: gpg: Signature made Wed Nov 30 16:41:57 2005 MST using DSA key ID 052E7D95 gpg: BAD signature from "Matthias Andree <mat...@gm...>" This was with the tar.bz2 download in each case. Second: The man page for fetchmail-6.3.0 has: The --showdots option (keyword: set showdots) forces fetchmail to show progress dots even if the current tty is not stdout (for example logfiles). Starting with fetch- mail version 5.3.0, progress dots are only shown on stdout by default. With showdots set (seems to be the default) the progress dots appear on stdout AND on any file the logging is redirected to. With showdots NOT set, the progress dots do NOT appear on stdout and do NOT appear on any file the logging is redirected to. I infer from the man page that "no showdots" should be set by default and the when showdots is NOT set, progress dots appear anyway when logging to stdout and NOT when logging is redirected to a file. To me, either the behavior of fetchmail should reflect the man page on this or vice-versa. Everything else looks nice! Harry w5...@ar... -- Harry G. McGavran, Jr. E-mail: w5...@ar... |