fetchmail-devel — Development related discussion

[fetchmail-devel] New Indonesian PO file for 'fetchmail' (version 6.3.15-pre2)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'fetchmail' has been submitted
by the Indonesian team of translators.  The file is available at:

    http://translationproject.org/latest/fetchmail/id.po

(This file, 'fetchmail-6.3.15-pre2.id.po', has just now been sent to you in
a separate email.)

All other PO files for your package are available in:

    http://translationproject.org/latest/fetchmail/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/fetchmail.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[fetchmail-devel] New Vietnamese PO file for 'fetchmail' (version 6.3.15-pre2)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'fetchmail' has been submitted
by the Vietnamese team of translators.  The file is available at:

    http://translationproject.org/latest/fetchmail/vi.po

(This file, 'fetchmail-6.3.15-pre2.vi.po', has just now been sent to you in
a separate email.)

All other PO files for your package are available in:

    http://translationproject.org/latest/fetchmail/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/fetchmail.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[fetchmail-devel] New Japanese PO file for 'fetchmail' (version 6.3.15-pre2)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'fetchmail' has been submitted
by the Japanese team of translators.  The file is available at:

    http://translationproject.org/latest/fetchmail/ja.po

(This file, 'fetchmail-6.3.15-pre2.ja.po', has just now been sent to you in
a separate email.)

All other PO files for your package are available in:

    http://translationproject.org/latest/fetchmail/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/fetchmail.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[fetchmail-devel] New French PO file for 'fetchmail' (version 6.3.15-pre2)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'fetchmail' has been submitted
by the French team of translators.  The file is available at:

    http://translationproject.org/latest/fetchmail/fr.po

(This file, 'fetchmail-6.3.15-pre2.fr.po', has just now been sent to you in
a separate email.)

All other PO files for your package are available in:

    http://translationproject.org/latest/fetchmail/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/fetchmail.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[fetchmail-devel] CR missing in messages of 6.3.15-beta2 ?

[Frédéric M. <fre...@wo...>]

Hello,

I just noticed that the message printed in rfc822.c at line 76:

    if (outlevel >= O_DEBUG)
	report_build(stdout, GT_("About to rewrite %s"), buf);

doesn't end with a \n. The next message written at line 212 is therefore 
concatenated with this one.

The same may be true for the message printed in driver.c starting at line 619:

		report_build(stdout, GT_("reading message %s@%s:%d of %d"),
			     ctl->remotename, ctl->server.truename,
			     num, count);

		if (len > 0)
		    report_build(stdout, wholesize ? GT_(" (%d octets)")
				 : GT_(" (%d header octets)"), len);

In my log, it is concatenated with the above mentioned message.

I'm running fetchmail with option -vv.

Frederic

[fetchmail-devel] New Chinese (simplified) PO file for 'fetchmail' (version 6.3.15-pre2)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'fetchmail' has been submitted
by the Chinese (simplified) team of translators.  The file is available at:

    http://translationproject.org/latest/fetchmail/zh_CN.po

(This file, 'fetchmail-6.3.15-pre2.zh_CN.po', has just now been sent to you in
a separate email.)

All other PO files for your package are available in:

    http://translationproject.org/latest/fetchmail/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/fetchmail.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[fetchmail-devel] New Polish PO file for 'fetchmail' (version 6.3.15-pre2)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'fetchmail' has been submitted
by the Polish team of translators.  The file is available at:

    http://translationproject.org/latest/fetchmail/pl.po

(This file, 'fetchmail-6.3.15-pre2.pl.po', has just now been sent to you in
a separate email.)

All other PO files for your package are available in:

    http://translationproject.org/latest/fetchmail/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/fetchmail.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[fetchmail-devel] New Czech PO file for 'fetchmail' (version 6.3.15-pre2)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'fetchmail' has been submitted
by the Czech team of translators.  The file is available at:

    http://translationproject.org/latest/fetchmail/cs.po

(This file, 'fetchmail-6.3.15-pre2.cs.po', has just now been sent to you in
a separate email.)

All other PO files for your package are available in:

    http://translationproject.org/latest/fetchmail/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/fetchmail.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[fetchmail-devel] New Dutch PO file for 'fetchmail' (version 6.3.15-pre2)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'fetchmail' has been submitted
by the Dutch team of translators.  The file is available at:

    http://translationproject.org/latest/fetchmail/nl.po

(This file, 'fetchmail-6.3.15-pre2.nl.po', has just now been sent to you in
a separate email.)

All other PO files for your package are available in:

    http://translationproject.org/latest/fetchmail/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/fetchmail.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[fetchmail-devel] New Italian PO file for 'fetchmail' (version 6.3.15-pre2)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'fetchmail' has been submitted
by the Italian team of translators.  The file is available at:

    http://translationproject.org/latest/fetchmail/it.po

(This file, 'fetchmail-6.3.15-pre2.it.po', has just now been sent to you in
a separate email.)

All other PO files for your package are available in:

    http://translationproject.org/latest/fetchmail/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/fetchmail.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[fetchmail-devel] New template for 'fetchmail' made available

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.  (If you have
any questions, send them to <coo...@tr...>.)

A new POT file for textual domain 'fetchmail' has been made available
to the language teams for translation.  It is archived as:

    http://translationproject.org/POT-files/fetchmail-6.3.15-pre2.pot

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

Below is the URL which has been provided to the translators of your
package.  Please inform the translation coordinator, at the address
at the bottom, if this information is not current:

    http://www.dt.e-technik.uni-dortmund.de/~ma/fetchmail/fetchmail-6.3.15-beta2.tar.bz2

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

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[fetchmail-devel] New Chinese (simplified) PO file for 'fetchmail' (version 6.3.15-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'fetchmail' has been submitted
by the Chinese (simplified) team of translators.  The file is available at:

    http://translationproject.org/latest/fetchmail/zh_CN.po

(This file, 'fetchmail-6.3.15-pre1.zh_CN.po', has just now been sent to you in
a separate email.)

All other PO files for your package are available in:

    http://translationproject.org/latest/fetchmail/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/fetchmail.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[fetchmail-devel] fetchmail 6.3.15-beta2 test release

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

[resend as PGP/MIME due to non-ASCII]

Greetings,

I am asking interested fetchmail users to test a BETA release of
fetchmail.  This beta2 *revises* the long-desired feature to ignore bad
headers in messages and pass them on (now called bad-header accept).
Note that this features is OFF BY DEFAULT and YOU need to turn it on
explicitly by command line or rcfile.

The beta software is available from:
<http://home.pages.de/~mandree/fetchmail/>

These are the relevant changes since the previous release.  Unless
otherwise noted, changes to this release were made by Matthias Andree:

# FEATURE
* Fetchmail now supports a bad-header command line or rcfile option that takes
  exactly one argument, accept or reject (default).  This specifies how messages
  with bad headers retrieved from the current server are to be treated.

# BUG FIXES
* In the rcfile, recognize "local" as abbreviation for "localdomains", as
  documented. The short form has not ever worked since this feature was added in
  January 1997. Reported by Frédéric Marchal.
* Do not close stdout when using mda and "bsmtp -" at the same time.
* Log operating system errors when BSMTP writes fail.
* Fix verbose mode progress formatting regression from 6.3.10; SMTP trace lines
  were no longer on a line of their own. Reported by Melchior Franz.

# CHANGES
* The repository has been converted and moved from the Subversion (SVN) format
  kindly hosted by Graham Wilson over the past years to Git format hosted on
  Gitorious.org.  My deepest thanks to Graham Wilson for this service that
  kept us going when BerliOS's Subversion service was faulty in its early days.
* This opportunity was used to convert BRANCH_6-2 and BRANCH_1-9-9 to
  GnuPG-signed tags, as a sign that these are now closed.
* The outdated SVN trunk is now called "oldtrunk" in Git just to save the work
  for future reference. All development in the past few years was on BRANCH_6-3.
* master was branched from BRANCH_6-3 for user convenience.

# DOCUMENTATION
* Web site and documentation were adjusted to reflect the SVN->Git move.
* The fetchmail manual page is now much clearer on the user id switching
  (seteuid) when using --mda while running as the super user.

# TRANSLATION UPDATES
* [cs]   Czech, by Petr Pisar
* [fr]   French, by Frédéric Marchal
* [de]   German
* [id]   Indonesian, by Andhika Padmawan
* [it]   Italian, by Vincenzo Campanella
* [ja]   Japanese, by Takeshi Hamasaki
* [pl]   Polish, by Jakub Bogusz
* [vi]   Vietnamese, by Clytie Siddall

-- 
Matthias Andree

[fetchmail-devel] fetchmail 6.3.15-beta2 test release

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

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

Greetings,

I am asking interested fetchmail users to test a BETA release of
fetchmail.  This beta2 *revises* the long-desired feature to ignore bad
headers in messages and pass them on (now called bad-header accept).
Note that this features is OFF BY DEFAULT and YOU need to turn it on
explicitly by command line or rcfile.

The beta software is available from:
<http://home.pages.de/~mandree/fetchmail/>

These are the relevant changes since the previous release.  Unless
otherwise noted, changes to this release were made by Matthias Andree:

# FEATURE
* Fetchmail now supports a bad-header command line or rcfile option that takes
  exactly one argument, accept or reject (default).  This specifies how messages
  with bad headers retrieved from the current server are to be treated.

# BUG FIXES
* In the rcfile, recognize "local" as abbreviation for "localdomains", as
  documented. The short form has not ever worked since this feature was added in
  January 1997. Reported by Frédéric Marchal.
* Do not close stdout when using mda and "bsmtp -" at the same time.
* Log operating system errors when BSMTP writes fail.
* Fix verbose mode progress formatting regression from 6.3.10; SMTP trace lines
  were no longer on a line of their own. Reported by Melchior Franz.

# CHANGES
* The repository has been converted and moved from the Subversion (SVN) format
  kindly hosted by Graham Wilson over the past years to Git format hosted on
  Gitorious.org.  My deepest thanks to Graham Wilson for this service that
  kept us going when BerliOS's Subversion service was faulty in its early days.
* This opportunity was used to convert BRANCH_6-2 and BRANCH_1-9-9 to
  GnuPG-signed tags, as a sign that these are now closed.
* The outdated SVN trunk is now called "oldtrunk" in Git just to save the work
  for future reference. All development in the past few years was on BRANCH_6-3.
* master was branched from BRANCH_6-3 for user convenience.

# DOCUMENTATION
* Web site and documentation were adjusted to reflect the SVN->Git move.
* The fetchmail manual page is now much clearer on the user id switching
  (seteuid) when using --mda while running as the super user.

# TRANSLATION UPDATES
* [cs]   Czech, by Petr Pisar
* [fr]   French, by Frédéric Marchal
* [de]   German
* [id]   Indonesian, by Andhika Padmawan
* [it]   Italian, by Vincenzo Campanella
* [ja]   Japanese, by Takeshi Hamasaki
* [pl]   Polish, by Jakub Bogusz
* [vi]   Vietnamese, by Clytie Siddall

- -- 
Matthias Andree
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iEYEARECAAYFAkuHEdkACgkQvmGDOQUufZWNTwCfRW9ePaczgIZEj2WtVnzjfQ0n
3CkAniWsasSvT9Egg226hkJqo12Y3g6J
=hzlq
-----END PGP SIGNATURE-----

Re: [fetchmail-devel] [BUG] \n missing in -v output

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

Am 16.11.2009, 14:07 Uhr, schrieb Matthias Andree <mat...@gm...>:

> Am 13.11.2009, 17:58 Uhr, schrieb Melchior FRANZ
> <mel...@gm...>:
>
>> Since I updated from openSUSE 11.1 to 11.2, fetchmail's output with one
>> verbose
>> level doesn't look right. They use fetchmail 6.3.11, but I checked out
>> 6.3.13
>> from your SVN repository and it has the same bug. (HEAD segfaults.)
>
> Please send a stack backtrace along with the necessary debug information
> (note you need to use branches/BRANCH_6-3, not trunk/) as per
> http://www.fetchmail.info/fetchmail-FAQ.html#G3 - perhaps
> http://leafnode.sourceforge.net/doc_en/FAQ.html#backtrace can also help
> you with the stack backtrace.

Given I still haven't received this or any other evidence, even after  
multiple requests, I'll ignore this allegation.

>> Looks like you want the space only if outlevel > O_VERBOSE, not >=.  (?)
>
> I'll look into that.

Should be fixed in 6.3.15 or -beta2 (not yet released; fix in git commit  
76fd18d1).

-- 
Matthias Andree

Re: [fetchmail-devel] fetchmail 6.3.15-beta1 beta release with "bad-header pass" feature

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

Am 25.02.2010 09:52, schrieb Frédéric Marchal:

>> I think the parser misunderstood your rcfile, so it wouldn't complain.
> 
> It's my fault. Sorry. Now, I'm sure the short form never worked before.

Nevermind. At least you found one of the longest-standing bugs I'd say. :)

(Fetchmail should really have insisted on quotes around strings, then it would
have been obvious.)

-- 
Matthias Andree

Re: [fetchmail-devel] fetchmail 6.3.15-beta1 beta release with "bad-header pass" feature

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

Am 25.02.2010 17:41, schrieb grarpamp:
> Ok. Thank you two for the definition and explanation.
> As my current use is only to fetch to disk [Maildir of course with procmail,
> perhaps maildrop? in the future]

Maildrop is definitely recommended. Procmail has been unmaintained since 2001
and is very hard to configure in a way such that it behaves predictably.

> for use with mutt, and even though I
> may mutt-reply from time to time from the Maildir, I think receipt of such
> bad messages is what I want, rather than miss one. I can always edit the
> bad messages in the Maildir. I did not know fetchmail would not
> receive messages/headers the server thought were valid. Thanks for
> this new feature :)
> 
> PS: I use of invisible mode for years, sometimes I forward things
> and in general prefer headers to be pristine as if they never passed
> through some middle parts of my systems.

Forwarding anything beyond the usually displayed From/To/Cc/Date/Subject headers
is somewhat dangerous to privacy, and "invisible" mode doesn't change those. :)

-- 
Matthias Andree

Re: [fetchmail-devel] fetchmail 6.3.15-beta1 beta release with "bad-header pass" feature

[grarpamp <gra...@gm...>]

Ok. Thank you two for the definition and explanation.
As my current use is only to fetch to disk [Maildir of course with procmail,
perhaps maildrop? in the future] for use with mutt, and even though I
may mutt-reply from time to time from the Maildir, I think receipt of such
bad messages is what I want, rather than miss one. I can always edit the
bad messages in the Maildir. I did not know fetchmail would not
receive messages/headers the server thought were valid. Thanks for
this new
feature :)

PS: I use of invisible mode for years, sometimes I forward things
and in general prefer headers to be pristine as if they never passed
through some middle parts of my systems.

Re: [fetchmail-devel] fetchmail 6.3.15-beta1 beta release with "bad-header pass" feature

[Frédéric M. <fre...@wo...>]

On Thursday 25 February 2010, Matthias Andree wrote:
> Am 25.02.2010 08:14, schrieb Frédéric Marchal:
> > On Wednesday 24 February 2010, Matthias Andree wrote:
> >> Am 24.02.2010 13:08, schrieb Frédéric Marchal:
> >> > The localdomains option cannot be shortened as local as specified in
> >> > the man page (that may not be new, I'm coming from 6.3.9).
> >>
> >> That's a good catch. The abbreviated form has never worked - according
> >> to "git annotate", it was already broken when it was added by ESR on
> >> 1997-01-09, however the fix is simple: change "local(domains)" in
> >> rcfile_l.l to "local(domains)?" and recompile. You need flex installed.
> >
> > I was using the short form with fetchmail 6.3.9. So, it was either not
> > complaining about the invalid option or it was working. I tend to believe
> > it is the latter as our mails were processed as expected and we had
> > problems before that option was added.
>
> I think the parser misunderstood your rcfile, so it wouldn't complain.

It's my fault. Sorry. Now, I'm sure the short form never worked before.

I looked at the backup of the config file and found that it was actually using 
localdomains. Not the short form.

I must have truncated it while modifying the poll entry to split it over 
multiple lines and forgot about it.

Frederic

Re: [fetchmail-devel] fetchmail 6.3.15-beta1 beta release with "bad-header pass" feature

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

Am 25.02.2010 08:14, schrieb Frédéric Marchal:
> On Wednesday 24 February 2010, Matthias Andree wrote:
>> Am 24.02.2010 13:08, schrieb Frédéric Marchal:
>> > The localdomains option cannot be shortened as local as specified in the
>> > man page (that may not be new, I'm coming from 6.3.9).
>>
>> That's a good catch. The abbreviated form has never worked - according to
>> "git annotate", it was already broken when it was added by ESR on
>> 1997-01-09, however the fix is simple: change "local(domains)" in
>> rcfile_l.l to "local(domains)?" and recompile. You need flex installed.
> 
> I was using the short form with fetchmail 6.3.9. So, it was either not 
> complaining about the invalid option or it was working. I tend to believe it 
> is the latter as our mails were processed as expected and we had problems 
> before that option was added.

I think the parser misunderstood your rcfile, so it wouldn't complain.

If there was another list (such as aka) prior to the local option, that list
would have had two more tokens, namely the word "local" and the domain -- and
that may have been sufficient to set delivery apparently straight (while
fetchmail would have mapped multidrop users, which localdomains is actually
supposed to suppress).

> On the other hand, I don' t see any change in the source code between versions 
> 6.3.8 and 6.3.15 that could explain why the option ceased to work or why it 
> would start complaining...

And I don't see how it could have worked as advertised. The lexer used to emits
a LOCALDOMAINS token only on "localdomains", but not on "local". I guess it
would have returned local as a STRING, and then the domain also as a STRING.

HTH

-- 
Matthias Andree

Re: [fetchmail-devel] fetchmail 6.3.15-beta1 beta release with "bad-header pass" feature

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

Am 25.02.2010 07:02, schrieb grarpamp:
>>>> fetchmail.  This beta1 has the long-desired feature to ignore bad
>>>> headers in messages and pass them on.
> 
> Hi group.
> What are 'bad headers'?

Those which (1) are not continuations of the previous line, i. e. do not start
with linear white space, and (2) which do not follow the usual header name plus
colon (:) syntax.

Fetchmail traditionally refused to deliver such messages, now you get the option
to attempt delivery. Some distributors have already been patching fetchmail to
do that. Such patches will be obsolete then (although I expect those
distributors will patch the default to accept such messages).

> Certainly would not all inbound headers be passed through fetchmail
> to disk or pipe, etc?

Yes of course they would, with additional Received: headers to trace that
fetchmail was in the path (unless you set it to invisible mode, which I discourage).

HTH

-- 
Matthias Andree

Re: [fetchmail-devel] fetchmail 6.3.15-beta1 beta release with "bad-header pass" feature

[Frédéric M. <fre...@wo...>]

On Thursday 25 February 2010, grarpamp wrote:
> >>> fetchmail.  This beta1 has the long-desired feature to ignore bad
> >>> headers in messages and pass them on.
>
> Hi group.
> What are 'bad headers'?
> Certainly would not all inbound headers be passed through fetchmail
> to disk or pipe, etc?

The purpose of this option is to ignore the invalid header lines if the server 
on which we are fetching the mail accepted (or even produced) that mail in 
the first place. If the mail can be delivered properly, everybody will be 
happy. If it can't, let's the blame fall on the software that can't handle it 
properly :-).

For instance, a mail header containing a very long line, was wrapped 
improperly by a previous version of my mail server. That is, the continuation 
line didn't start with a space. That invalid continuation line was then seen 
as an invalid mail header and fetchmail used to reject the whole mail as 
invalid. The mail was therefore undeliverable even though any other link in 
the mail delivery chain would have ignored that header just fine and passed 
the mail along. Returning it to the sender was dangerous (as the source 
address might have been forged) so the mail was stuck on the server.

With the new option, you can choose to reject any such mail as it used to be 
and avoid any trouble with the MDA/MTA to which fetchmail is passing the 
mail.

On the other hand, if you know the mail will be delivered without any problem, 
you can let it go and avoid to loose any mail.

Frederic

Re: [fetchmail-devel] fetchmail 6.3.15-beta1 beta release with "bad-header pass" feature

[Frédéric M. <fre...@wo...>]

On Wednesday 24 February 2010, Matthias Andree wrote:
> Am 24.02.2010 13:08, schrieb Frédéric Marchal:
> > The localdomains option cannot be shortened as local as specified in the
> > man page (that may not be new, I'm coming from 6.3.9).
>
> That's a good catch. The abbreviated form has never worked - according to
> "git annotate", it was already broken when it was added by ESR on
> 1997-01-09, however the fix is simple: change "local(domains)" in
> rcfile_l.l to "local(domains)?" and recompile. You need flex installed.

I was using the short form with fetchmail 6.3.9. So, it was either not 
complaining about the invalid option or it was working. I tend to believe it 
is the latter as our mails were processed as expected and we had problems 
before that option was added.

On the other hand, I don' t see any change in the source code between versions 
6.3.8 and 6.3.15 that could explain why the option ceased to work or why it 
would start complaining...

Frederic

Re: [fetchmail-devel] fetchmail 6.3.15-beta1 beta release with "bad-header pass" feature

[grarpamp <gra...@gm...>]

>>> fetchmail.  This beta1 has the long-desired feature to ignore bad
>>> headers in messages and pass them on.

Hi group.
What are 'bad headers'?
Certainly would not all inbound headers be passed through fetchmail
to disk or pipe, etc?
Thx.

Re: [fetchmail-devel] fetchmail 6.3.15-beta1 beta release with "bad-header pass" feature

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

Am 24.02.2010 13:08, schrieb Frédéric Marchal:
> On Wednesday 24 February 2010, Matthias Andree wrote:
>> Greetings,
>>
>> I am asking interested fetchmail users to test a BETA release of
>> fetchmail.  This beta1 has the long-desired feature to ignore bad
>> headers in messages and pass them on.  Note that this features is OFF BY
>> DEFAULT and YOU need to turn it on explicitly by command line or rcfile.
>>
>> The beta software is available from:
>> <http://home.pages.de/~mandree/fetchmail/>
> 
> Two really minor observations so far.
> 
> The localdomains option cannot be shortened as local as specified in the man 
> page (that may not be new, I'm coming from 6.3.9).

That's a good catch. The abbreviated form has never worked - according to "git
annotate", it was already broken when it was added by ESR on 1997-01-09, however
the fix is simple: change "local(domains)" in rcfile_l.l to "local(domains)?"
and recompile. You need flex installed.

> If bad-headers pass is set after a user option, fetchmail complains 
> with "server option after user options at pass". That's a little bit 
> confusing if password is shortened as pass too.

Also a good catch.  I'll change this to accept.  The current lexer/parser
wouldn't have treated this properly in all circumstances anyways because "pass"
can't be mapped to two tokens internally.

I think there will be another beta release or release candidate before 6.3.15...

Thanks for your tests and updating the French translation!

The changes have been committed and pushed to Git. (I have received, but not yet
committed, the Czech and Italian translation updates.)

Happy fetching,

-- 
Matthias Andree