The Friday 2004-01-23 at 08:39 -0800, Wojtek Malinski wrote:
OK. I check /etc/fetchmailrc and removed all the entries. Now I only have ~/.fetchmailrc and start it locally. my ~/.fetchmailrc for yahoo looks following: set postmaster "wojtek" set bouncemail set no spambounce set properties ""
I use also "set syslog", so that logs go to /var/log/mail
poll pop.mail.yahoo.com with proto POP3 user 'wmalinski' there with password 'mypasswd' is 'wojtek' here options fetchall
Ah. If there are problems during the download and it gets interrupted, everything will get downloaded again (fetchall).
when I run fetchmail from fechmailconf I got following for one of my mails:
From fetchmailconf? Why not call fetchmail -v directly?
#*****************************.**********************************.*****************************.*************************.*********fetchmail: SMTP>. (EOM) fetchmail: SMTP< 250 Ok: queued as 5C965187B5 flushed fetchmail: POP3> DELE 375 fetchmail: POP3< +OK message 375 marked deleted
Notice that: marked deleted. Not deleted, but marked - this is correct.
yet the mails are still not deleated from the yahoo server!!!
Right. There is nothing wrong so far... but. What happens is that if there is a network problem of any sort and the process is interrupted before this part of the sequence, that you have not pasted: |fetchmail[8262]: POP3> QUIT |fetchmail[8262]: POP3< +OK POP3 server closing connection |fetchmail[8262]: 6.2.1 querying pop.tiscali.es (protocol POP3) at Tue Jan | 20 03:04:29 2004: poll completed Ok. What I saying...? Ah, that if the command "QUIT" is not sent to the server, nothing gets actually deleted! And that is the correct procedure, it is defined so for POP3 protocol. So... what can you do? 0) Use IMAP instead - possibly not possible :-p 1) Reduce risks. Use this configuration instead: |poll pop.mail.yahoo.com with proto POP3 | user 'wmalinski' there with password 'mypasswd' is 'wojtek' here options fetchlimit 75 andfetchall This will make fetchmail close the connection after just 75 mails were downloaded (you can increase the number if your download is fast), and will leave the rest till next round. If you started the program in daemon mode, it will poll again at the predetermined time; for example: fetchmail -v --limit 200000 --daemon 300 That will poll every 300 seconds, and will leave on the server any email bigger than 200000 bytes - the last limit is something I need to do, you might not. 2) Don't use 'fetchall' Risky, but useful sometimes. In any case, put a limit per poll, as stated above. I found some times that fetchmail balks at a bad header, aborts the download, and will fetch every thing the next time. If that is the case, remove the "fetchall" from the config, and try again. After you empty the server, put again "fetchall": the problems is that some mails would remain on the server (even if they were downloaded), and fill up your remote account, which is limited. 3) If the problem is, as I said above, an email that is stuck because of a wrong header, log in to the mail server using the web account, and delete that single message that is stuck - after reading it - or download it using Mozilla, for example. Mozilla uses mbox format, so that mail got that way can be moved elsewhere on your system later.
If anyone has any idea what should I try next please help.
I think those are enough ideas for a night ;-) -- Cheers, Carlos Robinson