Menu
▾
▴
fetchmail-devel — Development related discussion
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
(6) |
Nov
|
Dec
|
|
From: Graham W. <gr...@mk...> - 2005-11-23 17:08:05
|
On Wed, Nov 23, 2005 at 02:45:52PM +0530, Sunil Shetye wrote: > Does this mean that anonymous checkout is going to be stopped? There > are links on http://fetchmail.berlios.de/ pointing to the repository > meant for this. > > It might be better to allow anonymous HTTP read-only access to trunk > and to a few select tags (like the release tags). Access to the > remaining tags, branches, as well as commits to the full tree via HTTP > can then be stopped. The main reason for me wanting to disable HTTP access is because I think the user management issues will be easier if committers have a shell account on the machine, rather than just having access via HTTP. This means that continuing to allow read-only checkouts via HTTP is not an issue for me. > Note that the svn+ssh protocol does not allow anonymous read-only > access as it requires a valid login account on the system. It's also possible to run svnserve to allow read-only checkouts (which is happening now). In the end, I'll probably choose either HTTP or svnserve for read-only checkouts. -- gram |
|
From: Graham W. <gr...@mk...> - 2005-11-23 17:04:51
|
On Wed, Nov 23, 2005 at 04:34:32PM +0530, Sunil Shetye wrote: > The user "anonsvn" will be a valid login account with a shell access. > Also, the repository has to be writable by "anonsvn" even for a > readonly checkout. So, it is possible to just: This is true for the old BDB filesystem type. The fetchmail repository mas been switched to the newer fsfs filesysttem type, which means that write access is not needed for read access any longer. > $ ssh -l anonsvn decoy.wox.org > $ rm -rf /path/to/repository/of/fetchmail FYI, the canonical name of the server is now mknod.org. (Though, the old name will work indefinitely for read-only checkouts.) -- gram |
|
From: Matthias A. <mat...@gm...> - 2005-11-23 15:26:23
|
Sunil Shetye <sh...@bo...> writes: > Quoting from Matthias Andree's mail on Wed, Nov 23, 2005: >> I have added a FAQ item No. O15, to ship with the upcoming fetchmail >> 6.3.0, to document this, so we have our own explanation for it and need >> not relay on third-party sites. > > Please update the FAQ on fetchmail.berlios.de. This would my link next > time then :-) > > <http://fetchmail.berlios.de/fetchmail-FAQ.html#O15> Done. -- Matthias Andree |
|
From: Sunil S. <sh...@bo...> - 2005-11-23 12:15:45
|
Quoting from Matthias Andree's mail on Wed, Nov 23, 2005: > I have added a FAQ item No. O15, to ship with the upcoming fetchmail > 6.3.0, to document this, so we have our own explanation for it and need > not relay on third-party sites. Please update the FAQ on fetchmail.berlios.de. This would my link next time then :-) <http://fetchmail.berlios.de/fetchmail-FAQ.html#O15> -- Sunil Shetye. |
|
From: Sunil S. <sh...@bo...> - 2005-11-23 12:01:44
|
Quoting from Matthias Andree's mail on Wed, Nov 23, 2005: > > It might be better to allow anonymous HTTP read-only access to trunk > > and to a few select tags (like the release tags). Access to the > > remaining tags, branches, as well as commits to the full tree via HTTP > > can then be stopped. > > > > Note that the svn+ssh protocol does not allow anonymous read-only > > access as it requires a valid login account on the system. > > Can the server side of subversion be configured to set particular users > to "read-only"? If so, I see no problem with creating a read-only user > named "anonsvn" or similar. The user "anonsvn" will be a valid login account with a shell access. Also, the repository has to be writable by "anonsvn" even for a readonly checkout. So, it is possible to just: $ ssh -l anonsvn decoy.wox.org $ rm -rf /path/to/repository/of/fetchmail Of course, a restricted shell along with a limited set of commands (like svnserve) in PATH may be more safer. But, it would be better to avoid this completely. -- Sunil Shetye. |
|
From: Matthias A. <mat...@gm...> - 2005-11-23 11:09:06
|
Sunil Shetye <sh...@bo...> writes: > It might be better to allow anonymous HTTP read-only access to trunk > and to a few select tags (like the release tags). Access to the > remaining tags, branches, as well as commits to the full tree via HTTP > can then be stopped. > > Note that the svn+ssh protocol does not allow anonymous read-only > access as it requires a valid login account on the system. Can the server side of subversion be configured to set particular users to "read-only"? If so, I see no problem with creating a read-only user named "anonsvn" or similar. -- Matthias Andree |
|
From: Sunil S. <sh...@bo...> - 2005-11-23 10:13:07
|
Quoting from Graham Wilson's mail on Mon, Nov 21, 2005: > I believe the problem with BerliOS.de was that we were using BDB in > combination with tunelling over SSH. The fetchmail repository at > mknod.org uses the new fsfs repository type, and therefore shouldn't see > any problems like we did in the past. (The repository format has been > switched since the commit mails stopped.) > > I'd like to get you and Rob switched over to the new access method well > before I disable HTTP Subversion access. If we see any problems in that > time period that we can't solve, I'm more than happy to continue running > the HTTP service as needed. > > Again, let me know of any concerns or if any other problems arise. Does this mean that anonymous checkout is going to be stopped? There are links on http://fetchmail.berlios.de/ pointing to the repository meant for this. It might be better to allow anonymous HTTP read-only access to trunk and to a few select tags (like the release tags). Access to the remaining tags, branches, as well as commits to the full tree via HTTP can then be stopped. Note that the svn+ssh protocol does not allow anonymous read-only access as it requires a valid login account on the system. -- Sunil Shetye. |
|
From: Karl E. <ke...@su...> - 2005-11-22 19:38:20
|
Matthias Andree <mat...@gm...> writes:
> Excellent, at least one of the translations is back on track.
>
> Happy day. :-)
Great - I hope you will receive more files some time soon ;-)
--
| ,__o
| _-\_<,
| (*)/'(*)
|
|
From: Graham W. <gr...@mk...> - 2005-11-21 20:41:40
|
On Mon, Nov 21, 2005 at 08:30:44PM +0100, Matthias Andree wrote: > On Mon, 21 Nov 2005, Graham Wilson wrote: > > Also, it's now possible to access the repository using SVN tunneled over > > SSH. > > Will that be more stable than BerliOS.de? We switched away from them > because svn+ssh:// was too flakey. I believe the problem with BerliOS.de was that we were using BDB in combination with tunelling over SSH. The fetchmail repository at mknod.org uses the new fsfs repository type, and therefore shouldn't see any problems like we did in the past. (The repository format has been switched since the commit mails stopped.) I'd like to get you and Rob switched over to the new access method well before I disable HTTP Subversion access. If we see any problems in that time period that we can't solve, I'm more than happy to continue running the HTTP service as needed. Again, let me know of any concerns or if any other problems arise. -- gram |
|
From: Matthias A. <mat...@gm...> - 2005-11-21 20:30:47
|
On Mon, 21 Nov 2005, Graham Wilson wrote: > Also, it's now possible to access the repository using SVN tunneled over > SSH. Will that be more stable than BerliOS.de? We switched away from them because svn+ssh:// was too flakey. -- Matthias Andree |
|
From: Graham W. <gr...@mk...> - 2005-11-21 19:16:06
|
On Mon, Nov 21, 2005 at 04:50:44PM +0100, Matthias Andree wrote: > I have not received any -svn announcements either, so we'd better ping > Graham. (Bcc:d for I don't recall which address he'd used to post here.) > > Before that, it sent the small ones out fast and the large ones later. > > Graham, could you check the SVN log mailing software on decoy.wox.org? Problem was on my end; sorry. I changed the repository format some time ago, and neglected to copy the old post-commit hook script. Things should be fixed now. Please let me know if that is not the case. Also, it's now possible to access the repository using SVN tunneled over SSH. In the future, this will be the preferred access mechanism, and HTTP access will be turned off. For more information you can contact me personally. (The HTTP access won't be turned off for sometime, so there is no need to switch things over soon.) Let me know if there are any other problems or issues that I can help with. -- gram |
|
From: Rob F. <rf...@fu...> - 2005-11-21 17:04:34
|
Matthias Andree wrote: > Before that, it sent the small ones out fast and the large ones later. The large ones were delayed because MailMan waited for me (or another list admin) to approve them, since I have it set not to automatically accept/forward any mail over a certain size. (I forget what size now.) It's generally just the translations that result in huge diffs. -- ==============================| "A microscope locked in on one point Rob Funk <rf...@fu...> |Never sees what kind of room that it's in" http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind" |
|
From: Matthias A. <mat...@gm...> - 2005-11-21 16:50:51
|
Rob Funk <rf...@fu...> writes: > Matthias Andree wrote: >> to bring everybody up to date WRT the latest SVN changes, these are the >> changes to the SVN trunk since 6.2.9-rc9 was released. > > This made me realize that I haven't seen any SVN changes emailed through > fet...@be... since August 4. Anyone else on fetchmail-svn > seeing them? Anyone know why I'm not? I have not received any -svn announcements either, so we'd better ping Graham. (Bcc:d for I don't recall which address he'd used to post here.) Before that, it sent the small ones out fast and the large ones later. Graham, could you check the SVN log mailing software on decoy.wox.org? Thank you. -- Matthias Andree |
|
From: Rob F. <rf...@fu...> - 2005-11-21 16:41:57
|
Matthias Andree wrote: > to bring everybody up to date WRT the latest SVN changes, these are the > changes to the SVN trunk since 6.2.9-rc9 was released. This made me realize that I haven't seen any SVN changes emailed through fet...@be... since August 4. Anyone else on fetchmail-svn seeing them? Anyone know why I'm not? -- ==============================| "A microscope locked in on one point Rob Funk <rf...@fu...> |Never sees what kind of room that it's in" http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind" |
|
From: Translation P. R. <tra...@ir...> - 2005-11-21 15:33:26
|
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-21, as a MIME invoice unpacking the file `fetchmail-6.2.9-rc9.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... |
|
From: Matthias A. <mat...@gm...> - 2005-11-21 11:32:52
|
Greetings, to bring everybody up to date WRT the latest SVN changes, these are the changes to the SVN trunk since 6.2.9-rc9 was released. This was generated with: env TZ=UTC LC_ALL=C svn log -vrHEAD:4461 ------------------------------------------------------------------------ r4471 | m-a | 2005-11-21 10:29:21 +0000 (Mon, 21 Nov 2005) | 8 lines Changed paths: M /trunk/specgen.sh Major overhaul: - drop the bogus email address calculation (it didn't work on NIS or LDAP clients anyways), hardcode fetchmail-devel mailing list at lists.berlios.de - add some magic so that RPMs can be built from -rc versions (or other versions that contain a MINUS character) - drop --enable-inet6, no longer needed and no longer supported ------------------------------------------------------------------------ r4470 | m-a | 2005-11-21 10:27:06 +0000 (Mon, 21 Nov 2005) | 2 lines Changed paths: M /trunk/Makefile.am Take care to ship a complete tarball even if PYTHON isn't installed. Clean up HAVE_PYTHON magic. ------------------------------------------------------------------------ r4469 | m-a | 2005-11-21 09:54:12 +0000 (Mon, 21 Nov 2005) | 1 line Changed paths: M /trunk/specgen.sh Cleanup. Sunil Shetye. ------------------------------------------------------------------------ r4468 | m-a | 2005-11-21 09:54:05 +0000 (Mon, 21 Nov 2005) | 1 line Changed paths: M /trunk/configure.ac Revise without-python check to print a readable warning. Sunil Shetye. ------------------------------------------------------------------------ r4467 | m-a | 2005-11-19 13:24:49 +0000 (Sat, 19 Nov 2005) | 1 line Changed paths: M /trunk/configure.ac Bump version to 6.2.9-rc10. ------------------------------------------------------------------------ r4466 | m-a | 2005-11-19 12:39:14 +0000 (Sat, 19 Nov 2005) | 1 line Changed paths: M /trunk/Makefile.am M /trunk/NEWS M /trunk/configure.ac M /trunk/specgen.sh Fix installation without Python. Sunil Shetye, reported by Peter Church. ------------------------------------------------------------------------ r4461 | m-a | 2005-11-19 03:03:56 +0000 (Sat, 19 Nov 2005) | 1 line Changed paths: M /trunk/po/pl.po M /trunk/po/sq.po Update sq/pl (Albanian/Polish) translations to 6.2.9-rc9. ------------------------------------------------------------------------ -- Matthias Andree |
|
From: Matthias A. <mat...@gm...> - 2005-11-21 11:05:08
|
Sunil Shetye <sh...@bo...> writes: > Quoting from Matthias Andree's mail on Sat, Nov 19, 2005: >> > To check the patch, python needs to be removed from the system first >> > as there is no configure option to disable checking the location of >> > python. >> >> No need to mess with the installation - you can just run this: >> ./configure PYTHON=: [other options here] > > Cool tip. The configure messages look weird, but it works. "weird" is a pretty mild description. It's utterly broken. > This minor patch now emits a warning if python is not found. Also, the > spec file has been cleanup up further. Thanks a lot. I have applied your patch, to ship with -rc10. I have also revised specgen.sh a bit to avoid bogus mail addresses with FM_* unset (we'll just list the developer list address as packager) and to work with versions that contain a "MINUS" character (6.2.9-rc10). -- Matthias Andree |
|
From: Sunil S. <sh...@bo...> - 2005-11-21 08:48:49
|
Quoting from Matthias Andree's mail on Sat, Nov 19, 2005: > > To check the patch, python needs to be removed from the system first > > as there is no configure option to disable checking the location of > > python. > > No need to mess with the installation - you can just run this: > ./configure PYTHON=: [other options here] Cool tip. The configure messages look weird, but it works. This minor patch now emits a warning if python is not found. Also, the spec file has been cleanup up further. -- Sunil Shetye. |
|
From: Matthias A. <mat...@gm...> - 2005-11-19 14:23:55
|
Sunil Shetye <sh...@bo...> writes: > Quoting from Sunil Shetye's mail on Sat, Nov 12, 2005: >> Quoting from Peter Church's mail on Fri, Nov 11, 2005 at 02:42:05PM -0000: >> > Like the title says :( I have tried to install this version and come up >> > with the following >> > error. I had a previous version installed however I deleted the old >> > binaries before I started... >> > >> > bash-3.00# make install >> >> ... >> >> > test -z "" || /bin/sh ./mkinstalldirs "" >> > ./install-sh -c -m 644 'fetchmailconf.py' '/fetchmailconf.py' >> >> It is installing fetchmailconf.py on the root directory! This means >> that pythondir and/or pyexecdir are not set correctly. >> >> > ./py-compile: Missing argument to --basedir. >> > *** Error code 1 >> >> Could you run these commands and tell the output? > > If python is missing, "make install" gives the above errors. It seems > that the configure script accepts a missing python, but the Makefile > generated by configure cannot cope with a missing python. *blush* OK, let's work around automake then. > This patch now avoids installing fetchmailconf* if python is missing. Thank you. > To check the patch, python needs to be removed from the system first > as there is no configure option to disable checking the location of > python. No need to mess with the installation - you can just run this: ./configure PYTHON=: [other options here] -- Matthias Andree |
|
From: Sunil S. <sh...@bo...> - 2005-11-19 12:15:43
|
Quoting from Sunil Shetye's mail on Sat, Nov 12, 2005: > Quoting from Peter Church's mail on Fri, Nov 11, 2005 at 02:42:05PM -0000: > > Like the title says :( I have tried to install this version and come up > > with the following > > error. I had a previous version installed however I deleted the old > > binaries before I started... > > > > bash-3.00# make install > > ... > > > test -z "" || /bin/sh ./mkinstalldirs "" > > ./install-sh -c -m 644 'fetchmailconf.py' '/fetchmailconf.py' > > It is installing fetchmailconf.py on the root directory! This means > that pythondir and/or pyexecdir are not set correctly. > > > ./py-compile: Missing argument to --basedir. > > *** Error code 1 > > Could you run these commands and tell the output? If python is missing, "make install" gives the above errors. It seems that the configure script accepts a missing python, but the Makefile generated by configure cannot cope with a missing python. This patch now avoids installing fetchmailconf* if python is missing. This patch also fixes specgen.sh to handle the missing python. If python is missing, with_python should be set to 0 manually and the spec file should work. The spec file has been cleaned up too. To check the patch, python needs to be removed from the system first as there is no configure option to disable checking the location of python. -- Sunil Shetye. |
|
From: Translation P. R. <tra...@ir...> - 2005-11-18 21:53:16
|
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 Albanian 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/sq.po The file should soon be made available in mirror sites as: > ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/sq.po > http://translation.sf.net/maint/fetchmail/sq.po > ftp://tiger.informatik.hu-berlin.de/pub/po/maint/fetchmail/sq.po This file has already been sent to you separately on 2005-11-18, as a MIME invoice unpacking the file `fetchmail-6.2.9-rc9.sq.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... |
|
From: Translation P. R. <tra...@ir...> - 2005-11-18 21:03:18
|
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-18, as a MIME invoice unpacking the file `fetchmail-6.2.9-rc9.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... |
|
From: Translation P. R. <tra...@ir...> - 2005-11-18 20:45:33
|
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-rc9.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-rc9.pot > http://translation.sf.net/domains/POT/fetchmail-6.2.9-rc9.pot > ftp://tiger.informatik.hu-berlin.de/pub/po/domains/POT/fetchmail-6.2.9-rc9.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-rc9.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... |
|
From: Matthias A. <mat...@gm...> - 2005-11-18 03:10:46
|
"Narendra" <nam...@os...> writes: > Dear fetchmail, > > I got a problem when i try to download mail from yahoo pop server(pop.mail.yahoo.com) > > I'm able to connect to pop server and after that the server is accepting user name. But when i sumit password it is responding with -ERR > command. [longish description of some personal Python code problem] > i'm giving the code here. Could anyone please let me know the problem > and how to solve that. Have you tried reading http://mail.yahoo.com, as it suggests: > " poplib.error_proto: -ERR Error logging in. Please visit http://mail.yahoo.com" Beyond that, problems with your personal code are outside the scope of the fetchmail mailing lists. Please go to the right place. (fetchmail is a C program/standalone application to retrieve and pass on mail and has little to do with Python). -- Matthias Andree |
|
From: Matthias A. <mat...@gm...> - 2005-11-18 03:05:21
|
Translation Project Robot <tra...@ir...> writes: > 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 > Albanian 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/sq.po Excellent, at least one of the translations is back on track. Happy day. :-) -- Matthias Andree |
147 messages has been excluded from this view by a project administrator.
