this problem.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
part is the broken one and reassign this bug
there. When reassigning, please remove the tags I have set on this bug.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
(or that your upstream is using).
Kind regards,
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
not currently see, it should at least be
recommends. Please change the dependencies accordingly.
Thanks,
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
. It took a long time
for sourceforge to verify my sender address and accept the announcement,
much longer indeed than was desirable.
Sorry!
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/_darcs/patches/20050511150108-86b8a-64ee7b7e15fb0b500b70f6dcafc20983e02e2c3d.gz
| gunzip -c | more
HTH,
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
a 1.10.8 or newer
fetchnews, please send a few of them to me. Thanks.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
. Should we figure that it's a
situation leafnode cannot resolve, for instance Nikolaus' Gnus issued
LIST ACTIVE * or such unspecific commands, we can still demote this to
a wishlist, or better copy the relevant info to a new wishlist item and
close this bug as invalid.
--
Matthias Andree
/ was a variant of
http://lists.berlios.de/pipermail/fetchmail-devel/2005-December/000585.html
that left the curly braces in fetchmail. It may not qualify as the
minimum fix though.
--
Matthias Andree
added? If
not, there's no reason to close the bug, unless the spare time situation
of the current co-maintainers has improved considerably.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
information,
exact information how to reproduce a problem, and in the case of a
crash, for a backtrace too, or at least strace.
It's impossible to debug this.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Why not just use --silent to get rid of these messages?
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
questions.
Regards,
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
upstream bugs with upstream, else I may not see them.
Merci d'avance.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
of descriptors left in limbo.
Is there a bullet-proof way to reproduce the socket leak? Could you try
6.3.1-pre1 from http://home.pages.de/~mandree/fetchmail/ to see if the
problem is fixed in that version?
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
.
--
Matthias Andree
--- ./transact.c.orig 2005-11-12 13:44:39.0 +0100
+++ ./transact.c 2005-12-19 00:20:05.0 +0100
@@ -401,16 +401,14 @@
* condition the code for sending bouncemail will actually look
* at the freed storage and coredump...
*/
-if (msgblk.headers
John,
Thank you for your efforts.
Please try if the attached patch fixes the bug. It is taken from a
6.2.9-pre* release. AFAIR, the patch was sent by Goswin von Brederlow.
--
Matthias Andree
--- driver.c (Revision 4126)
+++ driver.c (Revision 4127)
@@ -1161,5 +1161,5 @@
report(stderr
Hi,
is anyone of the original bug reporters using SSL to fetch mail?
If so, please check if your errors are preceded by SSL connection failures.
These are known to leak sockets, which may cause socket errors subsequently.
Thanks,
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Martin Schulze wrote:
The patch does not apply though, since xfree() is unknown in version 6.2.5.
I assume that the xfree only frees the memory when it is not NULL and sets
the variable to NULL again, so the attached patch should do the same and apply
to the version in Debian sarge/etch/sid.
Does the problem also affect 6.2.9-rc7?
See http://developer.berlios.de/projects/fetchmail/
Please test 6.2.9-rc7 and post your findings.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
severity 338007 wishlist
retitle 338007 fetchmail: handle IMAP servers that send crap after header better
thanks
On Wed, 09 Nov 2005, Nathaniel W. Turner wrote:
On Monday 07 November 2005 08:27 pm, Matthias Andree wrote:
Does the problem also affect 6.2.9-rc7?
Yes, I see the same problem
fixed in upcoming fetchmail 6.2.9-rc8
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
is near
end-of-life and a new release will only be made in case a security or
critical bug is found.
Debian packagers, please try the attached patch for 6.2.*.
Kind regards,
--
Matthias Andree
Index: fetchmailconf.py
Danni,
does the truncation happen in the body exclusively, or sometimes in the header,
too?
What is the most recent fetchmail version that you have observed this problem
with?
Thank you,
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
Dan,
what destination are you forwarding to, --mda, SMTP, LMTP or --bsmtp?
Can you show your configuration file? (Mask the passwords.)
Thank you.
Current fetchmail versions should re-fetch the message in the next poll
cycle.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
For lack of user feedback, I'm reassigning this bug to courier-imap.
Please check if this is a courier-IMAP upstream bug and if it is,
forward and tag as appropriate.
Thank you.
Matthias Andree
fetchmail upstream maintainer team
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
, although the MX
lookup code is still IPv4-only.
HTH,
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Please retest if this bug persists in fetchmail 6.2.9-rc6. We have had
two bug fixes WRT RECENT counting since 6.2.5.2.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
) {
+ if (count 0)
+ count --;
+ }
+ }
else if (strstr(buf, PREAUTH))
preauth = TRUE;
/*
--
Matthias Andree
--- ./imap.c.orig 2003-10-15 21:17:41.0 +0200
+++ ./imap.c2005-10-29 15:19:58.0 +0200
@@ -105,6 +105,15
...as though you'd upload a new upstream release for stable.
Please fix this in the 6.2.5 packages as well.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
;
echo -e A3 fetch 1234 body.PEEK[TEXT]\nA4 logout ) \
| openssl s_client -quiet -connect imap.web.de:993
Please report this bug to web.de and have them fix their junk software,
and post their response here.
Kind Regards,
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
severity 322683 wishlist
stop
This is a server problem, not a fetchmail bug.
I'll consider this as a wishlist item to work around such server bugs.
--
Matthias Andree [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
the output of fetchmail -vv and send a followup to
[EMAIL PROTECTED]
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
a stack backtrace so we can see where exactly the software crashes.
http://leafnode.sourceforge.net/doc_en/FAQ.html#backtrace
Alternatively, please see if 6.2.9-rc6 (or newer) still has a problem
fetching your mail and follow up with what you have found.
--
Matthias Andree
--
To UNSUBSCRIBE, email
tags 166899 + moreinfo
stop
Does the problem persist with a 6.2.5 version?
If yes, please provide details (fetchmail -vv).
If not, please follow up to [EMAIL PROTECTED] .
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
how about killall -STOP fetchmail?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
) to a FQDN.
Please fix this (perhaps a line in /etc/hosts is sufficient) and see if
that fixes your problem.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/fetchmail.man
and after download, you can format and read it with this command:
nroff -t -man fetchmail.man | ${PAGER-less}
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Can you please show a fetchmail -vv dump of such a session that causes
duplicate mail to appear? (For POP3, the uidl option might help.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
FYI: 6.2.9-rc7 still has this problem, but it will work if krb5-config is
on the PATH somewhere and --with-kerberos5 is used without path.
Perhaps this information can be used to update build instructions within
Debian.
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
I am attaching a revised version of the patch that doesn't count down on
the EXPUNGE OK lines.
--
Matthias Andree
Index: imap.c
===
--- imap.c (revision 4423)
+++ imap.c (working copy)
@@ -57,72 +57,85
---
leafnode-SA-2005:02.fetchnews-hangs-on-header
Topic: potential denial of service in leafnode
Announcement: leafnode-SA-2005:02
Author: Matthias Andree
Version:1.00
Announced: 2005-06-08
Category: main
Type
.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Is hiding the password in the input really useful if it's written
to the configuration in clear text?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
be reproduced on systems where
/etc/resolv.conf is a dummy (for instance, on systems with just a
modem) when fetchmail is started.
--
Matthias Andree
Index: NEWS
===
--- NEWS(revision 4981)
+++ NEWS(working copy
-safe, although IEEE Std
1003.1 mandates so.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Insufficient information to debug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
recovered from.)
Indeed fixed since. If there's still a problem, which I'm not going to
rule out right now, there'll need to be more logs. Please also check the
full log for signs of timeouts, signals and thereabouts.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
lock recovery isn't very bright, if any process has taken the PID
recorded in the file, fetchmail assumes it were running.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
in name resolution
either.
And this happens on FreeBSD 6.2-PRERELEASE i686, a fully patched Solaris
8/SPARC, SUSE Linux 9.2 i686, 10.0 i686, NetBSD 3.1 i386 - so taking the
patch upstream would make matters worse.
--
Matthias Andree
#include sys/socket.h
#include netdb.h
#include stdlib.h
#include
the name set
with --user.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Matthias Andree [EMAIL PROTECTED] writes:
Jorgen Schaefer [EMAIL PROTECTED] writes:
Package: fetchmail
Version: 6.3.6~rc3-1
I'm using fetchmail to get mails from an IMAP mailbox protected by SSL.
The configuration I use did not change at all, but since the last
upgrade, fetchmail gives
?
--
Matthias Andree
the fix.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The fetchmail configuration in itself is OK.
My standard recommendation however is to add uidl after pop3,
does this help as a workaround?
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Clemens Buchacher schrieb:
I see. If there is a connection, the request succeeds:
[EMAIL PROTECTED]:~/tmp$ ./gaitest
success, trying to free stuff.
Your name server is broken. I'm requesting a guaranteed-to-be-invalid
DNS name, there should not be success.
This is what I get, when no
Clemens Buchacher schrieb:
I wonder how your patch can then work without crashing fetchmail. Strange...
Not so. I don't know about the original fetchmail code, but the fetchmail
Debian package provides its own implementation of getaddrinfo.
Where and how does it do that?
--
To
linking with -lresolv according to my resolver(3)
manpage (SUSE 10.0 though, not Debian). This will be the case as long as
res_search is only in libresolv, but not in libc - just as a hint for
the packagers (Nico, Héctor).
Thank you for your information though.
--
Matthias Andree
--
To UNSUBSCRIBE
number.
Merci d'avance.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.
Any ideas ? It looks like it might be linked to #294547.
Please show -vv or -vvv logs.
We need to know what exactly is failing in order to debug and fix this.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
tag 329760 fixed-upstream
thanks
I have just fixed this bug in leafnode CVS, the fix will
appear in leafnode 1.11.5 which I am going to release
before end of February 2006, no release date is set yet.
As a workaround for 1.11.4 and before, comment out the
noactive configuration line.
Matthias
.
I've in fact already removed it from the upstream SVN.
Kind regards,
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
stupid). Please test and report.
Kind regards,
--
Matthias Andree
Index: NEWS
===
--- NEWS (revision 4651)
+++ NEWS (revision 4652)
@@ -60,6 +60,9 @@
* Add missing --help text for --sslcertck option. Matthias Andree
Turns out we need a 2nd patch to fix a 2nd occurrence of this bug.
This patch goes on top of the previous.
--
Matthias Andree
Index: sink.c
===
--- sink.c (Revision 4654)
+++ sink.c (Revision 4655)
@@ -934,7 +934,7 @@
transient
This bug is tracked by MITRE's CVE database as
CVE-2006-0321.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
the UIDs at the
client side, which will remove the --fetchall requirement and make
--keep sufficient. We'll then see the fix of this bug, too.
(tagging this bug upstream confirmed patch and cloning it as a
wishlist item for 6.4)
--
Matthias Andree
Index: NEWS
Google use nonstandard protocols = unsupported.
See http://www.fetchmail.info/fetchmail-FAQ.html#I9
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
*remove* mail INBOX:
Please try the attached patch and let me know if it helps.
--
Matthias Andree
Index: driver.c
===
--- driver.c (Revision 5220)
+++ driver.c (Arbeitskopie)
@@ -1324,7 +1324,7 @@
report(stdout, GT_(Polling %s
.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
such mail at least from localhost and/or via local
loopback interface
2 - use an MDA and bypass Exim and all the filtering it might do.
I'd suggest to close this bug (it's a WONTFIX for me) and check #471283
regularly.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
I suspect that some upstream server is known by the domain-local alias
or hostname news (as in: hostname = news; domain = some-uni.example)
and mistakes the user part for a hostname, rejecting alleged duplicates.
Whatever the reason, assuming that the Path has tracing, not routing,
functionality,
the blame
on the offending DFN server...
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.X has never supported client-side IPv6.
It would be nice to have a version of leafnode that is aware of modern
internet technology and that enables me to retrieve my news via IPv6.
leafnode 1.10.X is feature frozen.
- --
Matthias Andree
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU
behavior and needs to be fixed. Please file a bug report against glibc.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
().
This violates POSIX. Leafnode will not support this. How would I turn
this on under Linux? resolv.conf(5), host.conf(5) aren't helpful and
contain neither inet6 nor v6 (case insensitively).
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
. leafnode-1.10 will not support IPv6 on the client side.
4. leafnode-2 already has client-side IPv6 support.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
posted article the word article should be singlar:
news.server.com: 1 article posted.
It's trivial to fix at the same time, so 1.11.1 will repair this.
Thank you for the report.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
to transport binaries is near
zero. There are other protocols that are suited better to transport
binaries, among them HTTP/1.1, FTP, SFTP, BitTorrent, Gnutella, to name
the first that come to mind.
Consider this a wontfix.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
]);
requested_body = FALSE;
--
Matthias Andree
Matthias Andree [EMAIL PROTECTED] writes:
leafnode-1.11.0rc1 with fetchnews IPv6 support has been released, it is
available from http://home.pages.de/~mandree/leafnode/. No other
relevant changes have been made.
BTW, as some users never read manuals: you need to use
./configure --with-ipv6
with
your operating system and version (for example: Fedora Core 3, FreeBSD
5.3, Solaris 10) and your machine/CPU type (for example: SPARCv9, ix86)
Testing is not supposed to be limited to the systems mentioned!
Thanks in advance,
- --
Matthias Andree
-BEGIN PGP SIGNATURE-
Version: GnuPG
.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The attached patch should fix this issue.
--
Matthias Andree
Index: socket.c
===
--- socket.c(Revision 4993)
+++ socket.c(Revision 4994)
@@ -942,7 +942,7 @@
if( !mycert )
mycert
Please retry with 6.3.5 or newer and see if that solves the problem.
Fetchmail 6.3.5 dropped use of SIGPIPE altogether and ignores this
signal. Instead, it will rely on EPIPE to be asserted and rely on its
error handling.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
to work around the problem
in the fetchmail configuration (try via... or something, untested
however), then he should use ignore.d.server/local-* or
violations.ignore.d/local-* files.
The distribution should not suppress messages reporting possible
intrusion or eavesdropping.
--
Matthias Andree
. Still, thank you for forwarding the report and the
suggested fix.
BTW, has anyone ever used BSMTP? It failed for me with PS_SOCKET after
writing the first header, no matter if I used IMAP or POP3 with --all.
The attached patch should fix that as well. (First hunk.)
--
Matthias Andree
Index
, the second line should
have read something like 2 msgs, each 269542 octets long, skipped by
fetchmail - at least that's what it means.
In conclusion, the assertion not a bug is sort of incorrect.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
: it could on some servers, at additional download time, if
someone had written the code.
Sorry, perhaps in a later release.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
elment with size N :).
Indeed. Unfortunately my and Reto's research of this bug that I, too,
found when testing the BSMTP SIGSEGV fix overlapped.
Anyways, patch attached.
--
Matthias Andree
Index: sink.c
===
--- sink.c (Revision 5070
Vaclav,
this needs more information, particularly information on the timing.
Please re-run your command with --syslog enabled and extract the
fetchmail logging from your mail log.
Thanks.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
interval.
Fetchmail 6.3.8 makes this clear by writing 1 message, 2 messages,
5 messages... and thereabouts.
This alone doesn't look like a bug to me at any rate.
HTH,
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
This message only appears with plenty of -v options, which is probably
what the debug-run init script parameter does. Not something that's
going to be changed in the upstream code. If you don't like debugging
output, don't request it.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL
.
Unfortunately, restarting fetchmail does not help. It is as if I never
had more than 9 e-mails.
http://www.fetchmail.info/fetchmail-FAQ.html#G3 (you don't need to state
the obvious or what you've already given) - configuration matters though.
--
Matthias Andree
--
To UNSUBSCRIBE, email
The attached patch should fix this bug, which happens when the CAPA
probe fails.
--
Matthias Andree
Index: pop3.c
===
--- pop3.c (Revision 5108)
+++ pop3.c (Revision 5109)
@@ -449,7 +449,7 @@
report
if it's an
alias and (2) either install the root certificate or use --sslfingerprint.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
).
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sa, 16 Jul 2005, Jan Wagemakers wrote:
| Jul 16 19:51:41 qwerty fetchnews[24124]: STAT [EMAIL PROTECTED]
| Jul 16 19:56:41 qwerty fetchnews[24124]: (ERROR: timeout - no response
in 300 s)
| Jul 16 19:56:41 qwerty fetchnews[24124]: error: NNTP server went away
(server disconnect or
.
The implementation in SVN, post 6.2.6-pre4, was changed so that it
matches the existing documentation. The next release, -pre5, will carry
the bugfix.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Mon, 18 Jul 2005, Jan Wagemakers wrote:
Matthias Andree [EMAIL PROTECTED] schreef:
| Jul 16 19:51:41 qwerty fetchnews[24124]: STAT [EMAIL PROTECTED]
| Jul 16 19:56:41 qwerty fetchnews[24124]: (ERROR: timeout - no
response in 300 s)
| Jul 16 19:56:41 qwerty fetchnews[24124
1 - 100 of 273 matches
Mail list logo
