From: Otto R. (AP-SGP) <ot...@ap...> - 2007-02-03 01:31:38
|
Hi Matthias, Thanks for your reply. From your reply, it would imply that fetchmail would flush or delete these email - however it doesn't. After about a month, I'll have quite a number of these mails on the ISP's server and on each fetchmail run (it runs ever 10 minutes in cron) i would see a lot of these SAME unflushed emails (as per the log on on first email). Am I using the wrong parameter or am I missing a parameter? I am willing to take the risk and consequences if there is a parameter in fetchmail that will FORCE-DELETE or FLUSH these emails. I ran my fetchmail manually and it download 58 emails of which 9 were faulty and not flushed (as per the log). I then ran fetchmail again within seconds of the first on finishing and indeed there were only 9 messages on the server and again it did not flush. I then ran fetchmail again for a third time within seconds of the second run, and the same 9 messages were still on the server - i just couldn't get fetchmail to "flush" or delete these emails. Any help is much appreciated. Rgds. Otto. Matthias Andree wrote: > Otto Rodusek schrieb am 2007-02-02: > > >> I am doing a fetchmail from my ISP to my local server with the following >> command: >> >> fetchmail -K -F -f /menu/fetchmailrc where fetchmailrc is >> >> poll mail.sg.gs protocol pop3 username ro...@aa... password SECRET to >> ro...@aa... >> >> My ISP's email server is using QMAIL. >> > > The qmail pop server has been known for a while to miscalculate message > lenghts, violating RFC-1939, but you can't bother DJB to fix this... > http://home.pages.de/~mandree/qmail-bugs.html section 3.4 > > >> Fetchmail works just fine, however often times it DOES NOT delete the read >> message on the ISP's side (in each case it is definitely a JUNK mails) as >> per the log file below. I understand the problem and I have read the part >> about fetchmail/qmail however - >> > > Tell the ISP not to accept junk mail. > > >> IS ther ANY WAY for have fetchmail FORCE-DELETE these emails of the ISP >> server?? >> > > Yes, but as Rob correctly states, that way would endanger your > legitimate mail. > > >> fetchmail: SMTP> MAIL FROM:<egt...@sc...> >> fetchmail: SMTP< 451 DNS temporary failure (#4.3.0) >> > > DNS problem or the upstream should not accept messages from unresolvable > domains. This prevents flushing your messages. > > >> fetchmail: SMTP> RSET >> fetchmail: SMTP< 250 flushed >> fetchmail: message ro...@aa....@mail.sg.gs:3 was not the expected length >> (17967 actual != 17679 expected) >> > > Not related to your problem (fetchmail only reports this for your > information, but it's nothing more; fetchmail pretends this problem > hadn't existed after it's reported it.) > > |