[fetchmail-users] Re: [fetchmail]fetchmail 6.3.4 stable release

[Dale P. <po...@ki...>]

Hello,
I realize that you hate multidrop, and generally disparage and deprecate 
the heck out of it, but for some of us, it's about the only way to make 
our email come out halfway decent. Given the text of this announcement, 
I need to ask some questions, and also see if I'm going to have to 
squirrel away a "last usable" copy of fetchmail source at some point.

Matthias Andree wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Greetings,
>
> I am announcing the release of fetchmail 6.3.4. This new stable version
> of fetchmail fixes several minor bugs, adds a --pidfile option, a
> Vietnamese translation and updates other translations.
> For details, please see below.
>
> The software is available from:
> <http://developer.berlios.de/project/showfiles.php?group_id=1824&release_id=9751>
>
> The fetchmail home pages is:
> <http://www.fetchmail.info/>  or  <http://fetchmail.berlios.de/>
>
> These are the relevant changes in 6.3.4 since 6.3.3;
> unless otherwise noted, changes to this release were made by Matthias Andree:
>
> # DEPRECATED FEATURES AND MAJOR INCOMPATIBLE CHANGE ADVANCE WARNINGS
> * The MX and host alias DNS lookups that fetchmail performs in multidrop mode
>   are obsolete, deprecated and may be removed from a future fetchmail version.
>   They have never supported IPv6 (including IPv6-mapped IPv4) anyhow.
>   
Is this the 'aka' being deprecated, or is it some implicit lookup that I 
won't have to worry about, as long as I have 'aka' properly set up?
> * The monitor and interface options may be removed from a future fetchmail
>   version as they are not sufficiently portable.
> * POP2 is obsolete.
>   Support for POP2 may be removed from a future fetchmail version.
> * RPOP is obsolete, support may be removed from a future fetchmail release.
> * --sslcertck may become a default setting in a future fetchmail version.
> * The multidrop To/Cc guessing code along with the fragile duplicate suppressor
>   is deprecated and may be removed from a future release.
>   
Related to the 'aka' question, I noticed that when I upgraded to 6.3.2, 
multidrop pretty much fell apart for me, delivering all mail to the 
default id. I went back and RTFM, ran fetchmail with extra '-v's, added 
some extra 'aka's, and actually got it running better than ever. Most 
notably, we'd always lived with some duplicates that were now resolved 
and eliminated. Given that I've already spent the effort to adapt to the 
jump from 6.2.x to 6.3.2, am I set for the foreseeable future, or do 
these notes presage major pain to come?
> * The --enable-fallback (fall back to MDA if MTA unavailable) may be removed
>   from a future fetchmail release.
> * The "protocol auto" default inside fetchmail may be removed from a future
>   fetchmail release. Explicit configuration of the protocol is recommended.
>
> # KNOWN BUGS AND WORKAROUNDS:
>   (this section floats upwards through the NEWS to be on top of the list)
> * fetchmail does not handle messages without Message-ID header well
>   (See sourceforge.net bug #780933)
> * Sun Workshop 6 (SPARC) is known to miscompile the lexer in 64-bit mode.
>   Either compile 32-bit code or use GCC to compile 64-bit fetchmail.
>   Note that fetchmail doesn't take advantage of 64-bit code anyways,
>   so compiling 32-bit SPARC code should be fine.
> * The code still isn't 100% ISO-C compliant, some configurations attempt to
>   compile files that are empty after preprocessing, which can cause compiler
>   diagnostics and perhaps jam the compilation on strict compilers.
>
> # BUG FIXES:
> * configure: detect res_* functions properly with newer glibc ABIs.
>   Patch by Miloslav Trmac.
> * tracepolls: add folder information if available. Reported by Terry Brown.
> * lexer: add %option noyywrap to avoid link errors about missing yywrap().
> * a few more type fixes for report/snprintf, patch by Miloslav Trmac.
> * bouncing: fetchmail would still send "General SMTP/ESMTP error." bounces
>   in spite of "no bouncemail" configuration.
> * SSL/TLS: if, for a certain server, an sslfingerprint is specified and
>   sslcertck is NOT set, suppress printing SSL certificate mismatch errors.
>   (Reported by Hannes Erven.)
> * SSL/TLS: always print if the sslfingerprint mismatches, even in silent
>   mode.  (This is for consistency with certificate verification errors.)
>   
I only WISH my ISP would support ssl/tls, or etrn, or odmr. I'm STUCK 
with multidrop, unless I spring for more $$$ to use a different provider 
for my email. I'm already paying $$$$ for a cable ISP and $$ for my 
domain and forwarding, not to mention $$.$e$$ for kids' education, so 
$$$ just to avoid multidrop just isn't in the cards, for now. (My ISP 
has multiple POP boxes, but my domain forwarding doesn't have enough 
capability, so I use multidrop.)

Dale Pontius
> # TRANSLATION UPDATES:
> * German/de (Matthias Andree), French/fr (Matthias Andree), Spanish/es (Héctor
>   García), Polish/pl (Jakub Bogusz), Japanese/ja (Takeshi Hamasaki)
> * New Vietnamese/vi translation (Clytie Siddall).
> * Updated French descriptions for the .spec file (Stéphane Schildknecht,
>   Luc Pionchon, Matthias Andree).
>
> # CHANGES:
> * pidfile: there is a new command-line (--pidfile PATH) and global option for
>   the rcfile (set pidfile [=] "/path/to/pidfile") option to allow overriding
>   the default location of the PID file.
>   Requested by Héctor García, Debian maintainer.
> * specgen.sh: Converted to UTF-8 to support translated texts better.
>
> Regards,
>
> - -- 
> Matthias Andree
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (GNU/Linux)
>
> iD8DBQFEP9NcvmGDOQUufZURArqIAKC6oo1DQLVwV9Luct07Q1AiCY7SvACg0VPL
> fErfpBSuF828FlAI8payL+A=
> =uWqI
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Fetchmail-friends mailing list
> Fet...@li...
> http://lists.ccil.org/cgi-bin/mailman/listinfo/fetchmail-friends
>