Does this warrant "grave"?
This looks like trying to configure fetchmailconf before fetchmail is
configured, and before fetchmail saw configuration. However why is
fetchmail being "restart"ed? It could not have been running before...
Am 30.03.21 um 09:04 schrieb dk8kk:
> Package: fetchmailconf
> Version: 6.4.0~beta4-3+deb10u1
> Severity: grave
> Tags: a11y
> Justification: renders package unusable
>
> Dear Maintainer,
>
> apt-get update/apt-get upgrade suggests these package for upgrade:
> - fetchmail (6.4.0~beta4-3+deb10u1)
>
Control: tags -1 upstream fixed-upstream confirmed
Control: severity -1 grave
Christian, thanks for the report. It is a known issue that happens with
fortifying compilers.
Please use either the former rc3, rc4 or the upcoming 6.4.1. László
(gcs@) is aware of it.
Control: tags -1 confirmed upstream fixed-upstream -moreinfo -unreproducible
This got fixed in upstream Git as of commit
8c57ec38ae327fcd648569acc915f47f0eb2547d - please cherry-pick this.
https://gitlab.com/fetchmail/fetchmail/commit/8c57ec38ae327fcd648569acc915f47f0eb2547d
Generally, a POP3 DELE becomes effective only with the following QUIT that
completes the session, so the server is compliant.
I shall have a look at the stack and valgrind traces later to see if I can find
the cause.
Am 15.11.2015 um 06:00 schrieb peter green:
> Tags 804604 +patch
> thanks
>
>> socket.o: In function `SSLOpen':
>> /fetchmail-6.3.26/socket.c:917: undefined reference to
>> `SSLv3_client_method'
>> collect2: error: ld returned 1 exit status
>> Makefile:699: recipe for target 'fetchmail' failed
>>
Am 16.01.2015 um 01:24 schrieb Debian Bug Tracking System:
Processing control commands:
tags -1 + experimental
Bug #775255 [fetchmail] fetchmail: Fails to start when libssl has SSLv3
disabled
Added tag(s) experimental.
IMO this is an error from the shell and the dynamic run-time linker,
Am 29.04.2013 09:28, schrieb Tomas Pospisek:
To be specific:
1436: SockRead(sock, inbufp, sizeof(buf)-4-(inbufp-buf)))
This can not overflow.
1467: inbufp[len++] = '\r';
Can overflow if inbufp[len] outside of 'buf'. Can we prove that
inbufp[len] does not
Am 28.04.2013 18:28, schrieb Adam D. Barratt:
Indeed. From the release perspective, however, the question we're
concerned with is whether the issue is severe enough that it /must/ be
fixed before the release.
If it only occurs when a non-default option is used and has affected
fetchmail
Am 28.04.2013 09:07, schrieb Tomas Pospisek:
I have had a look at the patch and as an outsider to the fetchmail code
that is not a maintaner of fetchmail am personaly not comfortable with
it. The problem is that the patched code in question is allready twisted
enough, it's in very large part
Package: fetchmail
Version: 6.3.18-2
Severity: grave
Tags: upstream confirmed fixed-upstream
Control: found 6.3.9~rc2-4+lenny2
Control: found 6.3.21-4
Control: found 6.3.22-2
The bug report included below was filed against Ubuntu, it is an
upstream bug that also affects Debian.
It was originally
XREF Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=955814
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
/fetchmail/+bug/684228
But it is not to be expected that Ubuntu will see to those in the near future.
--
Matthias Andree
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
call, however, _does_ yield the proper path (dist-packages), then
check the build scripts where it gets overridden, if there are siteconfig files
for autoconf, or config.caches where a wrong pythondir might get picked up.
HTH
--
Matthias Andree
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ
retitle 578956 fetchmail drops messages with non-header lines in header section
severity 578956 wishlist
tags 578956 fixed-upstream
found 578956 6.3.6-1etch1
found 578956 6.3.6-1etch2
found 578956 6.3.6-1etch3
found 578956 6.3.9~rc2
found 578956 6.3.9~rc2-4+lenny1
found 578956 6.3.9~rc2-4+lenny2
Nico Golde [EMAIL PROTECTED] writes:
there is a problem with upstream ja.po localization file,
please fix it :)
Not a problem with that file, but with gettext 0.15 :-P
Use the attached patch.
--
Matthias Andree
Index: po/ja.po
.
- --
Matthias Andree
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFE7PeCvmGDOQUufZURAs01AJ9Ax9kCN59Q4rubF11/FMz6qhcb4wCgunuy
3xWJnpbHy+CPt6h7Q7ookc0=
=hZJE
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
refused - as seen in ..flushed.
But what exactly happens is a matter of your configuration.
Please show your fetchmailrc file and the output of
/etc/init.d/fetchmail debug-run
up to the error.
Remember to restart fetchmail afterwards with /etc/init.d/fetchmail start
--
Matthias Andree
/serious severities.
--
Matthias Andree
--- ./fetchmail.c.orig 2006-08-21 01:39:54.0 +0200
+++ ./fetchmail.c 2006-08-21 01:37:47.0 +0200
@@ -577,7 +577,7 @@
set_signal_handler(SIGINT, terminate_run);
set_signal_handler(SIGTERM, terminate_run);
set_signal_handler
---
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
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
/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 to [EMAIL PROTECTED
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 [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
]);
requested_body = FALSE;
--
Matthias Andree
24 matches
Mail list logo
