Re: [fetchmail-users] message...was not the expected length...not flushed

[Rob M. <rob...@gm...>]

On 2/2/07, Otto Rodusek <ot...@ap...> wrote:
> Hi,
>
> I am using fetchmail 6.3.5-13 under Suse 10.2 (kernel  2.6.18.2-34-default).

6.3.6 came out recently, though it won't help here you should upgrade.

> 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 -
>
> IS ther ANY WAY for have fetchmail FORCE-DELETE these emails of the ISP
> server??
<---SNIP--->
> fetchmail: SMTP< 451 DNS temporary failure (#4.3.0)

That is the actual problem I suspect - a temporary DNS failure.  You
could risk using the 451 code as an anti-spam code to flush the
emails, but if you do that you risk also dropping valid email.

Fetchmail is always conservative about these things for good reason :)

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche