fetchmail-friends
[Top] [All Lists]

Re: [fetchmail] unexpected behaviour with undeliverable mail

2002-09-04 12:45:02
Dear Eric,

Indeed, "no such user" (which is a configuration error, such as a typo
in the "user hans is andreas here" part) will yield 550 in many cases,
but this should be tested for before putting a system into production.

I was too hasty with my last reply, and rightly you criticize it.

Multidrop with wildcard can of course yield this 550 condition even
without configuration error (at least on Postfix), and some MTAs use
indeed 550 for content filter rejects as well as "no such user", so it
might be needed to add some parsing the reply message here, I'm thinking
of RFC-1893 (those codes used in Delivery Status Notifications), and/or
regexp matching (what is spam, what is not), for example.

In my last reply, I had not thought of multidrop, so I'll take that back
and herewith apologize to Andreas.

I'd second that this be changed for fetchmail 6.0.0.

Now, wait a second, Matthias.

Your response doesn't seem consistent.  First, you appear to argue
that deleting undeliverable mail is OK because there is no other
obvious fallback action.

Then you turn around and suggest that
antispam -1 ought to be the default.

I feel that no software should discard anything without _explicit_
user configuration, so the default should be -1, even though 554 and 571
look safe to me at this moment.

This is regardless of the other discussion and the discussion of
Andreas' problems. If the user wants to discard things, he should say
so. That's why I second Andreas' request to set the default to -1.

Feel free to ask further questions. Thanks for cautiously reading my
mails.

Best regards,
Matthias