fetchmail-devel — Development related discussion

[fetchmail-devel] New Polish PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Polish language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/pl.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/pl.po
>    http://translation.sf.net/maint/fetchmail/pl.po

This file has already been sent to you separately on 2006-10-12,
as a MIME invoice unpacking the file `fetchmail-6.3.5.pl.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] New Russian PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Russian language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/ru.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/ru.po
>    http://translation.sf.net/maint/fetchmail/ru.po

This file has already been sent to you separately on 2006-10-12,
as a MIME invoice unpacking the file `fetchmail-6.3.5.ru.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] New PO Template file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A new PO Template file, for programs using the textual domain
`fetchmail', has just been made available to language teams for
translation, and a copy is available as:
>    http://www.iro.umontreal.ca/translation/domains/POT/fetchmail-6.3.5.pot

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/domains/POT/fetchmail-6.3.5.pot
>    http://translation.sf.net/domains/POT/fetchmail-6.3.5.pot


In your releases, this file is usually found as `po/fetchmail.pot'.
It is created or updated automatically at `make dist' time, or
whenever you run `make update-po' in the `po/' subdirectory.  Whenever
you have a distribution ready which holds a newer PO Template, please
send the URL of this distribution to the address below.  The
distribution could be a pretest or a snapshot, it does not even have
to compile.  This is to be used by translators, when they need to get
some translation context from your sources.

Within the Translation Project, each PO Template file should have
different version numbers, but since it is not OK to have two
different distributions having same version numbers, this is not a
problem in practice.
Here is the URL information which has just been provided to translators for
your package.  Please inform the translation coordinator, at the address
given below, if the information does not appear to be adequate or current:

>    http://home.pages.de/~mandree/fetchmail/fetchmail-6.3.5.tar.bz2

Translated PO files will later be automatically e-mailed to you.

Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] patch for fetchmail 6.3.5 stable release

[Matthias A. <mat...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well,

a problem with --logfile rendering it useless went undetected through
the 6.3.5-beta* phase.

I have uploaded fm635-daemon-logfile.patch to the BerliOS site at
<http://developer.berlios.de/project/showfiles.php?group_id=1824> that
is supposed to fix this problem. Feedback as to whether it really fixes
- --logfile /SOME/LOG.FILE is needed. Expected behavior is that IN DAEMON
MODE, output shows up in the logfile. Note you cannot use syslog at the
same time. In doubt:

fetchmail -q
fetchmail --daemon 900 --nosyslog --logfile /SOME/LOG.FILE

Please reply to fet...@li... (Reply-To set) or to
fetchmail-devel@... if you have more technical comments.

Kind regards,
Matthias Andree
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFFLI/YvmGDOQUufZURAvv1AJsHU8McNOE7QU9tbXTy4ywtBTqyGwCgm2nA
qh2SZznc+I291KTxZadpnWg=
=ADSQ
-----END PGP SIGNATURE-----

[fetchmail-devel] [Bug #9059] 6.3.5 doesn't preserve logging fd

[<ad...@be...>]

Bug #9059, was updated on 2006-Oct-10 02:53
Here is a current snapshot of the bug.

Project: Community Fetchmail
Category: None
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: ferringb
Assigned to : none
Summary: 6.3.5 doesn't preserve logging fd

Details: 6.3.4 to 6.3.5 changes in daemon.c had a screw up that forced logging fd to 0 (being /dev/null) if opening the logfile *succeeded*; which is contrary to the intention there ;)

For detailed info, follow this link:
http://developer.berlios.de/bugs/?func=detailbug&bug_id=9059&group_id=1824

[fetchmail-devel] fetchmail 6.3.5 stable release

[Matthias A. <mat...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings,

I am announcing the release of fetchmail 6.3.5. This new stable version
of fetchmail fixes several minor bugs and revises the FAQ.

- ---------------------------------------------------------------------
NOTE THAT THE CCIL.ORG MAILING LISTS ARE DEPRECATED AND WILL BE SHUT
DOWN LATER THIS YEAR. Please subscribe to the new lists at
<https://developer.berlios.de/mail/?group_id=1824>:
- - for fetchmail-announce subscribers: subscribe to fetchmail-announce
- - for fetchmail-friends subscribers: subscribe to fetchmail-users
- ---------------------------------------------------------------------

The software is available from:
<http://developer.berlios.de/project/showfiles.php?group_id=1824&release_id=11358>

The fetchmail home pages are:
<http://www.fetchmail.info/>  or  <http://fetchmail.berlios.de/>

These are the relevant changes in 6.3.5 since 6.3.4;
unless otherwise noted, changes to this release were made by Matthias Andree:

fetchmail 6.3.5 (released 2006-10-09):

# 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.
  Non-DNS based alias keywords such as "aka" will remain in fetchmail.
* 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.
* The "envelope Received" option may be removed from a future release, because
  the Received header was never meant to be machine-readable, the format varies
  widely, and various other differences in behavior make parsing Received an
  unreliable undertaking. The enveloper option as such will remain though, in
  order to support Delivered-To, X-Envelope-To, X-Original-To and similar.
  See also <http://home.pages.de/~mandree/mail/multidrop>.
* 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.
* Kerberos IV support may be removed from a future fetchmail release.
* SIGHUP wakeup may be removed from a future fetchmail release and cause it
  to terminate.
* Support for operating systems that are not sufficiently POSIX compliant may be
  removed or operation on such systems may be suboptimal for future releases.

# 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.
* fetchmail expects Received: headers in a particular format when parsing
  envelopes.
* fetchmail does not track pending deletes over crashes
* the command line interface is a bit narrow-minded sometimes, for instance,
  fetchmail -s doesn't work with a running daemon
* some of the logging output is not very helpful
* some of the documentation is still not up to date

# BUG FIXES:
* For protocols such as IMAP that are not delimited by "." lines, truncate the
  input buffer when the message has been completely read, to avoid taking
  trailing garbage into the message if the terminal CRLF is missing. Fixes
  Debian Bug#312415. (Patch suggested by Mike Jones, Manchester Univ.).
* When using NTLM authentication, use regular IMAP response code handler after
  completing NTLM handshake, for robustness and consistency.
  (Taken from the NetBSD portable packages collection, patch-ac.)
* Support Kerberos installations where krb5.h and perhaps roken.h are in
  .../include/krb5.  Taken from NetBSD portable packages collection patch-ae.
* On NetBSD, link against -lroken -lcom_err if --with-kerberos is enabled.
* Drop #include <com_err.h> from Kerberos 5 header file, fixes compile error on
  SUSE Linux 10.0.
* Fix des_pcbc_encrypt compile warnings in kerberos.c line 246.
* If krb5-config provides gssapi library information, use that rather than
  guessing.
* Improve --with-gssapi auto detection for /usr-based GSSAPI installs.
* Fix --with-gssapi builds for NetBSD 3.0.
* Improve KAME/getnameinfo.c portability to Linux libc5 systems.
  Based on a patch by Dan Fandrich.
* Provide INET6 to KAME/getnameinfo.c (only useful on IPv6-enabled systems that
  lack getnameinfo, and there only visible in some Received: headers).
  Found by Dan Fandrich.
* POP3: some UID flags may not be set properly on UIDL lists. (Sunil Shetye)
* Make IMAP4 IDLE work on servers that do not update RECENT counts.
  Reported by Lars Tewes.
* IMAP4 patch by Sunil Shetye:
  - do not depend on server updating RECENT counts at all
  - also enter IDLE loop when messages are present on the server.
* Fix --flush description in the manual page, fetchmail does not mark messages
  seen unless it has successfully delivered them. Suggested by Frederic Marchal.
* Fetchmail no longer attempts to stat the "-" file in daemon mode -- this is a
  special name to read the RC file from stdin, and cannot always be re-read
  anyways. BerliOS bug #7858.
* When looking up ports for a service, the lookup succeeds and the returned
  address family isn't IPv4 or IPv6, properly free the allocated memory from the
  service lookup. Found by Uli Zappe.
* When looking up ports for a service, only look up TCP ports.
* Avoid compiling empty files, to avoid diagnostics from strict compilers.
* If the lockfile ends before the process ID, treat it as stale and unlink it.
  Reported by Justin Pryzby, Debian Bug #376603.
* SIGHUP wake-up behavior was broken since 5.9.13's Cygwin changes, in that for
  non-root users, SIGHUP would abort the first poll and subsequently interfere
  with new polls, and SIGHUP would be ignored for root users. SIGHUP now matches
  documented behavior. SIGUSR1 has always been a wakeup signal for both root
  (undocumented) and non-root users. See also the deprecation warning above.
* Track getaddrinfo() results to properly free them after timeouts and make sure
  that getaddrinfo() isn't interrupted by a timeout (which breaks on MacOS X),
  reported by Uli Zappe.  This should fix Debian Bug#294547 and Bug#377135.
* --logfile is now handled more carefully, errors opening the logfile are
  now reported to the TTY where fetchmail was started from.
* fetchmail now complains and aborts when it cannot properly daemonize itself.
* fix compilation on systems that don't know struct addrinfo (Solaris 2.6).
* ignore SIGPIPE signals and rely on functions to return EPIPE instead. This is
  necessary because the former longjmp() from the signal handler is unsafe and
  makes the whole fetchmail behavior undefined after the event.
* Avoid crash in env.c/host_fqdn if we cannot canonicalize our own hostname.
  Reported by Alexander Holler.
* SSL fix by Miloslav Trmac (Red Hat): free the SSL contexts after the
  connection, to avoid from growing SSL certpaths without bounds, avoid using
  SSL contexts for unrelated connections, and to fix Red Hat Bug #206346.

# CHANGES:
* Rename all fetchmail-internal lock_* functions to fm_lock_*. Obsoletes
  NetBSD portable packages collection patch-ah, patch-ai and patch-aj.
* Configure prints a warning (but proceeds) if Kerberos IV support is enabled.
* In verbose mode, log every IP fetchmail tries to connect to, to avoid
  misleading the user. Suppress EAFNOSUPPORT errors from socket() call, too.
  Fixes Debian Bug #361825, reported by Daniel Baur.
* In idle mode, fetchmail complains about the fetchall option.
* When a connection fails, log not only the IP address, but also host and
  service name and the port number. Log the latter when trying to connect in
  verbose mode, too.
* Keep syslog output at one line per message (this works if no errors occur).
* Fetchmail in verbose mode now logs if it opportunistically upgrades a POP3
  or IMAP connection to TLS security with STLS/STARTTLS.
* fetchmail now supports fo...@ex...=bar user mappings for multidrop boxes.
* switch setjmp/longjmp to sigsetjmp/siglongjmp
* IMAP now supports the EXTERNAL authentication method, courtesy of
  Götz 'nimrill' Babin-Ebell, BerliOS patch #1095 with minor changes.
* The sslproto keywords are now case insensitive, courtesy of
  Götz 'nimrill' Babin-Ebell, BerliOS patch #1095.
* When going to sleep, log for how long.  Suggested by Claudia Ludwig.
* When the server name cannot be canonicalized, log the gai_strerror value.

# TRANSLATION UPDATES:
* Catalan/ca (Ernest Adrogué Calveras), Japanese/ja (Takeshi Hamasaki) - also
  made gettext 0.15 ready, Polish/pl (Jakub Bogusz), Russian/ru (Pavel
  Maryanov), Spanish/es (Héctor García Álvarez), Vietnamese/vi (Clytie Siddall)

# CONTRIBUTED SCRIPTS:
* PopDel.py was revised by Joshua Crawford to display the From: address and
  list every email, even if it has no Subject: header; and not delete the wrong
  message in the presence of mail without Subject: headers.

Regards,

- -- 
Matthias Andree
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFFKfHwvmGDOQUufZURAgKqAKDKa6mUkNnJGMjXMSupaL9u5oCSzwCbBv+C
G+3g7/T/1Rteh1hSP2TCDeA=
=oOOH
-----END PGP SIGNATURE-----

Re: [fetchmail-devel] Bug#390861: fetchmail: Daemon Mode: Can't work with encrypted user private keys

[Nico G. <ni...@ng...>]

severity 390861 minor
tags 390861 + confirmed upstream
thanks

Hi,
* Stephan Seitz <nur...@gm...> [2006-10-03 15:38]:
> Package: fetchmail
> Version: 6.3.4-6
> Severity: normal
> 
> I need to give a client certificate to my server. If my private 
> key is encrypted fetchmail only asks for my password at the 
> server but not for my private key passphrase. The log file says:
> 	Enter PEM pass phrase:
> but fetchmail is already in the background. The man page says 
> for sslkey "This can cause some complications in daemon 
> mode.???, but in which situations will this work in daemon mode? 
> I never found one.
> 
> I would prefer a fix of fetchmail to ask for all passwords 
> before going into background, or at least the man page should be 
> updated to say, that this will never work.

I think updating the manpage would not be enough, I forward
this to upstream. I downgraded the bug to minor since this 
is not a very common situation.
Kind regards
Nico
-- 
Nico Golde - http://www.ngolde.de
JAB: ni...@ja... - GPG: 0x73647CFF
Forget about that mouse with 3/4/5 buttons,
gimme a keyboard with 103/104/105 keys!

[fetchmail-devel] (no subject)

[<tra...@ir...>]

The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.

[fetchmail-devel] New Polish PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Polish language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/pl.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/pl.po
>    http://translation.sf.net/maint/fetchmail/pl.po

This file has already been sent to you separately on 2006-10-02,
as a MIME invoice unpacking the file `fetchmail-6.3.5-b3.pl.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] New Vietnamese PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Vietnamese language.  This particular file, along with all other PO
files pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/vi.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/vi.po
>    http://translation.sf.net/maint/fetchmail/vi.po

This file has already been sent to you separately on 2006-09-30,
as a MIME invoice unpacking the file `fetchmail-6.3.5-b3.vi.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] New Russian PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Russian language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/ru.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/ru.po
>    http://translation.sf.net/maint/fetchmail/ru.po

This file has already been sent to you separately on 2006-09-29,
as a MIME invoice unpacking the file `fetchmail-6.3.5-b3.ru.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] New Japanese PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Japanese language.  This particular file, along with all other PO
files pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/ja.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/ja.po
>    http://translation.sf.net/maint/fetchmail/ja.po

This file has already been sent to you separately on 2006-09-28,
as a MIME invoice unpacking the file `fetchmail-6.3.5-b3.ja.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] New PO Template file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A new PO Template file, for programs using the textual domain
`fetchmail', has just been made available to language teams for
translation, and a copy is available as:
>    http://www.iro.umontreal.ca/translation/domains/POT/fetchmail-6.3.5-b3.pot

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/domains/POT/fetchmail-6.3.5-b3.pot
>    http://translation.sf.net/domains/POT/fetchmail-6.3.5-b3.pot


In your releases, this file is usually found as `po/fetchmail.pot'.
It is created or updated automatically at `make dist' time, or
whenever you run `make update-po' in the `po/' subdirectory.  Whenever
you have a distribution ready which holds a newer PO Template, please
send the URL of this distribution to the address below.  The
distribution could be a pretest or a snapshot, it does not even have
to compile.  This is to be used by translators, when they need to get
some translation context from your sources.

Within the Translation Project, each PO Template file should have
different version numbers, but since it is not OK to have two
different distributions having same version numbers, this is not a
problem in practice.
Here is the URL information which has just been provided to translators for
your package.  Please inform the translation coordinator, at the address
given below, if the information does not appear to be adequate or current:

>    http://www.dt.e-technik.uni-dortmund.de/~ma/fetchmail/fetchmail-6.3.5-beta3.tar.bz2

Translated PO files will later be automatically e-mailed to you.

Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] [PATCH] Don't reuse a single SSL context

[Miloslav T. <mi...@re...>]

Hello,
the SSL code currently reuses a single SSL_CTX for all connections, and
just modifies its parameters for each connection.

It turns out that SSL_CTX_load_verify_locations() and
SSL_CTX_set_default_verify_paths() don't override the previously
configured paths, but append to them; thus
- if two different servers are polled, the certpath configuration of the
  first one will always be used
- if fetchmail is running in daemon mode, the certificate search path
  will grow without bounds, leading to
  http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=206346

The attached patch modifies fetchmail-6.3.5-beta2 to create and free a
SSL context for each connection.

Thanks,
	Mirek

Re: [fetchmail-devel] es.po against svn trunk

[Matthias A. <mat...@gm...>]

Héctor García Álvarez <he...@de...> writes:

> Attached is the diff and the translated file against the one you pointed
> me to.

Much better, thank you. I've used the es.po file with one minor change
for sink.c 1350 where you spelled pclosei which should probably have
been pclose. IF it should still be pclosei, let me know.

-- 
Matthias Andree

Re: [fetchmail-devel] es.po against svn trunk

[Matthias A. <mat...@gm...>]

Héctor García Álvarez <he...@de...> writes:

> El jue, 14-09-2006 a las 23:14 +0200, Matthias Andree escribi.:
>> H.ctor Garc.a .lvarez <he...@de...> writes:
>> 
>> > I attach latest es.po translated and the diff against the version on
>> > svn.
>> 
>> Note that 6.3.X versions stem from the branch:
>> http://mknod.org/svn/fetchmail/branches/BRANCH_6-3
>> 
> Opps I got it from trunk, I'll do it again.
>
>> Your es.po file causes 22 fuzzy and 6 untranslated with "update-gmo" for
>> the branch and 3 fuzzy and 2 untranslated for the trunk.
>> 
> I got it from the web. I wrongly asume that update-gmo was recently
> run.

Doesn't matter, since you don't need the .gmo files for the translation
-- update-gmo is just a quick check to see if the .po file is a complete
translation or not.

> I'll try again later.
>
> Regards,
> P.D: I did all this because I couldn't download the announced beta
> tarball. Is your web down?.

Seems the redirector, home.pages.de, is down. It should currently be
redirecting to http://www.dt.e-technik.uni-dortmund.de/~ma/fetchmail/

-- 
Matthias Andree

Re: [fetchmail-devel] es.po against svn trunk

[Héctor G. Á. <he...@de...>]

Attached is the diff and the translated file against the one you pointed
me to.

Regards,

Héctor

Re: [fetchmail-devel] es.po against svn trunk

[Héctor G. Á. <he...@de...>]

El jue, 14-09-2006 a las 23:14 +0200, Matthias Andree escribió:
> Héctor García Álvarez <he...@de...> writes:
> 
> > I attach latest es.po translated and the diff against the version on
> > svn.
> 
> Note that 6.3.X versions stem from the branch:
> http://mknod.org/svn/fetchmail/branches/BRANCH_6-3
> 
Opps I got it from trunk, I'll do it again.

> Your es.po file causes 22 fuzzy and 6 untranslated with "update-gmo" for
> the branch and 3 fuzzy and 2 untranslated for the trunk.
> 
I got it from the web. I wrongly asume that update-gmo was recently run.

I'll try again later.

Regards,
P.D: I did all this because I couldn't download the announced beta
tarball. Is your web down?.

Héctor

Re: [fetchmail-devel] es.po against svn trunk

[Matthias A. <mat...@gm...>]

Héctor García Álvarez <he...@de...> writes:

> I attach latest es.po translated and the diff against the version on
> svn.

Note that 6.3.X versions stem from the branch:
http://mknod.org/svn/fetchmail/branches/BRANCH_6-3

Your es.po file causes 22 fuzzy and 6 untranslated with "update-gmo" for
the branch and 3 fuzzy and 2 untranslated for the trunk.

-- 
Matthias Andree

[fetchmail-devel] es.po against svn trunk

[Héctor G. Á. <he...@de...>]

I attach latest es.po translated and the diff against the version on
svn.

Regards,

Héctor

[fetchmail-devel] New Japanese PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Japanese language.  This particular file, along with all other PO
files pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/ja.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/ja.po
>    http://translation.sf.net/maint/fetchmail/ja.po

This file has already been sent to you separately on 2006-09-13,
as a MIME invoice unpacking the file `fetchmail-6.3.5-b1.ja.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] New Catalan PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Catalan language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/ca.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/ca.po
>    http://translation.sf.net/maint/fetchmail/ca.po

This file has already been sent to you separately on 2006-08-31,
as a MIME invoice unpacking the file `fetchmail-6.3.5-b1.ca.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

Re: [fetchmail-devel] BUG: [florent@sarcelle.net: Bug#385160: fetchmail: FTBFS: /usr/bin/msgfmt: found 1 fatal error]

[Matthias A. <mat...@gm...>]

Nico Golde <ni...@ng...> writes:

> there is a problem with upstream ja.po localization file, 
> please fix it :)

Not a problem with that file, but with gettext 0.15 :-P

Use the attached patch.

-- 
Matthias Andree

[fetchmail-devel] BUG: [florent@sarcelle.net: [pkg-fetchmail-maint] Bug#385160: fetchmail: FTBFS: /usr/bin/msgfmt: found 1 fatal error]

[Nico G. <ni...@ng...>]

Hi,
there is a problem with upstream ja.po localization file, 
please fix it :)
Kind regards
Nico
----- Forwarded message from Florent Bayle <fl...@sa...> -----

Resent-Date: Tue, 29 Aug 2006 14:03:30 +0000
From: Florent Bayle <fl...@sa...>
To: su...@bu...
User-Agent: KMail/1.9.4
Resent-Date: Tue, 29 Aug 2006 07:03:33 -0700
Subject: [pkg-fetchmail-maint] Bug#385160: fetchmail: FTBFS:
	/usr/bin/msgfmt: found 1 fatal error

Package: fetchmail
Version: 6.3.4-5
Severity: serious
Justification: no longer builds from source

Hello,

There was a problem while autobuilding your package:

> Automatic build of fetchmail_6.3.4-5 on saturne by sbuild/amd64 85
> Build started at 20060828-0043
> ******************************************************************************

[...]

> # recreate gmo-files as workaround
> (cd po; /usr/bin/make update-gmo)
> make[1]: Entering directory `/build/buildd/fetchmail-6.3.4/po'
> rm -f ca.gmo && /usr/bin/msgfmt -c --statistics -o ca.gmo ca.po
> 607 translated messages, 8 fuzzy translations, 4 untranslated messages.
> rm -f cs.gmo && /usr/bin/msgfmt -c --statistics -o cs.gmo cs.po
> 571 translated messages, 33 fuzzy translations, 15 untranslated messages.
> rm -f de.gmo && /usr/bin/msgfmt -c --statistics -o de.gmo de.po
> 619 translated messages.
> rm -f es.gmo && /usr/bin/msgfmt -c --statistics -o es.gmo es.po
> 619 translated messages.
> rm -f fr.gmo && /usr/bin/msgfmt -c --statistics -o fr.gmo fr.po
> 616 translated messages, 3 untranslated messages.
> rm -f ja.gmo && /usr/bin/msgfmt -c --statistics -o ja.gmo ja.po
> ja.po:8: nplurals = 1...
> ja.po:162: ...but some messages have 2 plural forms
> /usr/bin/msgfmt: found 1 fatal error
> 619 translated messages.
> make[1]: *** [ja.gmo] Error 1
> make[1]: Leaving directory `/build/buildd/fetchmail-6.3.4/po'
> make: *** [build-stamp] Error 2
> ******************************************************************************
> Build finished at 20060828-0043
> FAILED [dpkg-buildpackage died]

----- End forwarded message -----

-- 
Nico Golde - JAB: ni...@ja... | GPG: 0x73647CFF
http://www.ngolde.de | http://nion.modprobe.de/blog/
Forget about that mouse with 3/4/5 buttons -
gimme a keyboard with 103/104/105 keys!

[fetchmail-devel] New Russian PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Russian language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/ru.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/ru.po
>    http://translation.sf.net/maint/fetchmail/ru.po

This file has already been sent to you separately on 2006-08-26,
as a MIME invoice unpacking the file `fetchmail-6.3.5-b1.ru.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...