Matthias Andree wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Helge Hafting wrote:
Still, rejecting on TO address is tricky, mailing list mail is usually not
addressed to me.
Unfortunately, you haven't shown your configuration file yet.
I suspect you're using a wildcarded mult
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Helge Hafting wrote:
> Still, rejecting on TO address is tricky, mailing list mail is usually not
> addressed to me.
Unfortunately, you haven't shown your configuration file yet.
I suspect you're using a wildcarded multidrop configuration.
- --
Matt
Matthias Andree wrote:
(demoting to serious, tagging upstream, retitling)
Additional info:
fetchmail 6.3.4 and older do NOT log out of the upstream server after
SIGPIPE (I don't know the rationale behind this - it's not in the
comments), which prevents the deletions from happening properly.
Ret
(demoting to serious, tagging upstream, retitling)
Additional info:
fetchmail 6.3.4 and older do NOT log out of the upstream server after
SIGPIPE (I don't know the rationale behind this - it's not in the
comments), which prevents the deletions from happening properly.
Retitling the bug accordingl
Well, Exim's error before it just drops the connection isn't selling
fetchmail a hint that there's no progress beyond that point.
The question is: why does fetchmail not skip over the offending
messages? It may or may not try to bounce them, depending on your
configuration, but should mark them re
Package: fetchmail
Version: 6.3.4-4
Severity: grave
Justification: renders package unusable
I have been using fetchmail for many years - it runs every 10 minutes
fetching from a few accounts. The mail is then fed into a local
exim, because I used to have several users on this machine.
Yesterday,
6 matches
Mail list logo
