Branches
Releases
|
Version
|
Focus
|
Date
|
|
6.3.9-rc2
|
Minor security fixes |
25-Jun-2008 11:43 |
|
6.2.9-rc10
|
Minor bugfixes |
28-Nov-2005 01:10 |
|
6.2.9-rc9
|
Minor bugfixes |
18-Nov-2005 07:22 |
|
6.2.9-rc8
|
Minor bugfixes |
10-Nov-2005 03:18 |
|
6.2.9-rc7
|
Minor security fixes |
31-Oct-2005 05:47 |
|
6.2.9-rc5
|
Minor bugfixes |
26-Sep-2005 02:04 |
|
6.2.9-rc4
|
Minor bugfixes |
21-Sep-2005 13:58 |
|
6.2.9-rc3
|
Minor bugfixes |
19-Sep-2005 11:49 |
|
6.2.6-pre9
|
Code cleanup |
02-Aug-2005 06:11 |
|
6.2.6-pre8
|
Major security fixes |
23-Jul-2005 23:23 |
Articles referencing this project
- Debian: New fetchmail packages fix denial of service
by Patrick Lenz
,
in Security
Sun, Sep 23rd 2007 12:18
- Red Hat: Updated fetchmail package fixes a security bug
by Patrick Lenz
,
in Security
Sun, Jun 10th 2007 07:55
- Debian: New fetchmail packages fix information disclosure
by Patrick Lenz
,
in Security
Sun, Feb 18th 2007 01:36
- Red Hat: Updated fetchmail packages fix two security issues
by Patrick Lenz
,
in Security
Mon, Feb 5th 2007 03:28
- Debian: New fetchmail packages fix denial of service
by Patrick Lenz
,
in Security
Fri, Jan 13th 2006 08:18
|
|
Comments
[»]
Behaviour I didn't expected
by WimPunk - Apr 21st 2004 07:12:11
I'm using fetchmail for a few years now and I'm very happy about that.
Recently I was doing some experiments with "poll" and
"skip" and discovered something I didn't expected.
I have two providers, provider1 and provider2. On provider1 I have a
mailbox I check with fetchmail running in deamon mode every 10minutes.
This part works fine.
On provider2 I have a mailbox I check manually. I was hoping dat
"fetchmail provider2" or "fetchmail -d0 provider2"
should be working but it didn't, I only got the mail from provider1.
The only thing that works is "fetchmail -q; fetchmail -d0 provider2;
fetchmail". So I first have to kill my deamon, get the mail and start
fetching it again.
Is there a better work around?
Btw, I'm using release 6.2.5+NTLM+SDPS+SSL+NLS from debian-sarge.
--
I haven't lost my mind, I know exactly where I left it
[reply]
[top]
[»]
Fetchmail looses mail
by Andy - Mar 19th 2004 10:11:23
Hello, I think I have found a case where fetchmail will lose mail. If
'keep' is being used to leave mail on the server and the number of messages
on the server exceeds the fetchlimit, Fetchmail retrieves up to
<fetchlimit> messages, then on the next connection ignores all of the
messages, as if they have all been retrieved, when they have not.
I am using uidl, if this makes a difference.
[reply]
[top]
[»]
Many Features except Robustness
by Gary Lawrence Murphy - Jun 6th 2002 09:54:58
First off, we depend on Fetchmail to manage incoming email from several
offsite POP/IMAP accounts that must be redistributed locally across three
machines; for shear features and ease of deployment, fetchmail is the only
game in town. But it is a major admin headache: Where incoming
mail headers are non-standard (which is frequent with spam), or when the
MDA barfs on an incoming email (which procmail often does), instead of a
graceful recovery, fetchmail unceremoniously aborts.
It has buffer overrun problems too.
When it dies, POP3 leaves all messages in the queue,; it has to complete
the run to delete the server messages --- if you've downloaded 188 of 190
and it dies, next time in, you get those same 188 messages, again and again
and again until you notice the failure.
In our experience, handling only about 1000 messages a day from 6 sources,
fetchmail fails at least two or three times a day: Keep a close watch
if you run fetchmail in daemon mode. Curiously (and fortunately)
Eric's earlier program, popclient, is far more resilient to header errors;
we use a log-watch (logplay) to monitor syslog for fetchmail failure
messages, and launch the ancient popclient to recover. We're seriously
contemplating getmail as an alternative,
but it's a beast to install.
[reply]
[top]
[»]
Re: Many Features except Robustness
by andrew cooke / jara software - Mar 7th 2003 20:34:50
I use(d) fetchmail on my own server and had the same frustrating problems
(even with relatively low mail levels it would jam every week or so).
After reading your comments (thanks!) I realised it wasn't my fault and
switched to getmail.
I'm using Debian, so installing is trivial. And it was simple to
configure - I have it running as a cron job under the mail user, piping
mail to procmail for two users (procmail filters to maildirs which are
handled by Courier imap + Squirrelmail for web access). Appears to work
fine. You should try it...
[reply]
[top]
[»]
Re: Many Features except Robustness
by Gary Lawrence Murphy - Mar 7th 2003 21:07:22
> I'm using Debian, so installing [getmail] is
> trivial. And it was simple to configure
> - I have it running as a cron job under
> the mail user, piping mail to procmail
> for two users (procmail filters to
> maildirs which are handled by Courier
> imap + Squirrelmail for web access).
> Appears to work fine. You should try
> it...
We've since learned that procmail is also problematic as it loads entire
files into memory to process just the headers (or that's what I've heard,
haven't read the code yet). In these days of large attachments, that can
seriously impact server performance, so we've been looking at a few
alternatives.
Just so you know, though, the problem is not so serious that we're
scheduling downtime to fix it ;) ... we've known about the problem for a
long long time, and yet we still run procmail. What surprises me is how
the Linux distros (Mandrake at least) still ship with these really
bad-example programs as the default configuration.
[reply]
[top]
[»]
Re: Many Features except Robustness
by andrew cooke / jara software - Mar 24th 2003 16:40:20
We've since learned that procmail is also problematic as it loads
entire files into memory to process just the headers
curiously i am back here because i just had a big success with getmail
where fetchmail failed - a message with a 5Mb attachment (compressed dbase
image). procmail handled it fine, although the machine has much more
memory, of course.
in a way, it's a privilege to be able to worry about procmail (thanks
for the tip) - it was fetchmail's inability to grab an earlier file of this
size that finally forced me to use getmail (it's always possible, of
course, that's it's a fetchmail config error on my part, but i did check
and modify config files with no success). i can also now download channel4
news (uk independent news source) email list, which fetchmail choked on
because of incorrect headers.
[reply]
[top]
[»]
HTTP support ?
by John Harrison - Nov 7th 2001 11:12:36
Fetchmail rocks, I use it on my Slack 8 box to talk to yahoo.com, exim,
InterMail and others, don't get me wrong, I love it.
I must challenge the statement under "About:" on the freshmeat
page though:
"It supports every remote-mail protocol now in use on the
Internet"
Many HotMail accounts are good for nothing but catching spam. To
process this spam to get something done about it you either have to do it
manually (ouch! if you're getting 40+ spams a day that's HARD work and lots
of dead time!)
To bulk process my spam I have to use Outlook Express to download the
mail (it supports a "HTTP Mail Protocol") and then forward them on as
attchments to one big spam mail to my Linux box to process them.
This downloading over the modem is very slow, error prone and painful.
If fetchmail supported this "HTTP Protocol" for retrieval of mail I
wouldn't have to polute my fingers with touching a Windows keyboard, I
could cron my spam harvesting, and get to bed earlier at night...
As far as I can see the tricky part to this is the https
authentication, because from there on it it appears to just be http. (I may
be wrong)
It may be a spawn of the evil empire, but it is a protocol used for
remote mail retrieval, and fetchmail doesn't currently support it.
[reply]
[top]
[»]
Very good utility ..
by dodo - Oct 14th 1999 18:56:31
Grab your new release of this powerful and friendly program.
I' ve just done it for my Slack 4.0 ;-)
Bye !
[reply]
[top]
[»]
Re: Very good utility ..
by TuKo - Apr 24th 2001 14:43:10
It's a very useful utility !
But I think it's too oftently updated (yes, sure !). I'm compiling the
sources again and again...
--
.TuKo[pASSTECH]. .wEB. tuko-box.homeip.net.
.iCQ 2123967. .zIC. www.brain-damaged.ch.
.Et meme si elle n'est rien au milieu de l'ocean, une
seule goutte peut faire deborder le vase" (Lofofora).
[reply]
[top]
[»]
fetchmail, fetchpop, qmail, etc
by Jeremy Sasser - Sep 29th 1999 14:54:16
Can anyone verify that fetchmail doesn't work with qmail? I've replaced
sendmail with qmail and then tried fetchamil/fetchmailconf and boy, it blew
up on me...I've just tried fetchpop which was in redhat 6.0 powertools...so
far it's really great (encrypted username and password) I'm surprised it's
not listed in freshmeat.net...what do you guys think of fetchpop?
[reply]
[top]
|
