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.
This is my .fetchmailrc
defaults
set daemon 180
set postmaster craig
set nospambounce
set nobouncemail
set logfile /home/craig/fetchmail.log
poll MY_ISPs_MAIL_SERVER
proto imap
localdomains azapple.com
user "MY_ACCOUNT"
pass "MY_PASSWORD"
batchlimit 25
it's been working for a few years. The problem was of course spamass-
milter which has now been solved.
During my switchover from uw-imap to cyrus-imapd (which included
migrating all my mail from mbox and 're-creating' my procmail rules into
sieve filters) I was 'dark' for about 1 day and there were 1377 emails
waiting for me when I felt comfortable enough to resume 'fetching' - I
wonder whether 'expunge 1' or 'batchlimit 25' is more efficient.
Craig
