|
From: Rob M. <rob...@gm...> - 2007-02-03 20:46:18
|
Please don't top post.
On 2/3/07, Otto Rodusek (AP-SGP) <ot...@ap...> wrote:
>
> 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.
The problem is that YOUR local SMTP server is returning a temporary
delivery failure so fetchmail is keeping the email. You can either:
a) Get your ISP to not accept email from unresolvable domains (which
no ISP ever should)
b) Switch ISP to one with a clue
c) Configure your local SMTP server to provide a permanent delivery
failure on DNS lookup failures, which risks losing email
d) Configure fetchmail with the 451 code as an anti-spam code, and
risk losing email
--
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
|