causes this problem.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ur local SMTP forwards to.
Please find out which 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]
using
(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]
rong
for some reason I do 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]
fter a while, there are hundreds 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
.
--
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 su
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/si
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,
fixed in upcoming fetchmail 6.2.9-rc8
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d hostname.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [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)
@
---
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
YOU say you wanted to
be clear if help is needed? Have new (co-)maintainers been 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]
c without passwords), fetchmail -vv 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]
Goswin's and my questions.
Regards,
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
default.
Please tag all 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]
, as 6.2.X 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: fetchm
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 subje
6.3.0, 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]
eleased
one day after Steve's report.
The patch that was committed /upstream/ 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
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]
toi(buf+2) > 0) {
+ 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.c20
...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]
inbox" ;
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 [E
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". Tr
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]
ou can reproduce, please
obtain 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.
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". Troubl
how about killall -STOP fetchmail?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ur DNS setup is broken, the machine appears to be unable to
resolve its own hostname ("ip7133120") 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]
etchmail/trunk/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]
with a
609-done (append "-done") so the
bug is closed.
Thank you.
--
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]
s are set properly,
check gnus-read-active-file, it should be 'some or nil for instance.
I'm not sure if there are other variables that cause Gnus to read the
whole active file without querying groups individually.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
o Gnus v0.4, and the
recommended setting. Not sure how this relates to Debian installations,
I have none ready at the moment. I might install Sarge or Sid into Xen
some day though.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
in the FILES section for the
interesting.groups directory. I have added two more FAQ entries in this
regard, to appear in 1.11.3.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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]
.de/~mandree/leafnode/beta/darcs/_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]
ibing from ... (current time:
...): ctime age ..., mtime age ..." from your past news syslog (they are
logged at "INFO" severity) and they are from 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]
t the severity of this bug#
be bumped to "normal" for the nonce. 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 th
NLOG_CTOP, "%s: %s:%lu: article without
blank line after header, format violation",
current_server->name, g->name, stufftoget[i]);
requested_body = FALSE;
--
Matthias Andree
mail without problems,
and neither has such a nested SMTP_auth_error implementation.
Please remove from Debian all patches that break smtp.c.
--
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 disconn
BTS.
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
> >>
How would I reproduce this?
Are you using dial-on-demand?
Are you using DHCP?
Please attach strace when fetchmail loops like shown in your previous
log, say:
strace -tt -e trace=network -p $(cut -f1 -d" " ~/.fetchmail.pid)
and check particularly the connect() calls.
--
Matth
The output of "fetchmail -vv" is required to debug this.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hough).
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
<http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2335>
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e/project/showfiles.php?group_id=1824> which
contains a much simpler fix that Ludwig Nussel of SUSE Security has
provided.
I have updated the security announcement at
<http://fetchmail.berlios.de/fetchmail-SA-2005-01.txt> to version 1.01.
--
Matthias Andree
--
To UNSUBSCRIBE, email t
This bug is Debian-specific and caused by a fetchmail.c patch in
http://ftp.debian.org/debian/pool/main/f/fetchmail/fetchmail_6.2.5-14.diff.gz
The vanilla 6.2.5 version doesn't have this bug.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
I cannot reproduce this bug with vanilla 6.2.5.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
This will be fixed in 6.2.6-pre8.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
This is the same as Debian Bug#294547.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Upstream is aware of the problem, but there is insufficient information.
Please close this.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Please provide a fetchmail -vv trace to show the problem, or confirm
that the bug is fixed on sarge. I cannot reproduce this.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Just to see where the bug really is.
TIA,
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Final-Recipient: rfc822; [EMAIL PROTECTED]
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; host mx1.mail.spray.net[212.78.202.6] said: 550
<[EMAIL PROTECTED]>: Recipient address rejected: User unknown
in local recipient table (in reply to RCPT TO command)
--
Matthias
Please provide more details, for instance, the fetchmail -vv output and
the message that was received with the extra parenthesis.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Ralf,
Please retry with fetchmail-6.2.5 and state whether 6.2.5
still shows this problem or fixes it.
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186739>
Thank you.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
Please try adding a line like this to your .fetchmailrc and let me know
if it helps (yes it will report errors for obvious reasons - note that
"skip" doesn't work):
poll dummy.invalid with proto ETRN no dns
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
Christian Kurz wrote:
> fetchmail: POP3> QUIT
> fetchmail: POP3< The power and effects of Cialis stay in your body 9 TIMES
> LONGER than VlAGRA!
> fetchmail: SMTP transaction error while fetching from xxx.xxx.de
Something's gotten out of synch here, the POP3 server answered with a
line from a me
the
6.2.6-pre8 version. You may need to run fetchmail under gdb or catchsegv
supervision or valgrind if you have that.
I have a quite similar configuration (with I believe irrelevant
differences, but I haven't checked all of them), and fetchmail sends the
bounce
--
Matthias Andree
-
this. Please check your log files for errors - see
the README files for how to configure syslog.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
mpt to subscribe to it.
False. The groups are added to the groupinfo file before leafnode
attempts to download the group description. Only a premature fetchnews
crash can cause the groupinfo to be corrupt.
Check your syslog configuration (see README), perhaps restart syslogd
after reconfiguring syslog.con
can reproduce the problem with sqlite 3.2.1 on a Sun UltraSPARC running
Solaris 8 and can confirm the problem is fixed there with sqlite 3.2.2.
(I don't have access to 64-bit machines running Debian.)
Please consider updating to 3.2.2.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAI
n the case of a single
> 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 PROTE
, my sympathy for abusing NNTP 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 UNSU
some time to figure out the encoding. Nevermind.
4. If it is possible without major effort, please use UTF-8 encoding for
.po files, for consistency.
Kind regards,
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Torsten,
please re-run the bogofilter command that goes into a loop with the
-vvxdi options set, and make sure you are not accidentally discarding
debugging output. The output generated may help us isolate the problem.
Thanks.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
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]
with a
item.
--
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
le for the upstream.
It also requires 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
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
nce with "Temporary failure 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
#include
#i
CommonName and overrides 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 di
export LC_ALL
below that LC_ALL=C line?
--
Matthias Andree
t 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
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 UNSUBS
gt; folder, and then sits with the rest.
> 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 tho
says:
leafnode 1.9.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 SIGNATUR
e or actual
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]
stbyname().
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
nfiguration will be made.
3. 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]
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
./c
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
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
ut
yours first. 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 Andr
1 - 100 of 276 matches
Mail list logo
