(It loses the (To|Cc): qpsmtpd at perl.org, so it's really annoying to reply to.)
That's a carbon-based error (i.e. /I/ am deleting it). Since I am using a newsreader (and I'm not on the list), if I leave that header in, I get a warning message from the listserve software. I'll stop deleting the cc: and just ignore the warnings from now on.
Um. Not sure about this problem. My test instance doesn't seem to touch that. I hope its not something I broke.
I didn't have much time to debug it; maybe I'll get back to it on Tuesday (if there aren't any other fires to put out, like losing both T-1's to the phone switch).
I think the policy is that trunk is supposed to be always [mostly] functional. We're just um.. um... um... having different definitions of [mostly].
Yeah. It compiles without error, but it doesn't accept mail any more. ;)
Wow. I thought VRFY had been banished to the boonies around the time the spammers started doing dictionary attacks on it. Can you describe a little more what you mean by a crude hack?
I have two MX boxes which just accept the mail (and scan it for viruses), then pass it on to the actual mail server (where the virtual domains and users reside). Rather than replicating the database, or having the database available via any public (i.e. non-loopback address), I have the remote MX boxes using VRFY to validate the addresses they accept.
My code permits VRFY only from specified IP addresses/blocks, and does a direct query into the user database. The only reason I call it a "crude hack" is that I implemented it using
*Qpsmtpd::SMTP::vrfy = \&my_vrfy;
which is not what I would call an elegant interface... ;)
John
