On Tue, 2005-02-01 at 08:12, Craig White wrote:
On Mon, 2005-01-31 at 15:50 -0800, Richard E Miles wrote:
> On Mon, 31 Jan 2005 14:27:08 -0500 (EST)
> Craig White wrote:
> > Any suggestions? Right now, it is only 1 email but these things have a
> > way of snowballing.
> >
> > TIA
>
> You might want to check if you are getting socket errors in your fetchmail. It
> will cause messages to repeat in your mail. I experienced this from my
> fetchmail. To fix it I changed fetchmailrc to include logging and expunge 1 to
> erase mail from my server. here is a copy of my .fetchmailrc file.
>
> # Configuration created Sun Jul 11 10:36:42 2004 by fetchmailconf
> set postmaster "rmiles"
> set bouncemail
> set no spambounce
> set properties ""
> set daemon 90
>
> set no syslog
>
> set logfile /home/rmiles/fetchmail.log
> poll
mail.comcast.net with proto POP3
> user 'r.godzilla' there with password 'xxxx' is
'rmiles' here
>
> expunge 1
----
hmmm...
expunge 1 is interesting - I finally resorted to doing 25 at a time.
Note that essentially you're telling fethmail to break down the comm
process after each mail retrieved. This will be a huge load on your
server.
But this is handy when the link is flaky, and you can avoid
re-downloading the same mail over and over again.
wonder whether 'expunge 1' or 'batchlimit 25' is more
efficient.
Depends on your link I would say. I normally don't limit it at all. In
the office Lan, I just fire away and all 900+ emails gets DL'ed into my
laptop
--
Ow Mun Heng
Gentoo/Linux on DELL D600 1.4Ghz
98% Microsoft(tm) Free!!
Neuromancer 18:42:40 up 10:06, 8 users,
load average: 0.71, 0.52, 0.83