I'm skipping the more important stuff I don't have time to reply to for
this little topic.
Matt Kettler wrote:
True.. and writing a milter should be an expert task. I'm sorry the
milter your are using is causing you such fits, but I really don't think
it's normal for the average end-user to have to hack up their milters to
make them feed SA properly. Most milters that handle SA already do this
for you, right out of the box.
Petr Rehor is the maintainer for amavisd-milter. It's the *ONLY* way
that amavis works properly in a milter config. It's incredibly standard,
and works out of the (ports) box on FreeBSD and probably most linuxes.
There are tons of people using it today. So yeah, all of the "average
end users" who are using amavis out of ports on FreeBSD, really.
Petr never put this Received header forgery bit into amavisd-milter. He
didn't know he was supposed to, not having any documentation that
mentions this. So it was broken until Daryl flagged this issue, and I
brought it up with him and Marc (of amavisd-new fame) and we realized
that expectations didn't align. He pushed out a patch in < 24 hours and
this is now fixed.
Make autodetection work out of the box for the clueless people using
it out of the box. That's your real target audience.
I'd love to, but the SA project didn't write the milter you're using,
and the problems you're having can't be "fixed" by having SpamAssassin
"detect" the problem without doing something even dumber to someone else.
Sure it can! It's dead simple to determine that the last Received
header isn't yourself and can't possibly be related to you.
--
Jo Rhett
Network/Software Engineer
Net Consonance
