Folks -

The recent rash of virus-laden emails has brought up a previously
unforeseen problem on my system.

I use fetchmail(6.2.3) to grab mail from a remote POP server and dump it
to my local mail server(postfix 2.0.11) This weekend, I noticed that mail
wasn't moving. Certain messages led fetchmail to complain of an error
501. A little investigation showed that it was actually postfix rejecting
the mail, because one of the domains did not resolve.

The man page led me to an option, antispam 501, which is supposed to tell
fetchmail to drop a 501-rejected message completely. Theoretically, if a
501 mail is rejected by postfix, fetchmail is supposed to drop it and keep
going.

Here's the problem - after adding antispam 501 to my fetchmailrc, it now
complains of a 'client/protocol error' when fetching this mail. Now I'm a
bit lost - I don't know if the problem is postfix or sendmail.

Can anyone assist? I'd be happy with either telling postfix to stop
checking that domain, or telling fetchmail to drop that email.
Unfortunately, I'm having trouble figuring out how to do either.

fetchmailrc is included...any assistance would be highly appreciated.

set postmaster "pmgeahan"
set bouncemail
set spambounce
set properties ""
#set daemon 900
poll mail.REMOVED with proto POP3 auth cram-md5 user 'USER' there with
password 'PASS' is 'USER' here options fetchall antispam 501

poll mail.REMOVED with proto POP3 user 'USER' there with password 'PASS'
is 'USER' here options fetchall antispam 501


--
-------Patrick M Geahan----pmgeahan@thepatcave.org---ICQ:3784715------
Quote of the Week: "I probably won't start on the idea, and if I do it
will wind up being an unfinished project on my personal website featuring
pictures of my cat." rh2600 on /.

On Sun, 21 Sep 2003, Patrick M Geahan <pmgeahan-usenet@thepatcave.org> wrote:
Yes but you are overriding that by using bouncemail and spambounce options
which attempt to bounce mail your server does not accept. But most
worms and spam are either From a forged user, or possibly an invalid
address. So the protocol error is probably your server refusing to handle
the bounce because of invalid To: in the bounce message. It is silly to
bounce spam or worms because you are just propegating them to users who
did not send them (you are assisting worms and spammers).

--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/

David Efflandt <efflandt@xnet.com> wrote:

David -

I see your point.

However, removing those two lines does not stop the protocol error. I
still receive the following error message:

---
fetchmail: client/server protocol error while fetching from
mail.REMOVED
fetchmail: Query status=4 (PROTOCOL)
---

--
-------Patrick M Geahan----pmgeahan@thepatcave.org---ICQ:3784715------
Quote of the Week: "I probably won't start on the idea, and if I do it
will wind up being an unfinished project on my personal website featuring
pictures of my cat." rh2600 on /.