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

[Otto R. (AP-SGP) <ot...@ap...>]

Hi Rob,

Thanks for the reply. I agree about the 451 error and other things about 
fetchmail being conservative. I have been monitoring the situation for 
quite some time and in EACH case it happens that the faulty emails are 
spam. So the question again is - is there ANY WAY at all to get 
fetchmail to FORCE-DELETE these emails. I'm willing to take the risk and 
have tried various parameters but to no avail (I use the -F to flush but 
as you can see from the log it doesn't. Any ideas are welcome. Thanks. 
Rgds. Otto.

Rob MacGregor wrote:
> 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 :)
>
>