You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(73) |
Jul
(22) |
Aug
(42) |
Sep
(11) |
Oct
(23) |
Nov
(40) |
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
|
Feb
|
Mar
(17) |
Apr
(26) |
May
(6) |
Jun
(21) |
Jul
(133) |
Aug
(25) |
Sep
(40) |
Oct
(12) |
Nov
(71) |
Dec
(57) |
2006 |
Jan
(23) |
Feb
(22) |
Mar
(43) |
Apr
(27) |
May
(13) |
Jun
(7) |
Jul
(3) |
Aug
(20) |
Sep
(16) |
Oct
(17) |
Nov
(31) |
Dec
(10) |
2007 |
Jan
(12) |
Feb
(17) |
Mar
(26) |
Apr
(13) |
May
(4) |
Jun
(1) |
Jul
(1) |
Aug
(21) |
Sep
(3) |
Oct
(8) |
Nov
(8) |
Dec
(5) |
2008 |
Jan
(5) |
Feb
(1) |
Mar
(3) |
Apr
(10) |
May
(3) |
Jun
(11) |
Jul
(5) |
Aug
(1) |
Sep
(6) |
Oct
|
Nov
(10) |
Dec
(2) |
2009 |
Jan
(17) |
Feb
(2) |
Mar
(1) |
Apr
(9) |
May
(23) |
Jun
(22) |
Jul
(32) |
Aug
(30) |
Sep
(11) |
Oct
(24) |
Nov
(4) |
Dec
|
2010 |
Jan
(12) |
Feb
(56) |
Mar
(32) |
Apr
(41) |
May
(36) |
Jun
(14) |
Jul
(7) |
Aug
(10) |
Sep
(13) |
Oct
(16) |
Nov
|
Dec
(14) |
2011 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
(16) |
May
(36) |
Jun
(2) |
Jul
|
Aug
(9) |
Sep
(2) |
Oct
(1) |
Nov
(8) |
Dec
(3) |
2012 |
Jan
(1) |
Feb
(5) |
Mar
(1) |
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
(7) |
Sep
(9) |
Oct
(2) |
Nov
(8) |
Dec
(9) |
2013 |
Jan
(11) |
Feb
(6) |
Mar
(14) |
Apr
(10) |
May
|
Jun
(12) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(7) |
Dec
(4) |
2014 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
(7) |
Jul
|
Aug
(8) |
Sep
(8) |
Oct
|
Nov
|
Dec
(2) |
2017 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
(2) |
Feb
(3) |
Mar
(5) |
Apr
(2) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(2) |
Sep
(3) |
Oct
(4) |
Nov
(3) |
Dec
|
2021 |
Jan
(5) |
Feb
(2) |
Mar
(3) |
Apr
(3) |
May
|
Jun
|
Jul
(2) |
Aug
(14) |
Sep
(3) |
Oct
(4) |
Nov
(4) |
Dec
(3) |
2022 |
Jan
|
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2023 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
(2) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
From: Translation P. R. <ro...@tr...> - 2010-12-06 08:46:47
|
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.19-pre1.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.tu-dortmund.de/~ma/fetchmail/fetchmail-6.3.19-pre1.tar.bz2 We can arrange things so that translated PO files are automatically e-mailed to you when they arrive. Ask at the address below if you want this. Thank you for all your work, The Translation Project robot, in the name of your translation coordinator. <coo...@tr...> |
From: <ad...@be...> - 2010-10-21 13:27:03
|
Bug #17295, was updated on 2010-Jun-27 01:42 Here is a current snapshot of the bug. Project: fetchmail Category: None Status: Open Resolution: None Bug Group: None Priority: 2 Submitted by: gtozzi Assigned to : none Summary: Fetchmail provides insufficient log information Details: Hello, First of all, I wish to thank you all for sharing with us this very useful software. I'm running fetchmail 6.3.17+GSS+NTLM+SDPS+SSL+NLS+KRB5 in daemon mode to check a bunch of accounts. The log goes to syslog. Everything works fine but the log files are too inaccurate IMHO. Every line should ALWAYS include the name of the interested account. Example. Now I have: Jun 27 01:33:32 localhost fetchmail[18328]: Attenzione: si continua malgrado la connessione non sia sicura (si raccomanda l'utilizzo di --sslcertck) Jun 27 01:33:43 localhost fetchmail[18328]: Errore di verifica del certificato del server: self signed certificate Jun 27 01:33:43 localhost fetchmail[18328]: Questo significa che la radice che firma il certificato (emesso per /C=US/ST=Unknown/L=Unknown/O=Unknown/OU=Unknown/CN=dime148.dizinc.com/emailAddress=ss...@di...) non è nella posizione dei certificati CA fidati o che c_rehash deve essere eseguito sulla directory del certificato. Per maggiori dettagli consultare le pagine man a proposito di --sslcertpath e di --sslcertfile. This is not su useful, because I can't easily establish which account is triggering this error. I was expection instead: Jun 27 01:33:32 localhost fetchmail[18328]: USERNAME@SERVERNAME: Attenzione: si continua malgrado la connessione non sia sicura (si raccomanda l'utilizzo di --sslcertck) Jun 27 01:33:43 localhost fetchmail[18328]: USERNAME@SERVERNAME: Errore di verifica del certificato del server: self signed certificate Jun 27 01:33:43 localhost fetchmail[18328]: USERNAME@SERVERNAME: Questo significa che la radice che firma il certificato (emesso per /C=US/ST=Unknown/L=Unknown/O=Unknown/OU=Unknown/CN=dime148.dizinc.com/emailAddress=ss...@di...) non è nella posizione dei certificati CA fidati o che c_rehash deve essere eseguito sulla directory del certificato. Per maggiori dettagli consultare le pagine man a proposito di --sslcertpath e di --sslcertfile. Follow-Ups: Date: 2010-Jun-27 14:55 By: m-a Comment: Thanks. This is actually a feature request - it will be a while before this can be implemented. ------------------------------------------------------- For detailed info, follow this link: http://developer.berlios.de/bugs/?func=detailbug&bug_id=17295&group_id=1824 |
From: <ad...@be...> - 2010-10-21 13:26:44
|
Bug #17599, was updated on 2010-Oct-13 11:03 Here is a current snapshot of the bug. Project: fetchmail Category: None Status: Open Resolution: None Bug Group: None Priority: 5 Submitted by: keesbakker Assigned to : shetye Summary: antispam does not work Details: The --antispam option does not work (anymore?). I guess, it must have been disfunctional since 2002-sep-04, when a patch from Sunil Shetye ("double-bounce patch") was applied. (Git commit efe3c6cc82e214142809c77c4f2fa8a58bdef787) The code that was added in sink.c has this piece if (str_find(&ctl->antispam, smtperr)) And the problem is that the function returns a NULL pointer even if it finds the requested value. Notice that there is another location in sink.c which searches the ctl->antispam list using a while loop. Follow-Ups: Date: 2010-Oct-21 13:26 By: m-a Comment: Hi Kees, thanks for the report. I have pushed Sunil's patch to the Git repository. Could you please let us know if that fixes your problem? Best regards Matthias ------------------------------------------------------- For detailed info, follow this link: http://developer.berlios.de/bugs/?func=detailbug&bug_id=17599&group_id=1824 |
From: Matthias A. <mat...@gm...> - 2010-10-16 09:26:14
|
I wrote, in response to Christian's bug report: > OK, I found a few computers where autopoint is apparently skipped if the > AM_GNU_GETTEXT_VERSION macro is missing, so forget my questions. The > solution remains the same though :-) Note that to build from Git since this change, if you have built previously, you need to: # in the source directory autopoint --force # in the build directory (can be the same as the source, # but I personally prefer a separate one): rm -f config.cache ./config.status --recheck ./config.status make clean and only then build, else you get bogus libintl.h failures on some systems that go away with the procedure shown above. HTH Best regards Matthias |
From: Translation P. R. <ro...@tr...> - 2010-10-15 11:27:04
|
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 Slovak team of translators. The file is available at: http://translationproject.org/latest/fetchmail/sk.po (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Sunil S. <sh...@bo...> - 2010-10-14 05:19:34
|
Dear Kees Bakker, Thanks for your comments. I think you will have to subscribe to the fetchmail-devel list before replying to the list. Quoting from Kees Bakker's mail on Wed, Oct 13, 2010: > Thanks Sunil, that was a quick answer :-) > > I've tested it somewhat, not extensive. To me the patch looks > OK. > > It is strange that so few people have complained, because > without a working --antispam option in a fetchmail+MTA > configuration there could be a pile of spam messages that keep > being pulled from the pop server and always rejected by the > MTA due to 450 (for example). > > With this fix AND with the --antispam option such spam messages > will now be flushed from the pop server. > > Again, thanks Sunil for fixing this. > > Kind regards, > Kees Bakker This could be because fetchmail prefers options added to the rcfile in order to keep the command line clean. Due to this, fetchmail's option processing may have been neglected. Thanks for testing. -- Sunil Shetye. |
From: Sunil S. <sh...@bo...> - 2010-10-13 21:40:37
|
This appears to be similar to the recent --nosoftbounce and --nobounce issue where options are not handled exactly the same way as the rcfile parser. Is there a way to push the options also to the parser so that options.c as well as these mismatches can be eliminated? Dear keesbakker, Quoting from ad...@be...'s mail on Wed, Oct 13, 2010: > Summary: antispam does not work > > Details: The --antispam option does not work (anymore?). I guess, it must have been disfunctional since 2002-sep-04, when a patch from Sunil Shetye ("double-bounce patch") was applied. (Git commit efe3c6cc82e214142809c77c4f2fa8a58bdef787) Oops... > The code that was added in sink.c has this piece > > if (str_find(&ctl->antispam, smtperr)) > > And the problem is that the function returns a NULL pointer even if it finds the requested value. > > Notice that there is another location in sink.c which searches the ctl->antispam list using a while loop. It looks like one str_find() was replaced by the loop after my patch while the other was left alone. Let me try restoring the str_find() first!!! Please try this patch and report: ========================================================================= >From 00c78f2ada31b85ea2089a48f6c9467144a4fbf1 Mon Sep 17 00:00:00 2001 From: Sunil Shetye <sh...@bo...> Date: Thu, 14 Oct 2010 00:00:54 +0530 Subject: [PATCH] handle --antispam option correctly --- NEWS | 2 ++ options.c | 2 +- sink.c | 12 +----------- 3 files changed, 4 insertions(+), 12 deletions(-) diff --git a/NEWS b/NEWS index 4cbdd21..9a319e7 100644 --- a/NEWS +++ b/NEWS @@ -63,6 +63,8 @@ fetchmail-6.3.19 (not yet released): of local users, not just at the end. * In multidrop mode, header parsing is now more verbose in -vv mode, so that it becomes possible to see which header is used. +* Make --antispam work from command line (these used to work in rcfiles). + Reported by keesbakker. (Sunil Shetye) # KNOWN BUGS AND WORKAROUNDS: (this section floats upwards through the NEWS file so it stays with the diff --git a/options.c b/options.c index d0c7c2a..a298cb6 100644 --- a/options.c +++ b/options.c @@ -487,7 +487,7 @@ int parsecmdline (int argc /** argument count */, buf = xstrdup(optarg); cp = strtok(buf, ","); do { - struct idlist *idp = save_str(&ctl->antispam, NULL, 0);; + struct idlist *idp = save_str(&ctl->antispam, STRING_DUMMY, 0); idp->val.status.num = xatoi(cp, &errflag); } while diff --git a/sink.c b/sink.c index 3abbd60..92f7b43 100644 --- a/sink.c +++ b/sink.c @@ -441,8 +441,6 @@ static int handle_smtp_report(struct query *ctl, struct msgblk *msg) { int smtperr = atoi(smtp_response); char *responses[1]; - struct idlist *walk; - int found = 0; responses[0] = xstrdup(smtp_response); @@ -466,15 +464,7 @@ static int handle_smtp_report(struct query *ctl, struct msgblk *msg) * messages, which are probably in English (none of the * MTAs I know about are internationalized). */ - for( walk = ctl->antispam; walk; walk = walk->next ) - if ( walk->val.status.num == smtperr ) - { - found=1; - break; - } - - /* if (str_find(&ctl->antispam, smtperr)) */ - if ( found ) + if (str_find(&ctl->antispam, smtperr)) { /* * SMTP listener explicitly refuses to deliver mail -- 1.7.2.3 ========================================================================= -- Sunil Shetye. |
From: <ad...@be...> - 2010-10-13 11:03:46
|
Bug #17599, was updated on 2010-Oct-13 11:03 Here is a current snapshot of the bug. Project: fetchmail Category: None Status: Open Resolution: None Bug Group: None Priority: 5 Submitted by: keesbakker Assigned to : none Summary: antispam does not work Details: The --antispam option does not work (anymore?). I guess, it must have been disfunctional since 2002-sep-04, when a patch from Sunil Shetye ("double-bounce patch") was applied. (Git commit efe3c6cc82e214142809c77c4f2fa8a58bdef787) The code that was added in sink.c has this piece if (str_find(&ctl->antispam, smtperr)) And the problem is that the function returns a NULL pointer even if it finds the requested value. Notice that there is another location in sink.c which searches the ctl->antispam list using a while loop. For detailed info, follow this link: http://developer.berlios.de/bugs/?func=detailbug&bug_id=17599&group_id=1824 |
From: Translation P. R. <ro...@tr...> - 2010-10-12 12:32:03
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-10-11 20:37:05
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-10-10 19:52:05
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-10-10 11:22:04
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-10-10 10:17:08
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-10-10 09:42:06
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-10-10 09:22:03
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-10-10 09:14:12
|
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.18.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.tu-dortmund.de/~ma/fetchmail/fetchmail-6.3.18.tar.bz2 We can arrange things so that translated PO files are automatically e-mailed to you when they arrive. Ask at the address below if you want this. Thank you for all your work, The Translation Project robot, in the name of your translation coordinator. <coo...@tr...> |
From: Matthias A. <mat...@gm...> - 2010-10-10 01:00:17
|
The 6.3.18 release of fetchmail is now available at the usual locations, including <http://developer.berlios.de/projects/fetchmail>. It should fix the nasty authentication errors between fetchmail and Kerberized (GSSAPI) servers, and more issues - detailed below. The source archive is available at: <http://prdownload.berlios.de/fetchmail/fetchmail-6.3.18.tar.bz2> Here are the release notes: fetchmail-6.3.18 (released 2010-10-09, 25936 LoC): # SECURITY IMPROVEMENTS TO DEFANG X.509 CERTIFICATE ABUSE * Fetchmail now only accepts wildcard certificate common names and subject alternative names if they start with "*.". Previous versions would accept wildcards even if no period followed immediately. * Fetchmail now disallows wildcards in certificates to match domain literals (such as 10.9.8.7), or wildcards in domain literals ("*.168.23.23"). The test is overly picky and triggers if the pattern (after skipping the initial wildcard "*") or domain consists solely of digits and dots, and thus matches more than needed. * Fetchmail now disallows wildcarding top-level domains. # CRITICAL BUG FIXES AND REGRESSION FIXES * Fetchmail 6.3.15, 6.3.16, and 6.3.17 would pick up libmd5 to obtain MD5* functions, as an effect of an undocumented Solaris MD5 fix. This caused all MD5-related functions to malfunction if, for instance, libmd5.so was installed on other operating systems as part of libwww on machines where long isn't 32-bits, i. e. usually on 64-bit computers. Fixes Gentoo Bug #319283, reported, including libwww hint, by Karl Hakimian. Side effect: fetchmail will now use -lmd on Solaris rather than -lmd5. * Fetchmail 6.3.17 warned about insecure SSL/TLS connections even if a matching --sslfingerprint was specified. This is an omission from an SSL usability change made in 6.3.17. Fixes Debian Bug#580796 reported by Roland Stigge. * Fetchmail will now apply timeouts to the authentication stage. This stage encompasses STARTTLS/STLS negotiation in IMAP/POP3. Reported missing by Thomas Jarosch. * Fetchmail now cancels GSSAPI authentication properly when encountering GSS errors, such as no or unsuitable credentials. It now sends an asterisk on a line by its own, as required in SASL. This fixes protocol synchronization issues that cause Authentication failures, often observed with kerberized MS Exchange servers. Fixes Debian Bug #568455 reported by Patrick Rynhart, and Alan Murrell, to the fetchmail-users list. Fix verified by Thomas Voigtmann. # BUG FIXES * Fetchmail will no longer print connection attempts and errors for one host in "silent" and "normal" logging modes, unless all connections fail. This should reduce irritation around refused-connection logging if services are only on an IPv4 socket if the host also supports IPv6. Often observed as connections refused to ::1/25 when the subsequent connection to 127.0.0.1/25 then - silently - succeeds. Fetchmail, unless in verbose mode, will collect all connect errors and only report them if all of them fail. * Fetchmail will not try GSSAPI authentication automatically, unless it has GSS credentials. However, if GSSAPI authentication is requested explicitly, fetchmail will always try it. * Fetchmail now parses response to "FETCH n:m RFC822.SIZE" and "FETCH n RFC822.HEADER" in a more flexible manner. (Sunil Shetye) * The manual page clearly states that --principal is for Kerberos 4 only, not for Kerberos 5 or GSSAPI. Found by Thomas Voigtmann. # CHANGES * When encountering incorrect headers, fetchmail will refer to the bad-header option in the manpage. Fixes BerliOS Bug #17272, change suggested by Björn Voigt. * Fetchmail now decodes and reports GSSAPI status codes upon errors. * Fetchmail now autoprobes NTLM also for POP3. * The Fetchmail FAQ has a new item #R15 on authentication failures. # INTERNAL CHANGES * The common NTLM authentication code was factored out from pop3.c and imap.c. # TRANSLATION UPDATES [zh_CN] Chinese/simplified (Ji Zheng-Yu) [cs] Czech (Petr Pisar) [nl] Dutch (Erwin Poeze) [fr] French (Frédéric Marchal) [de] German [it] Italian (Vincenzo Campanella) [ja] Japanese (Takeshi Hamasaki) [pl] Polish (Jakub Bogusz) [sk] Slovak (Marcel Telka) # KNOWN BUGS AND WORKAROUNDS: (this section floats upwards through the NEWS file so it stays with the current release information - however, it was stuck with 6.3.8 for a while) * fetchmail does not handle messages without Message-ID header well (See sourceforge.net bug #780933) * BSMTP is mostly untested and errors can cause corrupt output. * Sun Workshop 6 (SPARC) is known to miscompile the configuration file 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, so compiling 32-bit SPARC code should not cause any difficulties. * fetchmail does not track pending deletes over crashes. * the command line interface is sometimes a bit stubborn, for instance, fetchmail -s doesn't work with a daemon running. * Linux systems may return duplicates of an IP address in some circumstances if no or no global IPv6 addresses are configured. (No workaround. Ubuntu Bug#582585, Novell Bug#606980.) * Kerberos 5 may be broken, particularly on Heimdal, and provide bogus error messages. This will not be fixed, because the maintainer has no Kerberos 5 server to test against. Use GSSAPI. -- Matthias Andree |
From: Translation P. R. <ro...@tr...> - 2010-09-28 12:02:05
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-09-27 09:47:04
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-09-26 19:57:06
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-09-26 19:57:03
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-09-26 19:27:03
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-09-26 18:27:03
|
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 Slovak team of translators. The file is available at: http://translationproject.org/latest/fetchmail/sk.po (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-09-26 18:22:04
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |
From: Translation P. R. <ro...@tr...> - 2010-09-26 18:02:04
|
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 (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) 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...> |