fetchmail-devel — Development related discussion

Re: [fetchmail-devel] [PATCH] mail delivery via smtp broken

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

Sunil Shetye <sh...@bo...> writes:

> smtp servers (on all non-server machines) listen on the loopback
> interface (i.e. 127.0.0.1) only. However, fetchmail release 6.2.9-rc7,
> by default, attempts to connect to the IP address obtained from
> gethostname(), which typically points to the external interface. Thus,
> fetchmail is no longer able to deliver mails by default!
>
> The problem is that fetchmailhost is overloaded to contain the
> domainname to be used for HELO/EHLO and for rcpt address and also to
> contain the default SMTP host. Previously, it was localhost, but
> after changes in r4382, it became the actual hostname. For smtp
> servers listening on localhost only, mail delivery consequently fails.
>
> This patch should fix this broken behaviour.

Thanks, applied for upcoming -rc8.

-- 
Matthias Andree

Re: [fetchmail-devel] [PATCH] fix for error messages

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

Sunil Shetye <sh...@bo...> writes:

> Some of the error messages are either incorrect or confusing. Here are
> some sample messages that this patch fixes.

Thanks, applied for upcoming -rc8.

-- 
Matthias Andree

[fetchmail-devel] [PATCH] mail delivery via smtp broken

[Sunil S. <sh...@bo...>]

Hi,

smtp servers (on all non-server machines) listen on the loopback
interface (i.e. 127.0.0.1) only. However, fetchmail release 6.2.9-rc7,
by default, attempts to connect to the IP address obtained from
gethostname(), which typically points to the external interface. Thus,
fetchmail is no longer able to deliver mails by default!

The problem is that fetchmailhost is overloaded to contain the
domainname to be used for HELO/EHLO and for rcpt address and also to
contain the default SMTP host. Previously, it was localhost, but
after changes in r4382, it became the actual hostname. For smtp
servers listening on localhost only, mail delivery consequently fails.

This patch should fix this broken behaviour.

==============================================================================
Index: fetchmail/fetchmail.c
===================================================================
--- fetchmail/fetchmail.c	(revision 4393)
+++ fetchmail/fetchmail.c	(working copy)
@@ -1156,7 +1156,7 @@
 	     * Make sure we have a nonempty host list to forward to.
 	     */
 	    if (!ctl->smtphunt)
-		save_str(&ctl->smtphunt, fetchmailhost, FALSE);
+		save_str(&ctl->smtphunt, "localhost", FALSE);
 
 	    /*
 	     * Make sure we have a nonempty list of domains to fetch from.
==============================================================================

-- 
Sunil Shetye.

[fetchmail-devel] [PATCH] fix for error messages

[Sunil S. <sh...@bo...>]

Hi,

Some of the error messages are either incorrect or confusing. Here are
some sample messages that this patch fixes.

Old message: socket error while delivering to SMTP host mailserver
Problem: It appears as if mails are being delivered back to the
mailserver and not to the smtp server.
New message: socket error while fetching from user@mailserver and delivering to SMTP host smtpserver

Old message: socket error while fetching from mailserver
Problem: It is not obvious which account had a problem if you (or
multiple users logging to syslog) are polling from multiple accounts
on same mailserver.
Old message: socket error while fetching from user@mailserver

Old message: SMTP transaction error while fetching from mailserver
New message: SMTP transaction error while fetching from user@mailserver and delivering to SMTP host smtpserver

Old message: Option --remote is not supported with POP3
New message: Option --folder is not supported with POP3

-- 
Sunil Shetye.

[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
>    ftp://tiger.informatik.hu-berlin.de/pub/po/maint/fetchmail/pl.po

This file has already been sent to you separately on 2005-11-03,
as a MIME invoice unpacking the file `fetchmail-6.2.9-rc7.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
>    ftp://tiger.informatik.hu-berlin.de/pub/po/maint/fetchmail/ru.po

This file has already been sent to you separately on 2005-11-03,
as a MIME invoice unpacking the file `fetchmail-6.2.9-rc7.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.2.9-rc7.pot

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

>    ftp://ftp.unex.es/pub/gnu-i18n/po/domains/POT/fetchmail-6.2.9-rc7.pot
>    http://translation.sf.net/domains/POT/fetchmail-6.2.9-rc7.pot
>    ftp://tiger.informatik.hu-berlin.de/pub/po/domains/POT/fetchmail-6.2.9-rc7.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://download.berlios.de/fetchmail/fetchmail-6.2.9-rc7.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...

Re: [fetchmail-devel] Poll: log level for "sleeping at ..."/"awakened at ..."

[Rob M. <rob...@gm...>]

On 31/10/05, Matthias Andree <mat...@gm...> wrote:
>
> At what verbosity should we log "sleeping at <date>"/"awakened at
> <date>" to the screen? Currently, it's logged whenever "--silent" isn't
> used. The debian patch changes this to "-v" level. Printing this in
> non-silent/non-verbose mode hints to the user that fetchmail isn't
> hanging and regularly checking for mail, but I'd personally not mind
> using -v.
>
> At what verbosity should we log these two messages to syslog? While
> there are valid reasons not to log these, the option is a keepalive
> timestamp in the log, to see when fetchmail was running and when it
> stopped, so I'm inclined to leave the syslog as it is now.

<Shrugs> I run fetchmail in silent mode to avoid these messages, so
I'd be in favour of moving the messages to verbose.

However, it doesn't exactly bother me to leave it running in silent mode.

--
                 Please keep list traffic on the list.
Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

[fetchmail-devel] Poll: log level for "sleeping at ..."/"awakened at ..."

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

Greetings,

The Debian BTS has a bug open that is titled
"fetchmail: shouldn't print sleeping at <date> while logging into syslog"
See <http://bugs.debian.org/282259>

The question is:

At what verbosity should we log "sleeping at <date>"/"awakened at
<date>" to the screen? Currently, it's logged whenever "--silent" isn't
used. The debian patch changes this to "-v" level. Printing this in
non-silent/non-verbose mode hints to the user that fetchmail isn't
hanging and regularly checking for mail, but I'd personally not mind
using -v.

At what verbosity should we log these two messages to syslog? While
there are valid reasons not to log these, the option is a keepalive
timestamp in the log, to see when fetchmail was running and when it
stopped, so I'm inclined to leave the syslog as it is now.

Opinions welcome.

Regards,

-- 
Matthias Andree

[fetchmail-devel] fetchmail 6.2.9-rc7 available (fix galore)

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

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

Greetings,

I have just released fetchmail 6.2.9-rc7, yet another release candidate
before 6.3.0, after yet another bugfix evening.

- -----------------------------------------------------------------------
Support call - fetchmail needs funding:
<https://developer.berlios.de/developer/make_donation.php?user_id=2007>
- -----------------------------------------------------------------------

For distributors, please upload this to every unstable/testing/current
distribution that you have (do not upload to "stable", it changes
behavior in a few places) to expose this to wider testing.

If someone is familiar with Kerberos 5, the automatic detection is
broken, help with fixing configure.ac for Kerberos 5 without krb5-config
will be appreciated.

Changes since -rc6 are:
* fetchmailconf -h documents the fetchmailconf -h option. Matthias Andree
* fetchmailconf -V now prints the fetchmailconf version. Matthias Andree
* Add support for SubjectAltName (RFC-2595 or 2818), to avoid bogus certificate
  mismatch errors. Patch by Roland Stigge, Debian Bug#201113. (MA)
* make fetchmail --silent --quit really silent, Debian Bug #229014 by Dr.
  Andreas Krüger.  Matthias Andree
* cleanup --quit handling again (so that --silent --quit just kills the
  existing daemon, rather than continue running), and document it more clearly.
  Matthias Andree
* Print an error message if multiple "defaults" records are found in the
  configuration file.  Matthias Andree
* Bury on_exit officially - the necessary code had been missing from 6.0.0,
  6.2.0, 6.2.5.  Matthias Andree
* Exit with error if the lock file cannot be read.  Matthias Andree
* Exit with error if the lock file cannot be created exclusively, this got
  broken in a 6.2.6-pre, 6.2.5.2 and older were fine.  Matthias Andree
* Do not break some other process's lockfile in "-q" mode, but wait for the
  other process's exit.  Matthias Andree
* Man page: --sslfingerprint points user to x509(1ssl) and gives an example
  how to use it. Debian Bug#213484, Eduard Bloch. (MA)
* Try to obtain FQDN as our own host by default, rather than using "localhost".
  If hostname cannot be qualified, complain noisily and continue, unless
  Kerberos, ODMR or ETRN are used (these require a FQDN).
  Partial fix of Debian Bug#150137. Fixes Debian Bug#316454.  Matthias Andree
* fetchmailconf now sets the service properly after autoprobe. Fixes Debian
  Bug#320645.  Matthias Andree
* fetchmail.man: Fix Debian Bug#241883, making global options more clear. Matt
  Swift, Matthias Andree.

I seek everyone to test it out, report remaining bugs, update outdated
translations (send your translated .po files to the translation
project's robot, it'll forward your translation to the -devel list) or
send patches for documentation or report inconsistencies (including
formatting!) in the documentation.

The software is available from:
<https://developer.berlios.de/project/showfiles.php?group_id=1824&release_id=7815>
<http://home.pages.de/~mandree/fetchmail/>


Regards,

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

iD8DBQFDZVexvmGDOQUufZURAtBUAJ9AIiALOB7rJKS0f+re5c6Uc8r47ACgyDNI
T9vSFmnx8YtwCtMZCmCQIxk=
=KyCq
-----END PGP SIGNATURE-----

[fetchmail-devel] fetchmail security announcement 2005-02 (CAN-2005-3088)

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

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

fetchmail-SA-2005-02: security announcement

Topic:		password exposure in fetchmailconf

Author:		Matthias Andree
Version:	1.02
Announced:	2005-10-21
Type:		insecure creation of file
Impact:		passwords are written to a world-readable file
Danger:		medium
Credits:	Thomas Wolff, Miloslav Trmac for pointing out
		that fetchmailconf 1.43.1 was also flawed
CVE Name:	CVE-2005-3088
URL:		http://fetchmail.berlios.de/fetchmail-SA-2005-02.txt

Affects:	fetchmail version 6.2.5.2
		fetchmail version 6.2.5
		fetchmail version 6.2.0
		fetchmailconf 1.43   (shipped with 6.2.0, 6.2.5 and 6.2.5.2)
		fetchmailconf 1.43.1 (shipped separately, now withdrawn)
		(other versions have not been checked but are presumed affected)

Not affected:	fetchmail 6.2.9-rc6
		fetchmailconf 1.43.2 (use this for fetchmail-6.2.5.2)
		fetchmailconf 1.49   (shipped with 6.2.9-rc6)
		fetchmail 6.3.0      (not released yet)

Corrected:	2005-09-28 01:14 UTC (SVN) - committed bugfix (r4351)
		2005-10-21                 - released fetchmailconf-1.43.2
		2005-10-21                 - released fetchmail 6.2.9-rc6

0. Release history
==================

2005-10-21	1.00 - initial version (shipped with -rc6)
2005-10-21	1.01 - marked 1.43.1 vulnerable
		     - revised section 4
		     - added Credits
2005-10-27	1.02 - reformatted section 0
		     - updated CVE Name to new naming scheme

1. Background
=============

fetchmail is a software package to retrieve mail from remote POP2, POP3,
IMAP, ETRN or ODMR servers and forward it to local SMTP, LMTP servers or
message delivery agents.

fetchmail ships with a graphical, Python/Tkinter based configuration
utility named "fetchmailconf" to help the user create configuration (run
control) files for fetchmail.

2. Problem description and Impact
=================================

The fetchmailconf program before and excluding version 1.49 opened the
run control file, wrote the configuration to it, and only then changed
the mode to 0600 (rw-------). Writing the file, which usually contains
passwords, before making it unreadable to other users, can expose
sensitive password information.

3. Workaround
=============

Run "umask 077", then run "fetchmailconf" from the same shell. After
fetchmailconf has finished, you can restore your old umask.

4. Solution
===========

For users of fetchmail-6.2.5.2:
- -------------------------------
Download fetchmailconf-1.43.2.gz from fetchmail's project site
<http://developer.berlios.de/project/showfiles.php?group_id=1824&release_id=6617>,
gunzip it, then replace your existing fetchmailconf with it.

For users of fetchmail-6.2.6* or 6.2.9* before 6.2.9-rc6:
- ---------------------------------------------------------
update to the latest fetchmail-devel package, 6.2.9-rc6 on 2005-10-21.
<https://developer.berlios.de/project/showfiles.php?group_id=1824>

A. References
=============

fetchmail home page: <http://fetchmail.berlios.de/>

B. Copyright, License and Warranty
==================================

(C) Copyright 2005 by Matthias Andree, <mat...@gm...>.
Some rights reserved.

This work is licensed under the Creative Commons
Attribution-NonCommercial-NoDerivs German License. To view a copy of
this license, visit http://creativecommons.org/licenses/by-nc-nd/2.0/de/
or send a letter to Creative Commons; 559 Nathan Abbott Way;
Stanford, California 94305; USA.

THIS WORK IS PROVIDED FREE OF CHARGE AND WITHOUT ANY WARRANTIES.
Use the information herein at your own risk.

END OF fetchmail-SA-2005-02.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFDY5UwvmGDOQUufZURAqUhAJ0XxrMg5KiVEzsSTM8bgT9m1z2MyACg5lGh
5a6rj77JM6OycVmrPvINmOY=
=YhtX
-----END PGP SIGNATURE-----

[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.2.9-rc6.pot

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

>    ftp://ftp.unex.es/pub/gnu-i18n/po/domains/POT/fetchmail-6.2.9-rc6.pot
>    http://translation.sf.net/domains/POT/fetchmail-6.2.9-rc6.pot
>    ftp://tiger.informatik.hu-berlin.de/pub/po/domains/POT/fetchmail-6.2.9-rc6.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.2.9-rc6.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] Re: [fetchmail-users] fetchmail 6.2.9-rc6 available (yet another candidate...)

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

On Fri, 21 Oct 2005, Thomas Wolff wrote:

> Hello,
> 
> > * fetchmailconf now changes the output file to mode 0600 BEFORE writing to it,
> >   so there is no window where passwords could be read by the world.
> >   Matthias Andree.
> This doesn't sound quite right. The only safe way is to CREATE the 
> file in 600 mode right away. If you just CHANGE to 600 even before writing 
> to it, there IS an unsafe window.
> Try the following:
> touch x
> tail -f x
> 
> Then in another shell:
> chmod -r x
> echo bla >> x
> 
> "bla" will show up in the first window, read by "tail".

Right you are, and thanks for reporting the problem.
(Thanks also to Miloslav Trmac, who also reported the problem.)

Actually, the new script also sets the umask to 077 before opening the
file, so we're doing the right thing, only the NEWS file is off track.

I have uploaded a new version of a security announcement, now at
http://fetchmail.berlios.de/fetchmail-SA-2005-02.txt and will ship it to
pertinent lists shortly.

I have also withdrawn fetchmailconf-1.43.1 and the corresponding patch
from distribution and uploaded fetchmailconf-1.43.2 for users of
fetchmail-6.2.5.2.

Please, further discussion only on fet...@li....

Warning: reply-to is set - take care should you desire to mail me
directly - some mailers require you to manually pick "To Sender Only" or
"Ignore Reply-To."

-- 
Matthias Andree

[fetchmail-devel] fetchmail 6.2.9-rc6 available (yet another candidate...)

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

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

Greetings,

I have just released fetchmail 6.2.9-rc6, yet another release candidate
before 6.3.0, after further fixes to -rc5, became necessary.

- -----------------------------------------------------------------------
Fetchmail needs your support - please consider a donation via:
<https://developer.berlios.de/developer/make_donation.php?user_id=2007>
- -----------------------------------------------------------------------

Changes since -rc5 are:
* fetchmailconf now changes the output file to mode 0600 BEFORE writing to it,
  so there is no window where passwords could be read by the world.
  Matthias Andree.
* Missed --port/--service/--ssl cleanups in the manual. Reminder from Thomas
  Wolff. (MA)
* Complain in POP3 if NTLM/MSN auth is requested but had not been enabled at
  compile time. This configuration mismatch now causes an error message and
  authentication failure. Found by Yves Boisjoly.  Matthias Andree
* fetchmailconf now allows expert users to choose the authorization type and
  also offers MSN and NTLM, suggested by Yves Boisjoly. Matthias Andree
* fetchmailconf now (as of 1.49) writes its version to the comment of the
  saved run control file. Matthias Andree
* Properly shut down SSL connections. Berlios Patch #647 by Arkadiusz
  Miśkiewicz. (MA)
* Global variable cleanup, to fix daemon mode reinitialization problems. Patch
  by Sunil Shetye. (MA)

I seek everyone to test it out, report remaining bugs, update outdated
translations (send your translated .po files to the translation
project's robot, it'll forward your translation to the -devel list) or
send patches for documentation or report inconsistencies (including
formatting!) in the documentation.

The software is available from:
<https://developer.berlios.de/project/showfiles.php?group_id=1824&release_id=7672>
<http://home.pages.de/~mandree/fetchmail/>


Regards,

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

iD8DBQFDWPWYvmGDOQUufZURAo3jAKCPkUpdm2p551anp1thfgR+vr6vEwCgrEQ7
uURXLUk1WBt1aDzIiDibqeA=
=aYrG
-----END PGP SIGNATURE-----

Re: [fetchmail-devel] [PATCH] uninitialized variables in daemon mode

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

Sunil Shetye <sh...@bo...> writes:

> fetchmail has too many global variables which are not being
> initialized properly. This affects the daemon mode as variables which
> are modified for a particular mailbox/poll never get reset back to the
> original value, thus affecting all the mailboxes/polls from that point
> on.

I have merged your patch. -rc6 due out later today.

-- 
Matthias Andree

[fetchmail-devel] [Patch #647] fix SSL/TLS transmission shutdown

[<no...@be...>]

Patch #647 has been updated. 

Project: fetchmail
Category: None
Status: Open
Submitted by: arekm
Assigned to : none
Summary: fix SSL/TLS transmission shutdown

-------------------------------------------------------
For more info, visit:

http://developer.berlios.de/patch/?func=detailpatch&patch_id=647&group_id=1824

[fetchmail-devel] [PATCH] uninitialized variables in daemon mode

[Sunil S. <sh...@bo...>]

Hi,

fetchmail has too many global variables which are not being
initialized properly. This affects the daemon mode as variables which
are modified for a particular mailbox/poll never get reset back to the
original value, thus affecting all the mailboxes/polls from that point
on.

This patch attempts to sort and fix a few of these variables. This
patch also removes unused variables and moves variables which are
unnecessarily static global.

The idea of this problem came from the fix to the original problem
reported in:

<http://lists.berlios.de/pipermail/fetchmail-users/2005-September/000059.html>.

I suspect that there could be a few more variables of this kind. If
possible, an audit of all global variables should be done.

-- 
Sunil Shetye.

[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
>    ftp://tiger.informatik.hu-berlin.de/pub/po/maint/fetchmail/pl.po

This file has already been sent to you separately on 2005-10-03,
as a MIME invoice unpacking the file `fetchmail-6.2.9-rc5.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
>    ftp://tiger.informatik.hu-berlin.de/pub/po/maint/fetchmail/ru.po

This file has already been sent to you separately on 2005-09-29,
as a MIME invoice unpacking the file `fetchmail-6.2.9-rc5.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.2.9-rc5.pot

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

>    ftp://ftp.unex.es/pub/gnu-i18n/po/domains/POT/fetchmail-6.2.9-rc5.pot
>    http://translation.sf.net/domains/POT/fetchmail-6.2.9-rc5.pot
>    ftp://tiger.informatik.hu-berlin.de/pub/po/domains/POT/fetchmail-6.2.9-rc5.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.2.9-rc5.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] 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.2.9-rc4.pot

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

>    ftp://ftp.unex.es/pub/gnu-i18n/po/domains/POT/fetchmail-6.2.9-rc4.pot
>    http://translation.sf.net/domains/POT/fetchmail-6.2.9-rc4.pot
>    ftp://tiger.informatik.hu-berlin.de/pub/po/domains/POT/fetchmail-6.2.9-rc4.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.2.9-rc4.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...

Re: [fetchmail-devel] [rdenis-debian-bts1@simphalempin.com: [pkg-fetchmail-maint] Bug#329975: fetchmail: IPv6 support]

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

Nico Golde wrote:

> * Matthias Andree <mat...@gm...> [2005-09-26 10:22]:
> > Nico Golde <ni...@ng...> writes:
> > 
> > > tags 329975 + upstream
> > 
> > I think 6.2.9-rc5 can be uploaded to Debian's unstable distribution, so
> > it gets more testing - after the upload please have Rémi retry with
> > -rc5, if that works, another "fixed-upstream" tag might be in order.
> 
> I will prepare an upload next week.

I'm not sure how long I'll delay a 6.3.0 release.

Perhaps I'll release 6.3.0 this week (given positive feedback and a few
translations), perhaps I'll release it in four weeks (if new issues
surface).

> Is there something import I have to keep track on with the new package?

Check the NEWS file, the important stuff is up front.

--enable-inet6 has no effect any more, --enable-netsec (and the
corresponding lines) are gone. Note that the set of translations shipped
with fetchmails has changed - see po/LINGUAS for the current set.

fetchmail now uses automake, and requires system gettext as build and
run-time prerequisite (--with-included-gettext doesn't work, the intl/
directory isn't shipped). There's a new html file for the documentation,
esrs-design-notes.html

Otherwise, nothing I remember off-hand without checking.

> > Does Debian compile 6.2.5 with --enable-inet6? If not, that might be the
> > problem.
> 
> fneq (,$(findstring IPV6,$(DEB_FETCHMAIL_BUILD_OPTIONS)))
>         FETCHCONFOPT += --enable-inet6
> endif
> ifneq (,$(findstring IPV6SEC,$(DEB_FETCHMAIL_BUILD_OPTIONS)))
>         FETCHCONFOPT += --enable-inet6 --enable-netsec
> endif

I don't know sufficient context to judge whether this is the problem or
isn't.

I'm not going to touch 6.2.5 anyways unless someone offers a support
contract with reasonable payment or evidence of a security problem that
isn't configuration-borne or the environment's fault (kernel bug or
such).

Kind regards,

-- 
Matthias Andree

[fetchmail-devel] fetchmail project needs translators!

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

Greetings,

The fetchmail project needs YOU - as translator. If you know your
language well, spell safely, please consider helping with translating
fetchmail. Translations are coordinated by the translation project,
http://translation.sourceforge.net/

The procedure is simple:

1. join your language team (see above link) - it usually means
subscribing to the language team's mailing list and mentioning there
that you'd wish to translate fetchmail message catalogs
2. download the -rc5 tarball to get an up-to-date .pot file
3. perhaps download the .po file from the repository (ask on the
fetchmail-devel list for the exact address)
4. translate -- there are powerful tools to make this easy: There is a
"po-mode" for the emacs editor, and there is "kbabel", a standalone KDE
application.
5. mail the translation to the translation project's robot

6. the robot will archive the translation, check it, and if complete,
send a copy to the fetchmail-devel list.

For the languages marked with an asterisk below, except French, we have
translators. I have been updating the French translation for the nonce,
but I'd rather wish that a native or very experienced (several years in
a Francophone area, with some courses) speaker handled this.

We have outdated translations (that means less work than a new
translation) for Albanian, Danish, Galician, Greek, Japanese, Brazilian
Portuguese, Slovak, Turkish.

These are our current statistics, languages shipping are marked with an
asterisk or plus. Those with asterisk have a translator.

I will not ship the translations without asterisk unless they are
updated soon.

* Language ca.po:         595 translated, 9 fuzzy, 2 untranslated.
* Language cs.po:         580 translated, 16 fuzzy, 10 untranslated.
  Language da.po:         536 translated, 57 fuzzy, 13 untranslated.
* Language de.po:         606 translated.
  Language el.po:         536 translated, 57 fuzzy, 13 untranslated.
* Language es.po:         589 translated, 13 fuzzy, 4 untranslated.
+ Language fr.po:         603 translated, 3 untranslated.
  Language gl.po:         401 translated, 94 fuzzy, 101 untranslated.
  Language ja.po:         515 translated, 72 fuzzy, 19 untranslated.
* Language pl.po:         595 translated, 9 fuzzy, 2 untranslated.
  Language pt_BR.po:      401 translated, 96 fuzzy, 99 untranslated.
* Language ru.po:         595 translated, 9 fuzzy, 2 untranslated.
  Language sk.po:         400 translated, 18 fuzzy, 178 untranslated.
  Language sq.po:         525 translated, 51 fuzzy, 30 untranslated.
  Language tr.po:         538 translated, 56 fuzzy, 12 untranslated.

Regards,

-- 
Matthias Andree

Re: [fetchmail-devel] [rdenis-debian-bts1@simphalempin.com: [pkg-fetchmail-maint] Bug#329975: fetchmail: IPv6 support]

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

Hallo Matthias,

* Matthias Andree <mat...@gm...> [2005-09-26 10:22]:
> Nico Golde <ni...@ng...> writes:
> 
> > tags 329975 + upstream
> 
> I think 6.2.9-rc5 can be uploaded to Debian's unstable distribution, so
> it gets more testing - after the upload please have Rémi retry with
> -rc5, if that works, another "fixed-upstream" tag might be in order.

I will prepare an upload next week.
Is there something import I have to keep track on with the new package?

> Does Debian compile 6.2.5 with --enable-inet6? If not, that might be the
> problem.

fneq (,$(findstring IPV6,$(DEB_FETCHMAIL_BUILD_OPTIONS)))
        FETCHCONFOPT += --enable-inet6
endif
ifneq (,$(findstring IPV6SEC,$(DEB_FETCHMAIL_BUILD_OPTIONS)))
        FETCHCONFOPT += --enable-inet6 --enable-netsec
endif

Regards Nico


-- 
Nico Golde - JAB: ni...@ja... | GPG: 0x73647CFF
http://www.ngolde.de | http://www.muttng.org | http://grml.org

Re: [fetchmail-devel] [rdenis-debian-bts1@simphalempin.com: [pkg-fetchmail-maint] Bug#329975: fetchmail: IPv6 support]

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

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

> tags 329975 + upstream

I think 6.2.9-rc5 can be uploaded to Debian's unstable distribution, so
it gets more testing - after the upload please have Rémi retry with
-rc5, if that works, another "fixed-upstream" tag might be in order.

Does Debian compile 6.2.5 with --enable-inet6? If not, that might be the
problem.

-- 
Matthias Andree