you should add also CHKUSER_ENABLE_NULL_SENDER.
When CHKUSER_SENDER_FORMAT or CHKUSER_SENDER_MX are defined, CHKUSER_ENABLE_NULL_SENDER will exclude NULL SENDERS from those checkings.
This is the new default in the last distributions, after CHKUSER_ENABLE_NULL_SENDER has been added:
CHKUSER_SENDER_FORMAT enabled CHKUSER_SENDER_MX enabled CHKUSER_ENABLE_NULL_SENDER enabled
Sorry, I realized too late that CHKUSER_ENABLE_NULL_SENDER_WITH_TCPREMOTEHOST feature, far from being a valid intruders rejection, has made too many troubles. I tried to fix the situation introducing CHKUSER_ENABLE_NULL_SENDER.
Let me know of any better explanation in the documentation or FAQ.
At 01.08 24/11/2004, you wrote:
On Tuesday 23 November 2004 05:30 pm, Jeremy Kitchen wrote: > On Tuesday 23 November 2004 04:53 pm, Rick Macdougall wrote: > > Jeremy Kitchen wrote: > > > mail from: <> > > > 571 sorry, sender address has invalid format (#5.7.1 - chkuser) > > > > > > HUH? > > > > > > this is fixed in a newer version I hope? > > > > Hi, > > > > Is CHKUSER_ENABLE_NULL_SENDER_WITH_TCPREMOTEHOST defined in your config ? > > > > From the manual > > > > CHKUSER_ENABLE_NULL_SENDER_WITH_TCPREMOTEHOST 2.0.5 defined > > Enables accepting null sender "<>" from hosts which have a name > > associated to their IP > > oh, and we don't do reverse dns lookups.. that would explain it. This is > on as default or something? Why is this even in chkuser? heh...
hmm.. even commenting it out it appears that I am not able to receive bounce messages. This is very bad.
-- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 815.776.9465 int'l kitchen @ #qmail #gentoo on EFnet IRC ++ scriptkitchen.com/qmail GnuPG Key ID: 481BF7E2 ++ jabber:[EMAIL PROTECTED]